From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Andi Kleen <ak@suse.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
akpm@linux-foundation.org, Yinghai Lu <yhlu.kernel@gmail.com>,
Chandramouli Narayanan <mouli@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm -v3 1/2] i386/x86_64 boot: setup data
Date: Sat, 22 Sep 2007 08:44:08 -0700 [thread overview]
Message-ID: <46F53848.3030100@goop.org> (raw)
In-Reply-To: <1190192306.12429.76.camel@caritas-dev.intel.com>
Huang, Ying wrote:
> This patch add a field of 64-bit physical pointer to NULL terminated
> single linked list of struct setup_data to real-mode kernel
> header. This is used as a more extensible boot parameters passing
> mechanism.
>
> This patch has been tested against 2.6.23-rc6-mm1 kernel on x86_64. It
> is based on the proposal of Peter Anvin.
>
>
> Known Issues:
>
> 1. Where is safe to place the linked list of setup_data?
> Because the length of the linked list of setup_data is variable, it
> can not be copied into BSS segment of kernel as that of "zero
> page". We must find a safe place for it, where it will not be
> overwritten by kernel during booting up. The i386 kernel will
> overwrite some pages after _end. The x86_64 kernel will overwrite some
> pages from 0x1000 on.
>
Do you actually need a linked list of data? This is similar to the
changes to bzImage to support booting bzImage a paravirt environment,
but I just proposed a pointer to a single info structure, along with a
field to identify the boot environment (ie, native/lguest/xen etc). It
would be easy to extend this to handle EFI as just another boot
environment, and you could hang a list of structures off the pointer.
J
next prev parent reply other threads:[~2007-09-22 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 8:58 [PATCH -mm -v3 1/2] i386/x86_64 boot: setup data Huang, Ying
2007-09-19 16:04 ` H. Peter Anvin
2007-09-27 6:06 ` Huang, Ying
2007-09-28 22:28 ` H. Peter Anvin
2007-09-22 15:44 ` Jeremy Fitzhardinge [this message]
2007-09-22 19:56 ` H. Peter Anvin
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=46F53848.3030100@goop.org \
--to=jeremy@goop.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.