All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Eric W. Biederman" <ebiederm@xmission.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 15:08:45 -0700	[thread overview]
Message-ID: <46463AED.5060800@zytor.com> (raw)
In-Reply-To: <m1iraxr95g.fsf@ebiederm.dsl.xmission.com>

Eric W. Biederman wrote:
> Ok.  If you have tested on a wide variety of machines then I won't
> worry about it.
> 
> I guess if a cr0 write has always been synchronizing things should be
> a safe practice.  The practical danger is if you write to cr0 and the
> pipeline is not flushed and the segment loads might execute as 16bit
> mode segment register loads.  I think this is more of a 486 or 586/Pentium
> danger actually then a 386 one.

Writes to CR0 are synchronizing and are documented as such.  This is a
fairly trivial consequence of it invoking microcode on every x86 ever
created.

> Hmm. I'm not certain about enabling protected mode but enabling paging
> at least does appear to be documented to require a jump, before the P6
> core.  Which may be why it is recommended for initializing protected
> mode.

Enabling paging is possibly a different matter.  I can't speak on that
particular subject with any authority.

	-hpa

  reply	other threads:[~2007-05-12 22:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09  5:15 x86 setup rewrite tree ready for flamage^W review 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
2007-05-12 18:59                 ` H. Peter Anvin
2007-05-12 22:04                   ` Eric W. Biederman
2007-05-12 22:08                     ` H. Peter Anvin [this message]
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=46463AED.5060800@zytor.com \
    --to=hpa@zytor.com \
    --cc=James.Bottomley@HansenPar \
    --cc=Matt_Domsch@dell.com \
    --cc=adaplas@gmail.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=heukelum@mailshack.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 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.