From: Phillip Susi <psusi@cfl.rr.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: nigel@nigel.suspend2.net,
Kexec Mailing List <kexec@lists.infradead.org>,
linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Pavel Machek <pavel@ucw.cz>,
Andrew Morton <akpm@linux-foundation.org>,
linux-pm@lists.linux-foundation.org,
Jeremy Maitin-Shepard <jbms@cmu.edu>
Subject: Re: [PATCH 0/2 -mm] kexec based hibernation -v5
Date: Fri, 19 Oct 2007 15:53:12 -0400 [thread overview]
Message-ID: <47190B28.6070405@cfl.rr.com> (raw)
In-Reply-To: <1192068833.27482.13.camel@caritas-dev.intel.com>
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?
> 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?
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Phillip Susi <psusi@cfl.rr.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: "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: Fri, 19 Oct 2007 15:53:12 -0400 [thread overview]
Message-ID: <47190B28.6070405@cfl.rr.com> (raw)
In-Reply-To: <1192068833.27482.13.camel@caritas-dev.intel.com>
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?
> 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?
next prev parent reply other threads:[~2007-10-19 19:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 2:13 [PATCH 0/2 -mm] kexec based hibernation -v5 Huang, Ying
2007-10-11 2:13 ` Huang, Ying
2007-10-11 10:17 ` Rafael J. Wysocki
2007-10-11 10:17 ` Rafael J. Wysocki
2007-10-11 10:17 ` Rafael J. Wysocki
2007-10-12 3:19 ` Huang, Ying
2007-10-12 3:19 ` Huang, Ying
2007-10-12 11:37 ` Rafael J. Wysocki
2007-10-12 11:37 ` Rafael J. Wysocki
2007-10-12 11:37 ` Rafael J. Wysocki
2007-10-12 3:19 ` Huang, Ying
2007-10-19 19:53 ` Phillip Susi [this message]
2007-10-19 19:53 ` Phillip Susi
2007-10-20 1:53 ` david
2007-10-20 1:53 ` david
2007-10-20 1:53 ` david
2007-10-20 5:50 ` huang ying
2007-10-20 5:50 ` huang ying
2007-10-20 5:50 ` huang ying
2007-10-19 19:53 ` Phillip Susi
-- strict thread matches above, loose matches on Subject: below --
2007-10-11 2:13 Huang, Ying
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=47190B28.6070405@cfl.rr.com \
--to=psusi@cfl.rr.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=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 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.