public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Huang, Ying" <ying.huang@intel.com>
To: Vivek Goyal <vgoyal@redhat.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 -v11: save/restore device state
Date: Fri, 13 Jun 2008 09:18:52 +0800	[thread overview]
Message-ID: <1213319932.22697.9.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <20080612130225.GA9654@redhat.com>

On Thu, 2008-06-12 at 09:02 -0400, Vivek Goyal wrote:
[...]
> Few things I don't understand.
> 
> - Are you saying that hibernated image will be saved in initrd
>   (rootfs.gz)? But that saving is only in RAM, we never write back
>   it to disk?

No. Hibernated image should be saved in a dedicated raw partition as you
said below.

> - I thought we probably have to dedicate a raw partition kind of thing
>   for saving image and then modify boot loader command line to something
>   similar to, "resume=partition". Then initrd can go hunting for image
>   in respective partition (as specified by command line parameter) and if
>   image is not available then continue with normal boot.

Yes. But the boot-loader command line only need to be changed during
system install or hibernation setup. We need not change the location of
"hibernation partition" frequently.

So I think one boot-loader command line is sufficient for:

- normal boot
- normal boot a system to be hibernated
- boot helper system to restore the hibernated system

Best Regards,
Huang Ying


      reply	other threads:[~2008-06-13  1:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10  7:15 [PATCH -mm 2/2] kexec jump -v11: save/restore device state Huang, Ying
2008-06-10 18:01 ` [linux-pm] " Len Brown
2008-06-11  1:01   ` Huang, Ying
2008-06-11  8:21     ` Len Brown
2008-06-11  9:46       ` Huang, Ying
2008-06-13 18:05     ` Vivek Goyal
2008-06-16  1:29       ` Huang, Ying
2008-06-11 16:30 ` Vivek Goyal
2008-06-12  0:53   ` Huang, Ying
2008-06-12 13:02     ` Vivek Goyal
2008-06-13  1:18       ` Huang, Ying [this message]

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=1213319932.22697.9.camel@caritas-dev.intel.com \
    --to=ying.huang@intel.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=vgoyal@redhat.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