[linux-pm] [PATCH -mm] kexec jump -v9

Eric W. Biederman ebiederm at xmission.com
Thu Mar 13 19:07:17 EDT 2008

"Rafael J. Wysocki" <rjw at sisk.pl> writes:

> From the ACPI compliance point of view it's better to do it this way.  We need
> to put the devices into low power states anyway before "powering off" the
> system and we won't need to touch them for the second time if we do that
> in advance.

Interesting.  From a kexec jump where we exit the kernel and then return
to it seem all that is required.

I will have to look at the ACPI case.  That seems to be the lynch pin
of a couple of arguments for doing strange things: ACPI requires it.

> Still, it would be sufficient if we disconnected the drivers from the hardware
> and thus prevented applications from accessing that hardware.

My gut feeling is that except for a handful of drivers we could even
get away with simply implementing hot unplug and hot replug.  Disks
are the big exception here.

Which suggests to me that it is at least possible that the methods we
want for a kexec jump hibernation may be different from an in-kernel
hibernation and quite possibly are easier to implement.


More information about the kexec mailing list