From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Jiri Kosina <jkosina@suse.cz>, Adam Osuchowski <adwol@zonk.pl>,
linux-kernel@vger.kernel.org, Nick Piggin <npiggin@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Is 386 processor still supported?
Date: Thu, 15 Jan 2009 15:20:47 +0100 [thread overview]
Message-ID: <20090115142047.GV11087@lug-owl.de> (raw)
In-Reply-To: <alpine.LFD.1.10.0901151353530.5737@ftp.linux-mips.org>
[-- Attachment #1: Type: text/plain, Size: 2056 bytes --]
On Thu, 2009-01-15 14:15:56 +0000, Maciej W. Rozycki <macro@linux-mips.org> wrote:
> On Thu, 15 Jan 2009, Alan Cox wrote:
> > > UP emulation of CMPXCHG and XADD for userland should be rather trivial,
> > > so why not include it like with LL/SC for MIPS?
> >
> > Why not just ship an additional libc with the right options ?
>
> Does not work for MIPS as glibc has no equivalent code for pre-LL/SC CPUs
> and LL/SC is always used. For the i386 the situation seems worse yet as
> for pre-i486 CPUs a generic C implementation of compare-and-exchange is
> used guaranteeing silent thread unsafety. :(
>
> IMO, a kernel emulation of CMPXCHG and XADD (both are used by
> sysdeps/i386/i486/bits/atomic.h in glibc) with an optional LOCK prefix,
> guaranteeing UP atomicity would be a cheap way to provide long-term i386
> userland support with little burden for both Linux and respective user
> software maintainers. Certainly it adds some bloat to the kernel, but I
> think it is not an option that should be outright dismissed without
> consideration.
I just searched for the old patch, but couldn't find it ad hoc. (But
it must be somewhere, at least in the archives, I guess?)
The kernel emulator has the benefit of no overhead when not switched
on, and low-to-no overhead when not being used (i386 capable kernel on
i486 hardware).
Heck, I'd dig out my two test systems and give them a try with current
Debian unstable. Should be fun with four to eight megabytes of RAM.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de +49-172-7608481
Signature of: 23:53 <@jbglaw> So, ich kletter' jetzt mal ins Bett.
the second : 23:57 <@jever2> .oO( kletter ..., hat er noch Gitter vorm Bett, wie früher meine Kinder?)
00:00 <@jbglaw> jever2: *patsch*
00:01 <@jever2> *aua*, wofür, Gedanken sind frei!
00:02 <@jbglaw> Nee, freie Gedanken, die sind seit 1984 doch aus!
00:03 <@jever2> 1984? ich bin erst seit 1985 verheiratet!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-01-15 14:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 12:03 Is 386 processor still supported? Adam Osuchowski
2009-01-08 13:05 ` Jiri Kosina
2009-01-08 13:24 ` Cyrill Gorcunov
2009-01-08 13:48 ` Jiri Kosina
2009-01-08 14:13 ` Peter Zijlstra
2009-01-08 14:21 ` Jiri Kosina
2009-01-08 14:27 ` Peter Zijlstra
2009-01-08 15:04 ` Alan Cox
2009-01-08 15:10 ` Ingo Molnar
2009-01-13 1:06 ` Maciej W. Rozycki
2009-01-15 12:36 ` Jan-Benedict Glaw
2009-01-15 13:22 ` Maciej W. Rozycki
2009-01-15 13:32 ` Alan Cox
2009-01-15 14:15 ` Maciej W. Rozycki
2009-01-15 14:17 ` Ingo Molnar
2009-01-16 9:00 ` Pavel Machek
2009-01-16 10:13 ` Jan-Benedict Glaw
2009-01-16 11:18 ` Andrey Panin
2009-01-16 13:46 ` Ingo Molnar
2009-01-16 18:17 ` H. Peter Anvin
2009-01-15 14:20 ` Jan-Benedict Glaw [this message]
2009-01-15 14:37 ` Bastien ROUCARIES
2009-01-15 14:25 ` Alan Cox
2009-01-15 14:44 ` Maciej W. Rozycki
2009-01-15 20:11 ` H. Peter Anvin
2009-01-15 14:46 ` Jan-Benedict Glaw
2009-01-08 16:45 ` Sam Ravnborg
2009-01-08 16:27 ` Andi Kleen
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=20090115142047.GV11087@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=adwol@zonk.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.