From: "H. Peter Anvin" <hpa@zytor.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Jeremy Fitzhardinge <jeremy@goop.org>,
"Pan, Jacob jun" <jacob.jun.pan@intel.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Andres Salomon <dilinger@queued.net>
Subject: RFC: can we kill the KEEP_SEGMENTS bzImage flag?
Date: Thu, 03 Feb 2011 09:19:42 -0800 [thread overview]
Message-ID: <4D4AE3AE.7000009@zytor.com> (raw)
> Bit 6 (write): KEEP_SEGMENTS
> Protocol: 2.07+
> - If 0, reload the segment registers in the 32bit entry point.
> - If 1, do not reload the segment registers in the 32bit entry point.
> Assume that %cs %ds %ss %es are all set to flat segments with
> a base of 0 (or the equivalent for their environment).
Does anything actually rely on this bit or can we kill it? I think it
was added as a crutch for paravirtualization, but I'm being told it is
not used...
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next reply other threads:[~2011-02-03 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 17:19 H. Peter Anvin [this message]
2011-02-03 20:01 ` RFC: can we kill the KEEP_SEGMENTS bzImage flag? 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=4D4AE3AE.7000009@zytor.com \
--to=hpa@zytor.com \
--cc=dilinger@queued.net \
--cc=jacob.jun.pan@intel.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).