From: "huang ying" <huang.ying.caritas@gmail.com>
To: "Phillip Susi" <psusi@cfl.rr.com>
Cc: "Huang, Ying" <ying.huang@intel.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"Pavel Machek" <pavel@ucw.cz>,
nigel@nigel.suspend2.net, "Rafael J. Wysocki" <rjw@sisk.pl>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Jeremy Maitin-Shepard" <jbms@cmu.edu>,
linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org,
"Kexec Mailing List" <kexec@lists.infradead.org>
Subject: Re: [PATCH 0/2 -mm] kexec based hibernation -v5
Date: Sat, 20 Oct 2007 13:50:10 +0800 [thread overview]
Message-ID: <851fc09e0710192250k7c2d5269rf6bf1ec604a23603@mail.gmail.com> (raw)
In-Reply-To: <47190B28.6070405@cfl.rr.com>
On 10/20/07, Phillip Susi <psusi@cfl.rr.com> wrote:
> Huang, Ying wrote:
> > The hibernation procedure with the patch set is as follow:
> >
> > 1. Boot a kernel A
> >
> > 2. Work under kernel A
> >
> > 3. Kexec another kernel B (crash dump enabled) in kernel A.
> >
> > 4. Save the memory image of kernel A through crash dump (such as "cp
> > /proc/vmcore ~"). Save the "jump back entry".
>
> Doesn't this also save the memory of kernel B?
The memory area of kernel B is excluded from the elf header of
/proc/vmcore. This is done in kexec-tools (/sbin/kexec) patches.
> > 5. Shutdown or reboot
> >
> >
> > The restore process with the patch set is as follow:
> >
> > 1. Boot a kernel C (crash dump enabled), the memory area used by
> > kernel C must be a subset of memory area used by kernel B.
>
> Why is a third kernel needed? Why can't kernel B be used for this as
> well? In fact, if kernel A has been compiled to be relocatable and
> crash dump enabled, why wouldn't it suffice for all 3 instances?
One kernel can be used for three situation. In fact, I use just one
kernel for testing.
Best Regards,
Huang Ying
prev parent reply other threads:[~2007-10-20 5:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 2:13 Huang, Ying
2007-10-11 10:17 ` Rafael J. Wysocki
2007-10-12 3:19 ` Huang, Ying
2007-10-12 11:37 ` Rafael J. Wysocki
2007-10-19 19:53 ` Phillip Susi
2007-10-20 1:53 ` david
2007-10-20 5:50 ` huang ying [this message]
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=851fc09e0710192250k7c2d5269rf6bf1ec604a23603@mail.gmail.com \
--to=huang.ying.caritas@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=jbms@cmu.edu \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=nigel@nigel.suspend2.net \
--cc=pavel@ucw.cz \
--cc=psusi@cfl.rr.com \
--cc=rjw@sisk.pl \
--cc=ying.huang@intel.com \
/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®