On Monday, 28 May 2007 15:26, Pavel Machek wrote:
quoted text
> Hi!
> 
> > >That's clear, I'll have to use xen or kvm or similar which restores 
> > >the system as suspended. Thanks for the clarification of the limitations.
> > >
> > Sorry, I wrote that late at night and quickly. I should have said 
> > "design decision" rather than "limitation," For systems which don't do 
> > multiple kernels it's not an issue.
> > 
> > I certainly would not have made the same decision, but I didn't write 
> > the code. It seems more robust to save everything than to try to 
> > identify what has and hasn't changed in a modular kernel.
> 
> We rely on atomic copy routine not moving inside the kernel. Yes, it
> would be possible to copy it to "known good" address and gain ability
> to resume different kernels. Actually it should not be _that_ hard.

Yup.  Don't we do something like this for the (ACPI-based) suspend to RAM
already?

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