From: ebiederm@xmission.com (Eric W. Biederman)
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Alexander van Heukelum <heukelum@mailshack.com>,
"Antonino A. Daplas" <adaplas@gmail.com>, Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@osdl.org>, Matt Domsch <Matt_Domsch@dell.com>,
Vivek Goyal <vgoyal@in.ibm.com>,
James Bottomley <James.Bottomley@HansenPar>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: x86 setup rewrite tree ready for flamage^W review
Date: Sat, 12 May 2007 12:35:28 -0600 [thread overview]
Message-ID: <m1mz09ritr.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <464602DC.4050603@zytor.com> (H. Peter Anvin's message of "Sat, 12 May 2007 11:09:32 -0700")
"H. Peter Anvin" <hpa@zytor.com> writes:
> Eric W. Biederman wrote:
>>
>> HPA is both right and wrong on this. The safe sequence for entering
>> protected mode requires a jump immediately after setting PE in %cr0.
>> To serialize the instruction stream and to be on an execution that
>> is tested and guaranteed to work in cpus.
>>
>
> Eric, that's complete nonsense. What Intel documents and what Intel
> tests are two very different things.
Likely.
> Intel appears to be afraid of what they call "the crack", but the
> semantics of the transition are quite well understood.
Regardless not putting a jump in there violates the principle of
be conservative in what you send.
> A lot of the Intel manuals are boilerplate written by technical writers.
> Once you're used to them you can spot it quite easily because it's
> carried from generation to generation with little change, even when it's
> blatantly obsoleted.
Even on 386 and 486 class cpus?
To some extent if the rules don't change it makes sense for them to
copy the information from one generation to the next of the architecture.
Even if the current cpus don't really care.
I guess I just don't see the sense in taking chances if we don't have
to, and I don't see any real advantage of doing a data segment reload
before the jump.
Eric
next prev parent reply other threads:[~2007-05-12 18:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 5:15 H. Peter Anvin
2007-05-09 6:51 ` Sam Ravnborg
2007-05-09 7:02 ` H. Peter Anvin
2007-05-09 8:11 ` Sam Ravnborg
2007-05-10 14:10 ` Alexander van Heukelum
2007-05-10 18:08 ` H. Peter Anvin
2007-05-10 18:38 ` Martin Mares
2007-05-11 0:55 ` H. Peter Anvin
2007-05-10 22:04 ` Alexander van Heukelum
2007-05-10 22:48 ` H. Peter Anvin
2007-05-12 12:21 ` Alexander van Heukelum
2007-05-12 14:20 ` Eric W. Biederman
2007-05-12 18:09 ` H. Peter Anvin
2007-05-12 18:35 ` Eric W. Biederman [this message]
2007-05-12 18:59 ` H. Peter Anvin
2007-05-12 22:04 ` Eric W. Biederman
2007-05-12 22:08 ` H. Peter Anvin
2007-05-11 4:37 ` Vivek Goyal
2007-05-11 23:58 ` Kevin Winchester
2007-05-12 0:23 ` H. Peter Anvin
2007-05-13 0:35 ` Kevin Winchester
2007-05-15 20:45 ` Rob Landley
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=m1mz09ritr.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=James.Bottomley@HansenPar \
--cc=Matt_Domsch@dell.com \
--cc=adaplas@gmail.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=heukelum@mailshack.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.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