LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* RFC: can we kill the KEEP_SEGMENTS bzImage flag?
@ 2011-02-03 17:19 H. Peter Anvin
  2011-02-03 20:01 ` Jeremy Fitzhardinge
  0 siblings, 1 reply; 2+ messages in thread
From: H. Peter Anvin @ 2011-02-03 17:19 UTC (permalink / raw)
  To: Linux Kernel Mailing List
  Cc: Ingo Molnar, Thomas Gleixner, Jeremy Fitzhardinge, Pan,
	Jacob jun, Rusty Russell, Andres Salomon

>   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.


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: RFC: can we kill the KEEP_SEGMENTS bzImage flag?
  2011-02-03 17:19 RFC: can we kill the KEEP_SEGMENTS bzImage flag? H. Peter Anvin
@ 2011-02-03 20:01 ` Jeremy Fitzhardinge
  0 siblings, 0 replies; 2+ messages in thread
From: Jeremy Fitzhardinge @ 2011-02-03 20:01 UTC (permalink / raw)
  To: H. Peter Anvin
  Cc: Linux Kernel Mailing List, Ingo Molnar, Thomas Gleixner, Pan,
	Jacob jun, Rusty Russell, Andres Salomon

On 02/03/2011 09:19 AM, H. Peter Anvin wrote:
>>   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...

We originally added it with the idea that we might change the Xen boot
sequence to just enter via the normal entrypoint before wandering off to
the Xen paravirt path - mostly as a way of making use of the bzImage's
own decompresser rather than having to have that externally.

But we never ended up doing that, so the paravirt boot path is unused by
Xen, and I don't see that changing.

I think VMI may have used it, but that's moot now.

So I think lguest is the only potential user, and I'm not sure if it
actually does.

    J

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-02-03 20:01 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-02-03 17:19 RFC: can we kill the KEEP_SEGMENTS bzImage flag? H. Peter Anvin
2011-02-03 20:01 ` Jeremy Fitzhardinge

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).