All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Ingo Molnar <mingo@elte.hu>
Cc: pm list <linux-pm@lists.linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Len Brown <lenb@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
	Pavel Machek <pavel@suse.cz>
Subject: Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64
Date: Mon, 31 Dec 2007 18:57:33 +0100	[thread overview]
Message-ID: <200712311857.34445.rjw@sisk.pl> (raw)
In-Reply-To: <20071231104311.GA30003@elte.hu>

On Monday, 31 of December 2007, Ingo Molnar wrote:
> 
> * Rafael J. Wysocki <rjw@sisk.pl> wrote:
> 
> > > ok, just to make sure we are talking about the same thing. Do you 
> > > mean we can restore an image saved by v2.6.12 into v2.6.24? I.e. a 
> > > 2.6.24 kernel will be able to run a 2.6.12 kernel's hibernation 
> > > image, with all the kernel internal data from v2.6.12, etc? No way 
> > > can that work.
> > 
> > Well, not exactly.  The support for different boot and image kernels 
> > has only been merged recently, but we can use the current git to 
> > restore 2.6.24-rc6-mm1, for example.
> > 
> > The trick is to pass a little additional information in the image 
> > header that can be used by the boot kernel to locate the entry point 
> > to the image kernel and the image kernel's page tables.
> 
> ok - i thought you meant that there's a general capability to resume 
> across kernel versions. (which would be close to impossible without some 
> major surgery.)

Well, there will be one. :-)  For example, one should be able to use a 2.6.25+
boot kernel to load the image containing 2.6.24-rc6 and restore the memory
state from it.

> btw., in what way is this different from kexec?

Not that much different indeed.  The hibernation code is more focused on
restoring the pre-hibernation state of the system rather than anything else,
plus on ACPI systems we try to handle the platform in accordance with the
specification (to some extent - you'd have to use a non-ACPI boot kernel to
follow the specification literally, which is possible but not straightforward).

Rafael

  parent reply	other threads:[~2007-12-31 17:37 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-28 12:53 [PATCH] Hibernation: Document __save_processor_state() on x86-64 Rafael J. Wysocki
2007-12-28 12:53 ` Rafael J. Wysocki
2007-12-29 23:43 ` Pavel Machek
2007-12-29 23:43 ` Pavel Machek
2007-12-30 13:30   ` Rafael J. Wysocki
2007-12-30 13:30   ` Rafael J. Wysocki
2007-12-30 20:17     ` Pavel Machek
2007-12-30 20:17     ` Pavel Machek
2007-12-30 14:21 ` Ingo Molnar
2007-12-30 21:04   ` Rafael J. Wysocki
2007-12-30 21:04   ` Rafael J. Wysocki
2007-12-30 20:51     ` Ingo Molnar
2007-12-30 21:48       ` Rafael J. Wysocki
2007-12-30 21:48       ` Rafael J. Wysocki
2007-12-30 21:31         ` Ingo Molnar
2007-12-30 21:31         ` Ingo Molnar
2007-12-30 22:08           ` Rafael J. Wysocki
2007-12-30 22:08           ` Rafael J. Wysocki
2007-12-30 21:57             ` Ingo Molnar
2007-12-30 21:57               ` Ingo Molnar
2007-12-30 22:37               ` Rafael J. Wysocki
2007-12-30 22:37               ` Rafael J. Wysocki
2007-12-31 10:43                 ` Ingo Molnar
2007-12-31 10:43                 ` Ingo Molnar
2007-12-31 17:57                   ` Rafael J. Wysocki
2007-12-31 17:57                   ` Rafael J. Wysocki [this message]
2007-12-31  9:29               ` Torsten Kaiser
2007-12-31  9:29               ` Torsten Kaiser
2007-12-30 20:51     ` Ingo Molnar
2007-12-30 14:21 ` Ingo Molnar

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=200712311857.34445.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mingo@elte.hu \
    --cc=pavel@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.