On Tue, 17 Jul 2007, Jeremy Maitin-Shepard wrote:
[email protected] writes:
[snip]
this is where we disagree.
why not? if all that the hibernated kernel does is to suspend-to-ram and makes
no changes to disks or TCP connections anything that it does do would be lost if
power were to fail and you instead did a restore from disk.
It would be okay to switch the "hibernated" kernel in order to
e.g. initiate a suspend to ram provided that everything is done
atomically with interrupts off, for instance. It is not clear, though,
that it is possible to suspend to ram atomically like that.
why would it neeed to be with interrupts off?
I am arguing that it wouldn't matter if the "hibernated" kernel changed
every bit of ram, as long as it didn't change anything that would be
visable when the ram is overwritten by the saved image.
There is also the question of what state the devices will be in when
switching back from the "save image" kernel to the "hibernated" kernel.
yes, this is a key factor.
if the saved image assumes that the hardware is in some ACPI mode instead
of re-initializeing the hardware then the suspend-to-ram operation could
leave them in a different mode.
but if the saved image doesn't make assumptions about the hardware modes
and initializes the hardware then it shouldn't matter.
David Lang
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
