From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: LOADER_TYPE for Xen in boot_params?
Date: Mon, 07 Aug 2006 23:11:52 -0700 [thread overview]
Message-ID: <44D82B28.6010709@goop.org> (raw)
In-Reply-To: <44D3C397.6010202@zytor.com>
H. Peter Anvin wrote:
>>
>> Should I be poking some Xen-specific value into the LOADER_TYPE
>> field? If so, what value? Should I just claim 5? And should this
>> be Xen in particular, or reserve a value for 'hypervisor' and then
>> have some other mechanism to distinguish which one?
>>
>
> It probably should be Xen in particular. Send me a patch allocating 9
> for Xen, and use that.
Claim an ID number for Xen in the LOADER_TYPE field.
Also, keep the table in zero-page.txt consistent with boot.txt.
Signed-off-by: Jeremy Fitzhardinge <jeremy@xensource.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
diff -r 4f3c59461622 Documentation/i386/boot.txt
--- a/Documentation/i386/boot.txt Mon Aug 07 12:01:49 2006 -0700
+++ b/Documentation/i386/boot.txt Mon Aug 07 23:06:45 2006 -0700
@@ -181,6 +181,7 @@ filled out, however:
5 ELILO
7 GRuB
8 U-BOOT
+ 9 Xen
Please contact <hpa@zytor.com> if you need a bootloader ID
value assigned.
diff -r 4f3c59461622 Documentation/i386/zero-page.txt
--- a/Documentation/i386/zero-page.txt Mon Aug 07 12:01:49 2006 -0700
+++ b/Documentation/i386/zero-page.txt Mon Aug 07 23:07:30 2006 -0700
@@ -63,6 +63,10 @@ 0x210 char LOADER_TYPE, = 0, old one
2 for bootsect-loader
3 for SYSLINUX
4 for ETHERBOOT
+ 5 for ELILO
+ 7 for GRuB
+ 8 for U-BOOT
+ 9 for Xen
V = version
0x211 char loadflags:
bit0 = 1: kernel is loaded high (bzImage)
parent reply other threads:[~2006-08-08 6:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <44D3C397.6010202@zytor.com>]
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=44D82B28.6010709@goop.org \
--to=jeremy@goop.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome