public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Huang, Ying" <ying.huang@intel.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Pavel Machek <pavel@ucw.cz>, "Rafael J. Wysocki" <rjw@sisk.pl>,
	Jeremy Maitin-Shepard <jbms@cmu.edu>,
	Alan Stern <stern@rowland.harvard.edu>,
	david@lang.hm, linux-kernel@vger.kernel.org,
	linux-pm@lists.linux-foundation.org,
	Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: [PATH 0/1] Kexec jump - v2 - the first step to kexec based hibernation
Date: Thu, 19 Jul 2007 12:15:04 +1000	[thread overview]
Message-ID: <200707191215.05245.nigel@nigel.suspend2.net> (raw)
In-Reply-To: <20070718180420.02352d4f.akpm@linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]

Hi.

On Thursday 19 July 2007 11:04:20 Andrew Morton wrote:
> On Sun, 15 Jul 2007 15:13:13 +0800
> "Huang, Ying" <ying.huang@intel.com> wrote:
> 
> > 
> > The changelog between v1 and v2
> > 
> > 1. The kexec jump implementation is put into the kexec/kdump
> >    framework instead of software suspend framework. The device
> >    and CPU state save/restore code of software suspend is called
> >    when needed.
> > 
> > 2. The same code path is used for both kexec a new kernel and jump
> >    back to original kernel.
> 
> I like the idea but I think I'll let people chat about it a bit more
> before looking at merging the patches, OK?

Please wait until you see a complete implementation that actually works. I'm 
sitting here quietly, following (and now breaking) the "If you can't say 
anything positive, don't say anything at all" line because I think that the 
more into the implementation details people get, the uglier this is going to 
show itself to be. I'm perfectly willing to be proven wrong, but haven't seen 
anything so far that's even begun to convince me otherwise.

Regards,

Nigel
-- 
See http://www.tuxonice.net for Howtos, FAQs, mailing
lists, wiki and bugzilla info.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-07-19  2:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-15  7:13 [PATH 0/1] Kexec jump - v2 - the first step to kexec based hibernation Huang, Ying
2007-07-15  9:08 ` Nigel Cunningham
2007-07-15 10:09 ` Rafael J. Wysocki
2007-07-19  1:04 ` Andrew Morton
2007-07-19  2:15   ` Nigel Cunningham [this message]
2007-07-19  3:30     ` david
2007-07-19  6:43   ` Huang, Ying
2007-07-19  9:13     ` Rafael J. Wysocki
2007-07-31  9:10 ` Pavel Machek
2007-07-31  9:25   ` Huang, Ying
2007-07-31 10:52     ` Eric W. Biederman
2007-07-31 11:12       ` Pavel Machek
2007-08-01  1:16       ` Huang, Ying
2007-07-31 11:14     ` Pavel Machek
2007-07-31 11:04 ` Pavel Machek
2007-08-01  1:34   ` Huang, Ying
2007-08-05 18:55     ` Pavel Machek
2007-08-06  2:31       ` Huang, Ying
2007-08-06  9:02         ` Pavel Machek
2007-08-06 13:22           ` 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=200707191215.05245.nigel@nigel.suspend2.net \
    --to=nigel@nigel.suspend2.net \
    --cc=akpm@linux-foundation.org \
    --cc=david@lang.hm \
    --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@suspend2.net \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.edu \
    --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