Re: Hibernation Redesign

[Oliver Neukum]

Am Montag, 9. Juli 2007 schrieb Pavel Machek:
> Hi!
> 
> > >> This approach eliminates the need for the freezer, as it would make
> > >> hibernate look a lot a bit like suspend to ram from the perspective of
> > >> the "old" kernel (the kernel being hibernated), as the hibernate
> > >> operation itself would be completely atomic from the perspective of the
> > >> "old" kernel.  That is not to say, of course, that any code paths would
> > >> actually be shared, or that the drivers would do the same things
> > >> (because they probably would not).
> > 
> > > Well it basically is suspend to RAM with the additional step that a
> > > new kernel gets booted and writes out the data from RAM to disk then
> > > shuts down.
> > 
> > There is the key difference, though, that the drivers should do rather
> > different things.  In particular, rather than place the hardware in a
> > low-power mode, it should place it in some state such that the new
> > kernel being loaded can handle it.
> 
> Actually, when current kernel restores the snapshot... driver
> requirements seem to be pretty similar. So that should not be a big
> problem.

Hm, once the new kernel is booted, this decision is irrevocable, isn't it?
Is there any way to deal with errors by handing control back?

	Regards
		Oliver

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/