From: Andrew Morton <akpm@linux-foundation.org>
To: Vivek Goyal <vgoyal@redhat.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>,
linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org,
Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: [PATCH -mm 1/2] kexec jump -v12: kexec jump
Date: Fri, 11 Jul 2008 12:21:31 -0700 [thread overview]
Message-ID: <20080711122131.b6461ab1.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080708145051.GA14745@redhat.com>
On Tue, 8 Jul 2008 10:50:51 -0400 Vivek Goyal <vgoyal@redhat.com> wrote:
> On Mon, Jul 07, 2008 at 11:25:22AM +0800, Huang Ying wrote:
> > This patch provides an enhancement to kexec/kdump. It implements
> > the following features:
> >
> > - Backup/restore memory used by the original kernel before/after
> > kexec.
> >
> > - Save/restore CPU state before/after kexec.
> >
>
> Hi Huang,
>
> In general this patch set looks good enough to live in -mm and
> get some testing going.
>
> To me, adding capability to return back to original kernel looks
> like a logical extension to kexec functionality.
Exciting ;) It's much less code than I expected.
I don't think I understand the feature any more. Once upon a time we
thought that this might become a new and better (or at least
better-code-sharing) way of doing suspend-to-disk. How far are we from
that?
What are the prospects of supporting other architectures?
Who maintains kexec-tools, and are they OK with merging up the
corresponding changes?
Thanks.
next prev parent reply other threads:[~2008-07-11 19:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 3:25 [PATCH -mm 1/2] kexec jump -v12: kexec jump Huang Ying
2008-07-07 12:50 ` Pavel Machek
2008-07-08 9:10 ` Huang Ying
2008-07-08 10:40 ` Pavel Machek
2008-07-09 1:12 ` Huang Ying
2008-07-08 14:50 ` Vivek Goyal
2008-07-09 1:09 ` Huang Ying
2008-07-11 19:21 ` Andrew Morton [this message]
2008-07-11 20:11 ` Vivek Goyal
2008-07-12 1:02 ` Nigel Cunningham
2008-07-14 5:46 ` Pavel Machek
2008-07-14 13:32 ` Vivek Goyal
2008-08-04 11:01 ` Pavel Machek
2008-07-14 13:09 ` Vivek Goyal
2008-07-11 20:24 ` Pavel Machek
2008-07-11 20:40 ` Rafael J. Wysocki
2008-07-12 2:23 ` Eric W. Biederman
2008-07-12 3:04 ` [linux-pm] " Alan Stern
2008-07-12 3:50 ` Eric W. Biederman
2008-07-12 18:52 ` Rafael J. Wysocki
2008-07-12 19:55 ` Alan Stern
2008-07-14 13:30 ` 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=20080711122131.b6461ab1.akpm@linux-foundation.org \
--to=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=vgoyal@redhat.com \
--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