[lkml]   [2007]   [Jul]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Hibernation Redesign
    Oliver Neukum <> writes:

    > Am Montag, 9. Juli 2007 schrieb Jeremy Maitin-Shepard:
    >> Oliver Neukum <> writes:
    >> [snip]
    >> > 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?
    >> Returning to the old kernel can be done by telling drivers to set the
    >> hardware to the appropriate state, then copying the backed up memory
    >> back to the beginning of physical memory, and finally jumping to the old
    >> kernel.  It would be much like what is done to resume from hibernation.

    > If you can do that, why load a new kernel image?

    The challenges in doing that are analogous to the challenges in
    suspending to RAM, for which it has been agreed that drivers should be
    fixed such that the freezer is not necessary.

    The hard part of hibernate is not creating the snapshot; rather, the
    hard part is writing the snapshot, and allowing the user some
    flexibility in how and where the snapshot is written. The kdump
    approach allows complete flexibility in writing the snapshot
    (essentially any kernel or user space facility can be used), while not
    interfering at all with the snapshot state.

    Jeremy Maitin-Shepard
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-07-09 17:31    [W:0.021 / U:119.584 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site