Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!brutus.cs.uiuc.edu!ginosko!uunet!cbmvax!valentin
From: valentin@cbmvax.UUCP (Valentin Pepelea)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Exec questions...
Message-ID: <8315@cbmvax.UUCP>
Date: 27 Oct 89 05:40:45 GMT
References: <218@egrunix.UUCP> <8278@cbmvax.UUCP>
Reply-To: valentin@cbmvax.UUCP (Valentin Pepelea)
Organization: Commodore Technology, West Chester, PA
Lines: 26

In article <8278@cbmvax.UUCP> valentin@cbmvax.UUCP (Valentin Pepelea) writes:
>In article <218@egrunix.UUCP> cogswell@unix.secs.oakland.edu (Dan Cogswell)
>writes:
>
>> Is it possible for a user program to easily and reliably schedule tasks
>> already in the various system lists??  
>
>Only if they are in the TaskReady list. If they are in the Running or the Wait
>lists, then it would be really stupid to forcibly schedule them onto the CPU.

I made an error, Bryce pointed it out to me. The answer should have been NO.

>Well yes, you can always play with the Exec lists within Forbid() calls. As
>long as the code you are executing and the data you are accessing are all in
>MEMF_PUBLIC memory, you are safe.

Here is another error. You can play with task lists only within Disable()
calls, not Forbid() calls. Congratulate bryce for this one, too. 

Valentin
-- 
"An  operating  system  without        Name:    Valentin Pepelea
 virtual memory is an operating        Phone:   (215) 431-9100
 system without virtue."               Usenet:  uunet!cbmvax!valentin
                                       Bitnet:  cbmvax!valentin@uunet.uu.net
         - Ancient Inca Proverb        Claimer: these aren't Commodore thoughts