Re: suspend.c vs driver-model.txt

[Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>]

Hi!

> >> The nice thing here, I beleive, is that suspend to disk could then just
> >> be an additional generic step between 1) and 2) that takes care of
> >> dumping memory content to disk.
> >
> >It can not, because after saving state you can not easily write to
> >swap partition.
> 
> Well, you have to. I mean, you can't write to swap before saving state
> (or you'll miss some state information). Which means the device dealing
> with the save has to be treated as a special case. At least, that's what
> we figured out when discussing this during OLS. 

Discussing with who?

Its rather simple: free half of memory, stop everything, save device
state, copy used memory into free memory, continue devices, save data
from "free" memory into swap.

> >Too complicated. Look at swsusp -- it is designed not to need
> >pre-allocated pages, pre-mapped DMA etc.
> 
> I didn't look at it recently, but does it work properly in a solid
> way whatever state other devices are ?

It is designed to be safe, yes.

								Pavel
-- 
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?


-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31