From: Jeremy Maitin-Shepard <jbms@cmu.edu>
To: Oliver Neukum <oliver@neukum.org>
Cc: Pavel Machek <pavel@ucw.cz>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Al Boldi <a1426z@gawab.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Hibernation Redesign
Date: Mon, 09 Jul 2007 10:26:14 -0400 [thread overview]
Message-ID: <87bqelwt4p.fsf@jbms.ath.cx> (raw)
In-Reply-To: <200707091602.27312.oliver@neukum.org> (Oliver Neukum's message of "Mon\, 9 Jul 2007 16\:02\:26 +0200")
Oliver Neukum <oliver@neukum.org> 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.
--
Jeremy Maitin-Shepard
next prev parent reply other threads:[~2007-07-09 14:26 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 14:37 Hibernation Redesign (was: malicious filesystems (was Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM) Al Boldi
2007-07-09 4:11 ` Hibernation Redesign Jeremy Maitin-Shepard
2007-07-09 4:29 ` Nick Piggin
2007-07-09 4:36 ` Jeremy Maitin-Shepard
2007-07-09 4:45 ` Nick Piggin
2007-07-09 4:54 ` Jeremy Maitin-Shepard
2007-07-09 4:58 ` Nick Piggin
2007-07-09 5:33 ` Nick Piggin
2007-07-09 6:22 ` Jeremy Fitzhardinge
2007-07-09 13:45 ` Pavel Machek
2007-07-09 14:02 ` Oliver Neukum
2007-07-09 14:26 ` Jeremy Maitin-Shepard [this message]
2007-07-09 15:09 ` Oliver Neukum
2007-07-09 15:27 ` Jeremy Maitin-Shepard
2007-07-09 4:39 ` Nick Piggin
2007-07-09 13:52 ` Pavel Machek
2007-07-09 15:30 ` Al Boldi
2007-07-10 1:29 ` Nick Piggin
2007-07-10 2:28 ` Jeremy Maitin-Shepard
2007-07-10 14:57 ` Jeremy Fitzhardinge
2007-07-10 17:25 ` Jeremy Maitin-Shepard
2007-07-10 22:59 ` Jeremy Fitzhardinge
2007-07-11 4:11 ` Al Boldi
2007-07-11 10:27 ` Rafael J. Wysocki
2007-07-11 10:42 ` Miklos Szeredi
2007-07-11 11:04 ` Rafael J. Wysocki
2007-07-11 11:11 ` Miklos Szeredi
2007-07-11 11:50 ` Rafael J. Wysocki
2007-07-11 11:54 ` Miklos Szeredi
2007-07-11 12:00 ` Nigel Cunningham
2007-07-11 12:09 ` Miklos Szeredi
2007-07-11 12:17 ` Nigel Cunningham
2007-07-11 12:27 ` Rafael J. Wysocki
2007-07-11 12:29 ` Miklos Szeredi
2007-07-11 21:04 ` Rafael J. Wysocki
2007-07-12 9:15 ` Pavel Machek
2007-07-12 22:13 ` Miklos Szeredi
2007-07-11 12:19 ` Rafael J. Wysocki
2007-07-11 12:49 ` Nigel Cunningham
2007-07-11 21:06 ` Rafael J. Wysocki
2007-07-11 12:11 ` Nigel Cunningham
2007-07-11 12:24 ` Miklos Szeredi
2007-07-11 12:46 ` Nigel Cunningham
2007-07-11 12:55 ` Miklos Szeredi
2007-07-11 13:16 ` Jeremy Maitin-Shepard
2007-07-11 20:48 ` Mark Lord
2007-07-11 21:14 ` Rafael J. Wysocki
2007-07-11 22:17 ` Al Boldi
2007-07-11 22:34 ` Rafael J. Wysocki
2007-07-11 23:12 ` Al Boldi
2007-07-11 23:31 ` Nigel Cunningham
2007-07-12 3:11 ` Al Boldi
2007-07-12 13:20 ` Rafael J. Wysocki
2007-07-16 6:04 ` Nick Piggin
2007-07-12 20:29 ` Jeremy Maitin-Shepard
2007-07-11 23:46 ` Nigel Cunningham
2007-07-11 17:55 ` david
2007-07-11 22:54 ` Nigel Cunningham
2007-07-10 17:45 ` Al Boldi
2007-07-10 18:20 ` Jeremy Maitin-Shepard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bqelwt4p.fsf@jbms.ath.cx \
--to=jbms@cmu.edu \
--cc=a1426z@gawab.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=oliver@neukum.org \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox