From: Vivek Goyal <vgoyal@redhat.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>,
linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org,
Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: [PATCH -mm 2/2] kexec jump -v12: save/restore device state
Date: Mon, 14 Jul 2008 09:48:05 -0400 [thread overview]
Message-ID: <20080714134805.GD16673@redhat.com> (raw)
In-Reply-To: <1215401124.4660.5.camel@caritas-dev.intel.com>
On Mon, Jul 07, 2008 at 11:25:24AM +0800, Huang Ying wrote:
> This patch implements devices state save/restore before after kexec.
>
>
> This patch together with features in kexec_jump patch can be used for
> following:
>
> - A simple hibernation implementation without ACPI support. You can
> kexec a hibernating kernel, save the memory image of original system
> and shutdown the system. When resuming, you restore the memory image
> of original system via ordinary kexec load then jump back.
>
> - Kernel/system debug through making system snapshot. You can make
> system snapshot, jump back, do some thing and make another system
> snapshot.
>
> - Cooperative multi-kernel/system. With kexec jump, you can switch
> between several kernels/systems quickly without boot process except
> the first time. This appears like swap a whole kernel/system out/in.
>
> - A general method to call program in physical mode (paging turning
> off). This can be used to invoke BIOS code under Linux.
>
Huang,
You have cited various possible use cases of this patchset. Which is
the specific feature you are planning to use?
Thinking more about it, what's the compelling feature out of this list
which makes this patchset a strong candidate for inclusion?
Regarding hibernation, Rafael does not think this is the way to go
for future.
Regarding ability to have two kernels in memory at the same time and
be able to jump between these two looks like a cool feature but who
is actually planning to use it?
So I am curious to know, which is the compelling feature you are planning
to use?
Thanks
Vivek
next prev parent reply other threads:[~2008-07-14 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 3:25 [PATCH -mm 2/2] kexec jump -v12: save/restore device state Huang Ying
2008-07-14 13:48 ` Vivek Goyal [this message]
2008-07-15 5:19 ` 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=20080714134805.GD16673@redhat.com \
--to=vgoyal@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox