From: ebiederm@xmission.com (Eric W. Biederman)
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Jeremy Fitzhardinge <jeremy@xensource.com>,
Rusty Russell <rusty@rustcorp.com.au>,
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: Fri, 26 Oct 2007 12:22:39 -0600 [thread overview]
Message-ID: <m1k5p920sw.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <47222AFA.9030902@zytor.com> (H. Peter Anvin's message of "Fri, 26 Oct 2007 10:59:22 -0700")
"H. Peter Anvin" <hpa@zytor.com> writes:
> Eric W. Biederman wrote:
>>
>> Both x86 and x86_64 support the same boot protocol so we need
>> to implement the KEEP_SEGMENTS on x86_64 as well. It isn't
>> just paravirt bootloaders that could use this functionality.
>>
>
> Out of curiousity, what other users do you see?
Simply that is easier to provide segments that are not fit to be
reloaded before the kernel sets up it's own GDT. Then to ensure you
stick a GDT someplace that won't get stomped.
Especially before we froze which segments numbers the kernel
would load into the boot protocol. I would have used this in
places where I was doing 32bit bootloader work as it is just easier to
support.
Eric
next prev parent reply other threads:[~2007-10-26 18:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 17:29 Eric W. Biederman
2007-10-26 17:59 ` H. Peter Anvin
2007-10-26 18:22 ` Eric W. Biederman [this message]
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
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=m1k5p920sw.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jeremy@xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome