Hi!

> To solve first of these problems we need to stop using PF_FROZEN to tell
> tasks that they should go to the refrigerator.  Instead, we can introduce
> a special TIF_*** flag and use it for this purpose, since it is allowed to
> change the other tasks' TIF_*** flags and there are special calls for it.
> 
> To avoid the freeze_process()-refrigerator() race we can make freeze_process()
> to always check the task's PF_FROZEN flag after it's read its "freeze" flag.
> We should also make sure that refrigerator() will always reset the task's
> "freeze" flag after it's set PF_FROZEN for it.
> 
> Signed-off-by: Rafael J. Wysocki <[EMAIL PROTECTED]>

ACK.
                                                                Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) 
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Suspend-devel mailing list
Suspend-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/suspend-devel

Reply via email to