From: "H. Peter Anvin" <hpa@zytor.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: huang ying <huang.ying.caritas@gmail.com>,
Andi Kleen <ak@suse.de>, Yinghai Lu <yhlu.kernel@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Chandramouli Narayanan <mouli@linux.intel.com>,
linux-kernel@vger.kernel.org, Aaron Durbin <adurbin@google.com>
Subject: Re: [PATCH 0/3] x86_64 EFI runtime service support
Date: Wed, 22 Aug 2007 19:46:59 -0700 [thread overview]
Message-ID: <46CCF523.2090403@zytor.com> (raw)
In-Reply-To: <1187835680.3247.14.camel@caritas-dev.intel.com>
Huang, Ying wrote:
>
> My intention is that we have 3 possible schemes for kernel to use boot
> information.
>
That's not an intention, it's an observation.
> 1. Use "linked list" only. Then if booted with old bootloader which uses
> "zero page" protocol, the "zero page" information provided by bootloader
> should be converted to "linked list" for other part of kernel to use.
>
> 2. Use "zero page" only. Then if booted with new bootloader which
> provides "linked list" but not "zero page", the "linked list"
> information provided by bootloader should be converted to "zero page"
> for other part of kernel to use.
>
> 3. Use "zero page" + "linked list". Then if booted with old bootloader,
> the "linked list" is empty. If booted with new bootloader, both the
> "zero page" and "linked list" are used.
>
> We need to choose one from schemes above.
>
> - The scheme 1 appears the most clean one.
> - The scheme 2 has 4k "zero page" constraint, so it is not good.
> - The scheme 3 is easiest to be implemented.
>
> Personally, I prefer the scheme 1. But the scheme 3 is OK too.
Scheme 3 is the only realistic way to move away from the current
situation (scheme 2). Scheme 1 just means unnecessary divergences
between codepaths. If it wasn't for LunacyBIOS and (to a smaller
extent) kexec, we would probably be OK, but that's not the real world.
-hpa
next prev parent reply other threads:[~2007-08-23 2:47 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 7:30 [PATCH 0/3] x86_64 EFI runtime service support Huang, Ying
2007-08-15 22:42 ` Andrew Morton
2007-08-16 7:51 ` Huang, Ying
2007-08-16 14:11 ` Andi Kleen
2007-08-17 1:25 ` Huang, Ying
2007-08-17 16:11 ` H. Peter Anvin
2007-08-20 3:20 ` Huang, Ying
2007-08-20 17:12 ` H. Peter Anvin
2007-08-21 1:44 ` Huang, Ying
2007-08-21 3:54 ` H. Peter Anvin
2007-08-21 4:53 ` Huang, Ying
2007-08-21 11:33 ` Andi Kleen
2007-08-21 10:41 ` H. Peter Anvin
2007-08-21 11:45 ` Andi Kleen
2007-08-21 23:58 ` Yinghai Lu
2007-08-22 1:22 ` Andi Kleen
2007-08-22 6:43 ` Yinghai Lu
2007-08-22 11:11 ` Andi Kleen
2007-08-22 14:23 ` huang ying
2007-08-22 16:28 ` H. Peter Anvin
2007-08-23 2:21 ` Huang, Ying
2007-08-23 2:46 ` H. Peter Anvin [this message]
2007-08-22 14:41 ` Eric W. Biederman
2007-08-22 16:44 ` H. Peter Anvin
2007-08-22 7:20 ` Yinghai Lu
2007-08-15 23:16 ` Andrew Morton
2007-08-15 23:22 ` H. Peter Anvin
2007-08-16 8:00 ` Huang, Ying
2007-08-16 16:09 ` H. Peter Anvin
2007-08-19 22:27 ` Eric W. Biederman
2007-08-19 22:25 ` Eric W. Biederman
2007-08-19 23:46 ` Yinghai Lu
2007-08-20 17:05 ` H. Peter Anvin
2007-08-20 17:20 ` San Mehat
2007-08-20 20:13 ` Matthew Garrett
2007-08-20 5:14 ` Huang, Ying
2007-08-16 7:52 ` 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=46CCF523.2090403@zytor.com \
--to=hpa@zytor.com \
--cc=adurbin@google.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=huang.ying.caritas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mouli@linux.intel.com \
--cc=yhlu.kernel@gmail.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