From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Adrian Bunk <bunk@fs.tum.de>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: TSCs are a no-no on i386
Date: Wed, 6 Aug 2003 16:33:14 +0200 (MET DST) [thread overview]
Message-ID: <Pine.GSO.3.96.1030806162050.26399A-100000@delta.ds2.pg.gda.pl> (raw)
In-Reply-To: <20030806110855.GA583@elf.ucw.cz>
On Wed, 6 Aug 2003, Pavel Machek wrote:
> > > Note that this can also allow Step-A 486's to correctly run multi-thread
> > > applications since cmpxchg has a wrong opcode on this early CPU.
> > >
> > > Don't use this to enable multi-threading on an SMP machine, the lock
> > > atomicity can't be guaranted!
> >
> > That is of course the other problem with this approach - you can't
> > really get the intended results without some extremely heavyweight code
> > (using an IPI to halt all CPU's, doing the access and then resuming
> > them)
>
> Hopefully there are not too many SMP-486 machines out there ;-).
Step-A i486 processors are supposedly very rare and they were the
earliest ones (predating the DX suffix), so they were probably never used
for SMP systems. And I think the i82489DX APIC was introduced a bit later
anyway -- we don't support non-APIC SMP implementations.
BTW, the step-A i486 reused opcodes of the famous i386's ibts and xbts
instructions. Once the chips were out, Intel discovered there is actually
some software out there expecting ibts/xbts semantics with these opcodes,
so the encoding of cmpxchg was quickly changed. ;-)
--
+ Maciej W. Rozycki, Technical University of Gdansk, Poland +
+--------------------------------------------------------------+
+ e-mail: macro@ds2.pg.gda.pl, PGP key available +
next prev parent reply other threads:[~2003-08-06 14:36 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 13:56 TSCs are a no-no on i386 Jan-Benedict Glaw
2003-07-30 14:18 ` Maciej W. Rozycki
2003-07-30 14:44 ` Jan-Benedict Glaw
2003-07-30 16:58 ` Matthew Garrett
2003-07-30 17:19 ` Alan Cox
2003-07-30 18:10 ` Adrian Bunk
2003-07-30 18:30 ` Mike Fedyk
2003-07-30 18:45 ` Adrian Bunk
2003-07-30 20:01 ` Alan Cox
2003-07-30 20:33 ` Jan-Benedict Glaw
2003-07-30 22:19 ` J.A. Magallon
2003-07-31 6:11 ` Jan-Benedict Glaw
2003-07-30 23:05 ` Alan Cox
2003-07-31 11:11 ` Richard B. Johnson
2003-07-31 11:26 ` Emulating i486+ insn on i386 (was: TSCs are a no-no on i386) Jan-Benedict Glaw
2003-07-31 11:41 ` TSCs are a no-no on i386 Jan-Benedict Glaw
2003-07-31 0:22 ` Adrian Bunk
2003-07-31 6:22 ` Jan-Benedict Glaw
2003-07-31 7:17 ` Willy Tarreau
2003-07-31 11:38 ` Emulating i486 on i386 (was: TSCs are a no-no on i386) Jan-Benedict Glaw
2003-07-31 11:51 ` Alan Cox
2003-07-31 12:14 ` Jan-Benedict Glaw
2003-07-31 13:01 ` Jan-Benedict Glaw
2003-07-31 15:09 ` Martin Schlemmer
2003-07-31 15:33 ` Jan-Benedict Glaw
2003-08-01 5:37 ` Martin Schlemmer
2003-07-31 15:12 ` Jamie Lokier
2003-07-31 15:32 ` Jan-Benedict Glaw
2003-07-31 15:07 ` TSCs are a no-no on i386 Jamie Lokier
2003-07-31 15:23 ` Willy Tarreau
2003-07-31 15:50 ` Richard B. Johnson
2003-07-31 16:24 ` Jan-Benedict Glaw
2003-08-06 11:08 ` Pavel Machek
2003-08-06 14:33 ` Maciej W. Rozycki [this message]
2003-07-30 20:28 ` Jan-Benedict Glaw
2003-07-30 21:50 ` Petr Vandrovec
2003-07-30 23:10 ` Alan Cox
2003-07-31 15:10 ` Jamie Lokier
2003-07-31 16:01 ` Alan Cox
2003-07-31 18:37 ` Jamie Lokier
2003-07-31 19:10 ` Alan Cox
2003-07-31 6:29 ` Jan-Benedict Glaw
2003-07-30 20:27 ` Jan-Benedict Glaw
2003-08-06 16:41 James Bottomley
2003-08-06 16:45 James Bottomley
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=Pine.GSO.3.96.1030806162050.26399A-100000@delta.ds2.pg.gda.pl \
--to=macro@ds2.pg.gda.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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;
as well as URLs for NNTP newsgroup(s).