[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1213319932.22697.9.camel@caritas-dev.intel.com>
Date: Fri, 13 Jun 2008 09:18:52 +0800
From: "Huang, Ying" <ying.huang@...el.com>
To: Vivek Goyal <vgoyal@...hat.com>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
Pavel Machek <pavel@....cz>, nigel@...el.suspend2.net,
"Rafael J. Wysocki" <rjw@...k.pl>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org,
Kexec Mailing List <kexec@...ts.infradead.org>
Subject: Re: [PATCH -mm 2/2] kexec jump -v11: save/restore device state
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists