Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@suse.cz>
Cc: nigel@nigel.suspend2.net,
	Kexec Mailing List <kexec@lists.infradead.org>,
	linux-kernel@vger.kernel.org,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Huang Ying <ying.huang@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-pm@lists.linux-foundation.org,
	Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH -mm 1/2] kexec jump -v12: kexec jump
Date: Fri, 11 Jul 2008 22:40:58 +0200	[thread overview]
Message-ID: <200807112240.59461.rjw@sisk.pl> (raw)
In-Reply-To: <20080711202434.GB6261@elf.ucw.cz>

On Friday, 11 of July 2008, Pavel Machek wrote:
> On Fri 2008-07-11 12:21:31, Andrew Morton wrote:
> > 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?
> 
> Well, it will be tricky to get kjump-hibernation right with respect to
> ACPI, but we should be fairly close to basic hibernation working with
> this. It has major advantage of not needing refrigerator (and few
> disadvantages -- like doing aditional boot during suspend).

Please, stop that.  This has always been a bogus argument.

The truth is we could do hibernation without the freezer if
(a) some drivers were fixed not to rely on it (kexec doesn't help here),
(b) we had support at the block layer or filesystems level (kexec is a big
   workaround here).

> But main reason I'd like kjump to be in is different -- it should be
> useful to stuff like "dump but continue running", etc...

That's a different thing.

Thanks,
Rafael

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2008-07-11 20:40 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
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 [this message]
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=200807112240.59461.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --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@suse.cz \
    --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