From: Ingo Molnar <mingo@elte.hu>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Pavel Machek <pavel@suse.cz>, LKML <linux-kernel@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64
Date: Sun, 30 Dec 2007 22:57:45 +0100 [thread overview]
Message-ID: <20071230215745.GB31386@elte.hu> (raw)
In-Reply-To: <200712302308.51562.rjw@sisk.pl>
* Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > what's exactly in the hibernation image? Dirty data i suppose
>
> No, everything, including the kernel code, page tables etc. :-)
>
> > - but what about kernel-internal pages. What if we go from SLAB to
> > SLUB? What if the size of a structure changes? Etc.
>
> We can go from SLAB to SLUB just fine, it doesn't matter. The only
> thing that matters is we have to jump to the right address at the end
> of core_restore_code() (defined in arch/x86/kernel/suspend_asm_64.S).
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.
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
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: Sun, 30 Dec 2007 22:57:45 +0100 [thread overview]
Message-ID: <20071230215745.GB31386@elte.hu> (raw)
In-Reply-To: <200712302308.51562.rjw@sisk.pl>
* Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > what's exactly in the hibernation image? Dirty data i suppose
>
> No, everything, including the kernel code, page tables etc. :-)
>
> > - but what about kernel-internal pages. What if we go from SLAB to
> > SLUB? What if the size of a structure changes? Etc.
>
> We can go from SLAB to SLUB just fine, it doesn't matter. The only
> thing that matters is we have to jump to the right address at the end
> of core_restore_code() (defined in arch/x86/kernel/suspend_asm_64.S).
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.
Ingo
next prev parent reply other threads:[~2007-12-30 21:57 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 20:17 ` Pavel Machek
2007-12-30 20:17 ` Pavel Machek
2007-12-30 13:30 ` Rafael J. Wysocki
2007-12-30 14:21 ` Ingo Molnar
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 22:08 ` Rafael J. Wysocki
2007-12-30 22:08 ` Rafael J. Wysocki
2007-12-30 21:57 ` Ingo Molnar [this message]
2007-12-30 21:57 ` Ingo Molnar
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
2007-12-30 22:37 ` Rafael J. Wysocki
2007-12-31 9:29 ` Torsten Kaiser
2007-12-31 9:29 ` Torsten Kaiser
2007-12-30 21:31 ` Ingo Molnar
2007-12-30 20:51 ` Ingo Molnar
2007-12-30 21:04 ` Rafael J. Wysocki
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=20071230215745.GB31386@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@suse.cz \
--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 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.