From: Stan Bubrouski <stan@ccs.neu.edu>
To: Jamie Lokier <jamie@shareable.org>
Cc: Jim Houston <jim.houston@comcast.net>,
linux-kernel@vger.kernel.org, jim.houston@ccur.com
Subject: Re: [PATCH] Pentium Pro - sysenter - doublefault
Date: Wed, 27 Aug 2003 11:15:50 -0400 [thread overview]
Message-ID: <3F4CCB26.3020408@ccs.neu.edu> (raw)
In-Reply-To: <20030827140121.GA1973@mail.jlokier.co.uk>
Jamie Lokier wrote:
<SNIP>
> I expect it to do the first of these which is applicable:
>
> - raise SIGILL on Pentium and earlier Intel CPUs
> - raise SIGILL on non-Intel CPUs which don't have the SEP capability
> - raise SIGSEGV on Pentium Pro CPUs
> - raise SIGSEGV on Pentium II CPUs with model == 3 and stepping < 3
> - raise SIGSEGV on 2.4 kernels
> - exit with status 0 on 2.6 kernels
>
> Enjoy,
> -- Jamie
As expected I get a SIGILL on P166 with 2.4.22
-sb
-----------------------------------------------
The price of freedom? Ask your Senator how much
the RIAA gave him for his Lexus.
next prev parent reply other threads:[~2003-08-27 15:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 20:41 [PATCH] Pentium Pro - sysenter - doublefault 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
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 [this message]
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=3F4CCB26.3020408@ccs.neu.edu \
--to=stan@ccs.neu.edu \
--cc=jamie@shareable.org \
--cc=jim.houston@ccur.com \
--cc=jim.houston@comcast.net \
--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