From: Pavel Machek <pavel@suse.cz>
To: Jamie Lokier <jamie@shareable.org>
Cc: Mikael Pettersson <mikpe@csd.uu.se>,
jim.houston@comcast.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Pentium Pro - sysenter - doublefault
Date: Wed, 3 Sep 2003 14:50:20 +0200 [thread overview]
Message-ID: <20030903125019.GN1358@openzaurus.ucw.cz> (raw)
In-Reply-To: <20030825060900.GA21213@mail.jlokier.co.uk>
Hi!
> > I double-checked AP-485 (24161823.pdf, the "real" reference to CPUID),
> > and it says (section 3.4) that SEP is unsupported when the signature
> > as a whole is less that 0x633. This means all PPros, and PII Model 3s
> > with steppings less than 3.
>
> "SEP is unsupported". It's interesting that Pentium Pro erratum #82
> is "SYSENTER/SYSEXIT instructions can implicitly load 'null segment
> selector' to SS and CS registers", implying that SYSENTER does
> _something_ useful on PPros.
Well, with CS==0 machine is not going to survive too long.
If it only happens sometimes you might catch the double fault
and fixup, but....
Pavel
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
next prev parent reply other threads:[~2003-09-08 13:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 20:41 Jim Houston
2003-08-21 21:32 ` Mikael Pettersson
2003-08-22 2:18 ` [PATCH2] " Jim Houston
2003-08-25 5:56 ` [PATCH] " Jamie Lokier
2003-08-25 6:09 ` Jamie Lokier
2003-09-03 12:50 ` Pavel Machek [this message]
2003-09-08 14:05 ` Jamie Lokier
2003-08-25 4:05 ` Jamie Lokier
2003-08-25 4:14 ` Jakob Oestergaard
2003-08-25 5:50 ` Jamie Lokier
2003-08-25 6:29 ` Jamie Lokier
2003-08-25 7:49 ` Jakob Oestergaard
2003-08-25 18:15 ` Jim Houston
2003-08-26 12:26 ` Richard Curnow
2003-08-27 14:01 ` Jamie Lokier
2003-08-27 14:23 ` Richard Curnow
2003-08-27 14:25 ` dl-ipaddr
2003-08-27 15:15 ` Stan Bubrouski
2003-08-27 16:02 ` Pasi Savolainen
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=20030903125019.GN1358@openzaurus.ucw.cz \
--to=pavel@suse.cz \
--cc=jamie@shareable.org \
--cc=jim.houston@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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
all inboxes | Powered by JetHome®