From: Adrian Bunk <bunk@fs.tum.de>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: TSCs are a no-no on i386
Date: Wed, 30 Jul 2003 20:45:29 +0200 [thread overview]
Message-ID: <20030730184529.GE21734@fs.tum.de> (raw)
In-Reply-To: <20030730183033.GA970@matchmail.com>
On Wed, Jul 30, 2003 at 11:30:33AM -0700, Mike Fedyk wrote:
> On Wed, Jul 30, 2003 at 08:10:06PM +0200, Adrian Bunk wrote:
> > On Wed, Jul 30, 2003 at 03:56:23PM +0200, Jan-Benedict Glaw wrote:
> > >...
> > > Please apply. Worst to say, even Debian seems to start using i486+
> > > features (ie. libstdc++5 is SIGILLed on Am386 because there's no
> > > "lock" insn available)...
> >
> > Shouldn't the 486 emulation in the latest 386 kernel images in Debian
> > unstable take care of this?
>
> What emulation?
486 emulation
CONFIG_CPU_EMU486
When used on a 386, Linux can emulate 3 instructions from the 486 set.
This allows user space programs compiled for 486 to run on a 386
without crashing with a SIGILL. As any emulation, performance will be
very low, but since these instruction are not often used, this might
not hurt. The emulated instructions are:
- bswap (does the same as htonl())
- cmpxchg (used in multi-threading, mutex locking)
- xadd (rarely used)
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!
Although it's highly preferable that you only execute programs targetted
for your CPU, it may happen that, consecutively to a hardware replacement,
or during rescue of a damaged system, you have to execute such programs
on an inadapted processor. In this case, this option will help you get
your programs working, even if they will be slower.
It is recommended that you say N here in any case, except for the
kernels that you will use on your rescue disks.
This option should not be left on by default, because it means that
you execute a program not targetted for your CPU. You should recompile
your applications whenever possible.
If you are not sure, say N.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-07-30 18:45 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 [this message]
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
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=20030730184529.GE21734@fs.tum.de \
--to=bunk@fs.tum.de \
--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;
as well as URLs for NNTP newsgroup(s).