From: Andi Kleen <andi@firstfloor.org>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org, mingo@redhat.com,
tglx@linutronix.de
Subject: Re: [PATCH] fix i486 boot failure due to stale %ds
Date: Mon, 05 Nov 2007 00:05:48 +0100 [thread overview]
Message-ID: <p733avl392r.fsf@bingen.suse.de> (raw)
In-Reply-To: <200711042158.lA4Lwv9S014628@harpo.it.uu.se> (Mikael Pettersson's message of "Sun\, 4 Nov 2007 22\:58\:57 +0100 \(MET\)")
Mikael Pettersson <mikpe@it.uu.se> writes:
> Maybe not. I had a look in Intel's SDM Vol3, and the
> section "switching to protected mode" specifies that
> a move to %cr0 that sets PE should immediately be
> followed by a far jmp or call. They write that "random
> failures can occur if other instructions exist between
> [the move to %cr0] and [the far jmp/call]". The current
> version of pmjump.S does exactly that: it executes
> a bunch of moves to segment registers in that window.
iirc various Intel VT hypervisor implementations also have trouble
with not following this restriction. At least in the early Xen
days it was a frequent reason for boot failure.
-Andi
next prev parent reply other threads:[~2007-11-04 23:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 21:58 [PATCH] fix i486 boot failure due to stale %ds Mikael Pettersson
2007-11-04 22:20 ` H. Peter Anvin
2007-11-04 23:05 ` Andi Kleen [this message]
2007-11-04 23:07 ` Jeremy Fitzhardinge
2007-11-04 23:12 ` H. Peter Anvin
2007-11-04 23:50 ` H. Peter Anvin
2007-11-05 0:15 ` Linus Torvalds
2007-11-05 0:23 ` Linus Torvalds
2007-11-04 23:51 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2007-11-05 1:18 Mikael Pettersson
2007-11-04 19:38 Mikael Pettersson
2007-11-04 19:41 ` H. Peter Anvin
2007-11-04 16:44 Mikael Pettersson
2007-11-04 18:29 ` H. Peter Anvin
2007-11-04 19:00 ` H. Peter Anvin
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=p733avl392r.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=mingo@redhat.com \
--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