From: ebiederm@xmission.com (Eric W. Biederman)
To: Pavel Machek <pavel@ucw.cz>
Cc: "Huang, Ying" <ying.huang@intel.com>,
vgoyal@in.ibm.com, nigel@nigel.suspend2.net,
Andrew Morton <akpm@linux-foundation.org>,
Jeremy Maitin-Shepard <jbms@cmu.edu>,
Alan Stern <stern@rowland.harvard.edu>,
linux-pm@lists.linux-foundation.org,
Kexec Mailing List <kexec@lists.infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 0/2 -mm] kexec based hibernation
Date: Mon, 27 Aug 2007 07:05:41 -0600 [thread overview]
Message-ID: <m1d4x95dqy.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20070827075317.GB2060@elf.ucw.cz> (Pavel Machek's message of "Mon, 27 Aug 2007 09:53:17 +0200")
Pavel Machek <pavel@ucw.cz> writes:
> Hi!
>
>> > Does this make sense?
>>
>> Yes, this is a sensible optimization. But I think it may be better to
>> make bootloader load kernel D directly into a specified memory location.
>> For example, we can add a option to "kernel" command of grub.
>>
>> And, I think we can do more in bootloader. Such as we can prepare
>> two
>
> Yes, that would be nice.
>
> It will mean quite a bit of work, but I guess it should be the long
> term goal. Loading restore kernel directly from bootloader means:
>
> 1) it is fast -- no need to boot another kernel
>
> 2) it is "classical" way of doing things
>
> On the other hand, we loose flexibility that way:
>
> 1) it locks you onto one bootloader
>
> 2) you no longer have userland there to do uncompression, decryption,
> etc..
True although for the uncompression and decryption those aren't exactly foreign
requirements for bootloaders.
Eric
next prev parent reply other threads:[~2007-08-27 13:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 1:14 Huang, Ying
2007-08-27 1:28 ` [linux-pm] " Hu, Fenghua
2007-08-27 2:16 ` Huang, Ying
2007-08-29 2:41 ` Nick Piggin
2007-08-27 5:00 ` Vivek Goyal
2007-08-27 6:18 ` Huang, Ying
2007-08-27 6:46 ` Vivek Goyal
2007-08-27 7:53 ` Pavel Machek
2007-08-27 13:05 ` Eric W. Biederman [this message]
2007-08-27 13:15 ` Pavel Machek
2007-08-28 1:24 ` 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=m1d4x95dqy.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=jbms@cmu.edu \
--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=stern@rowland.harvard.edu \
--cc=vgoyal@in.ibm.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
all inboxes | Powered by JetHome®