From: "Huang, Ying" <ying.huang@intel.com>
To: "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>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH -mm -v5 0/3] i386/x86_64 boot: 32-bit boot protocol
Date: Fri, 12 Oct 2007 13:52:25 +0800 [thread overview]
Message-ID: <1192168345.17539.42.camel@caritas-dev.intel.com> (raw)
This patchset defines a 32-bit boot protocol for i386/x86_64 platform,
adds an extensible boot parameter passing mechanism, export the boot
parameters via sysfs.
The patchset has been tested against 2.6.23-rc8-mm2 kernel on x86_64
and i386.
This patchset is based on the proposal of Peter Anvin.
Known Issues:
- 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.
- The fields in zero page are fairly complex (such as struct
edd_info). Is it necessary to document every field inside the first
level fields, until the primary data type? Or is it sufficient to
provide the C struct name only?
v5:
- Use bt_ioremap/bt_iounmap in copy_setup_data.
v4:
- Reserve setup_data and boot parameters for accessing during
runtime.
- Export boot parameters via sysfs.
v3:
- Move hd0_info and hd1_info back to zero page for compatibility.
v2:
- Increase the boot protocol version number
- Check version number before parsing setup data.
- Revise zero page description according to the source code and move
them to zero-page.txt.
Best Regards,
Huang Ying
next reply other threads:[~2007-10-12 5:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 5:52 Huang, Ying [this message]
2007-10-15 1:47 ` [PATCH -mm -v5 0/3] i386/x86_64 boot: 32-bit boot protocol Huang, Ying
2007-10-17 1:59 ` Huang, Ying
2007-10-17 8:25 ` Andi Kleen
2007-10-17 9:05 ` Huang, Ying
2007-10-17 9:24 ` Andi Kleen
2007-10-18 6:44 ` Huang, Ying
2007-10-17 9:38 ` Eric W. Biederman
2007-10-18 6:57 ` 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=1192168345.17539.42.camel@caritas-dev.intel.com \
--to=ying.huang@intel.com \
--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 \
/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