mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andi Kleen <ak@suse.de>, LKML <linux-kernel@vger.kernel.org>,
	pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: [RFC][PATCH -mm 2/4] Hibernation: Arbitrary boot kernel support on x86_64
Date: Wed, 22 Aug 2007 10:26:13 +0200	[thread overview]
Message-ID: <20070822082613.GB2479@elf.ucw.cz> (raw)
In-Reply-To: <200708221019.03798.rjw@sisk.pl>

On Wed 2007-08-22 10:19:03, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rjw@sisk.pl>
> 
> Make it possible to restore a hibernation image on x86_64 with the help of a
> kernel different from the one in the image.
> 
> The idea is to split the core restoration code into two separate parts and to
> place each of them in a different page.  The first part belongs to the boot
> kernel and is executed as the last step of the image kernel's memory restoration
> procedure.  It restores all of the image kernel's memory that has not been
> restored yet except for the one page containing the very code that is being
> executed at that time.  The final operation performed by it is a jump to the
> second part of the core restoration code that belongs to the image kernel and
> has just been restored.  This code restores the last remaining page of the image
> kernel's memory containing the first, already executed, part of the core
> restoration code (temporary page tables created by the boot kernel are used at
> this stage).  It also makes the CPU switch to the image kernel's page tables and
> restores the state of general purpose registers (including the stack pointer)
> from before the hibernation.
> 
> The main issue with this idea is that in order to jump to the second part of the
> restoration code the boot kernel needs to know its address.  However, this
> address may be passed to it in the image header.  Namely, the part of the image
> header previously used for checking if the version of the image kernel is
> correct can be replaced with some architecture specific data that will allow
> the boot kernel to jump to the right address within the image kernel.  These
> data should also be used for checking if the image kernel is compatible with
> the boot kernel (as far as the memory restroration procedure is concerned).
> It can be done, for example, with the help of a "magic" value that has to be
> equal in both kernels, so that they can be regarded as compatible.
> 
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>

ACK.
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2007-08-22 15:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22  8:15 [RFC][PATCH -mm 0/4] " Rafael J. Wysocki
2007-08-22  8:17 ` [RFC][PATCH -mm 1/4] Hibernation: Arbitrary boot kernel support - generic code Rafael J. Wysocki
2007-08-22  8:25   ` Pavel Machek
2007-08-22  8:19 ` [RFC][PATCH -mm 2/4] Hibernation: Arbitrary boot kernel support on x86_64 Rafael J. Wysocki
2007-08-22  8:26   ` Pavel Machek [this message]
2007-08-22  8:20 ` [RFC][PATCH -mm 3/4] Hibernation: Pass CR3 in the image header " Rafael J. Wysocki
2007-08-22  8:28   ` Pavel Machek
2007-08-22 16:17     ` Rafael J. Wysocki
2007-08-22 20:49       ` [linux-pm] " Rafael J. Wysocki
2007-08-24  9:02         ` Pavel Machek
2007-08-24 21:24           ` Rafael J. Wysocki
2007-08-22  8:21 ` [RFC][PATCH -mm 4/4] Hibernation: Use temporary page tables for kernel text mapping " Rafael J. Wysocki
2007-08-22  8:29   ` Pavel Machek
2007-08-22 16:16     ` Rafael J. Wysocki
2007-08-24  8:31       ` Pavel Machek

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=20070822082613.GB2479@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=rjw@sisk.pl \
    /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

all inboxes | Powered by JetHome®