From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Pavel Machek <pavel@ucw.cz>, "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 0/3 -mm] kexec jump -v8
Date: Fri, 21 Dec 2007 19:35:27 +1100 [thread overview]
Message-ID: <476B7ACF.8020602@nigel.suspend2.net> (raw)
In-Reply-To: <1198222399.1965.15.camel@caritas-dev.intel.com>
Hi.
Huang, Ying wrote:
> This patchset provides an enhancement to kexec/kdump. It implements
> the following features:
>
> - Backup/restore memory used both by the original kernel and the
> kexeced kernel.
Why the kexeced kernel as well?
[...]
> The features of this patchset can be used as follow:
>
> - Kernel/system debug through making system snapshot. You can make
> system snapshot, jump back, do some thing and make another system
> snapshot.
Are you somehow recording all the filesystem changes after the first
snapshot? If not, this is pointless (you'll end up with filesystem
corruption).
[...]
> - 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.
How is this useful to the end user?
Regards,
Nigel
next prev parent reply other threads:[~2007-12-21 8:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 7:33 [PATCH 0/3 -mm] kexec jump -v8 Huang, Ying
2007-12-21 8:35 ` Nigel Cunningham [this message]
2007-12-21 8:53 ` Huang, Ying
2007-12-27 1:57 ` Vivek Goyal
2007-12-27 2:33 ` Huang, Ying
2007-12-27 18:12 ` Vivek Goyal
2007-12-28 7:30 ` Huang, Ying
2007-12-28 21:33 ` Vivek Goyal
2007-12-29 2:00 ` Huang, Ying
2007-12-31 19:26 ` Vivek Goyal
2008-01-03 8:42 ` Huang, Ying
2008-01-06 20:49 ` Vivek Goyal
2008-01-07 8:12 ` 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=476B7ACF.8020602@nigel.suspend2.net \
--to=nigel@nigel.suspend2.net \
--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=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