From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Vivek Goyal <vgoyal@in.ibm.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Zachary Amsden <zach@vmware.com>, Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] x86: Fix boot protocol KEEP_SEGMENTS check.
Date: Tue, 30 Oct 2007 18:10:10 -0700 [thread overview]
Message-ID: <4727D5F2.6000402@goop.org> (raw)
In-Reply-To: <200710311149.23006.rusty@rustcorp.com.au>
Rusty Russell wrote:
> On Saturday 27 October 2007 03:29:04 Eric W. Biederman wrote:
>
>> The kernel only ever supports 1 version of the boot protocol
>> so there is no need to check the boot protocol revision to
>> see if a feature is supported.
>>
>
> OK, I'm completely confused, so this is probably a v. dumb question. Doesn't
> this boot header come from the boot loader?
No, other way around. It the kernel telling the bootloader "I
understand boot protocol X", and the bootloader makes sure it doesn't
fill out more than X allows. If the bootloader supports <X, then the
kernel's boot_params structure is pre-constructed with reasonable
default values.
J
prev parent reply other threads:[~2007-10-31 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 17:29 [PATCH] x86: Fix boot protocol KEEP_SEGMENTS check Eric W. Biederman
2007-10-26 17:59 ` H. Peter Anvin
2007-10-26 18:22 ` Eric W. Biederman
2007-10-26 18:52 ` Jeremy Fitzhardinge
2007-10-26 19:40 ` H. Peter Anvin
2007-10-31 0:49 ` Rusty Russell
2007-10-31 1:10 ` Jeremy Fitzhardinge [this message]
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=4727D5F2.6000402@goop.org \
--to=jeremy@goop.org \
--cc=James.Bottomley@hansenpartnership.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=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=vgoyal@in.ibm.com \
--cc=zach@vmware.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.