mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jim Houston <jim.houston@comcast.net>
To: Jamie Lokier <jamie@shareable.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Pentium Pro - sysenter - doublefault
Date: 25 Aug 2003 14:15:12 -0400	[thread overview]
Message-ID: <1061835311.12585.46.camel@new.localdomain> (raw)
In-Reply-To: <20030825062905.GA21262@mail.jlokier.co.uk>

On Mon, 2003-08-25 at 02:29, Jamie Lokier wrote:
> Jamie Lokier wrote:
> > So that means the sysenter instruction _does_ exist on the PPro and
> > early Pentium II, but it isn't usable.
> 
> If anyone has information on what the SYSENTER and SYSEXIT
> instructions actually do on Intel Pentium Pro or stepping<3 Pentium II
> processors, I am very interested.
> 
> I'm intrigued to know if the buggy behaviour of these instructions is
> really unsafe, or simply hard to use so Intel changed the behaviour.
> (An example of hard to use would be SYSENTER not disabling
> interrupts).  If they are safe but hard to use, perhaps the ingenuity
> of kernel hackers can work around the hardness >:)

Hi Jamie,

I tried your test on my machine.  It fails with a segmentation
fault.  I noticed that the Pentium II specifications update manual
starts with rev C0 stepping (ignoring mask rev < 3).
I'm inclined to forgive Intel for not publishing the scary errata that
goes with the first few mask revs, particularly for an old product.

When I was chasing the original problem, I added tracing code 
(compiling the kernel with finstrument-functions) so that when I
got into kgdb after the double-fault I could see that it had just
completed a umask system call.  I'm assuming that it failed on
the sysexit.

I keep the old Pentium Pro around because it has an NMI interrupt
button.

I'm happy that Linus has merged the fix to disable correctly
disable sysenter for these machines.

Jim Houston - Concurrent Computer Corp


  parent reply	other threads:[~2003-08-25 18:08 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
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 [this message]
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=1061835311.12585.46.camel@new.localdomain \
    --to=jim.houston@comcast.net \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    /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®