On ?t 15-06-06 19:29:47, Linus Torvalds wrote: > > > On Fri, 16 Jun 2006, Benjamin Herrenschmidt wrote: > > > > But how can you save a sate and use it for resume if the device can > > still operate on further requests ? Your state won't be consistent > > anymore... the state your resume function will get will _not_ match the > > last known hardware state. Pretty annoying. > > Not annoying at all, and there is absolutely no disconnect. > > > Also that means that for things like STD and kexec, you still need a > > second step "suspend" phase to actually stop DMAs which involve stopping > > processing. > > That's the _real_ suspend. The last thing you do. The thing you do _after_ > you've saved the snapshot. But but but but I need need need DMAs stopped to create the image, too. So I actually need DMAs stopped two times during suspend to disk, once when creating the image, and once as the last thing I do. Yes, it is confusing, but it allows me to have _atomic_ image, and I believe that means it is less confusing than alternatives. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
