linux-kernel - Re: Is 386 processor still supported?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090115144651.GZ11087@lug-owl.de>
Date:	Thu, 15 Jan 2009 15:46:51 +0100
From:	Jan-Benedict Glaw <jbglaw@...-owl.de>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	"Maciej W. Rozycki" <macro@...ux-mips.org>,
	Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <peterz@...radead.org>,
	Jiri Kosina <jkosina@...e.cz>, Adam Osuchowski <adwol@...k.pl>,
	linux-kernel@...r.kernel.org, Nick Piggin <npiggin@...e.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: Is 386 processor still supported?

On Thu, 2009-01-15 13:32:52 +0000, Alan Cox <alan@...rguk.ukuu.org.uk> 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 ?

Due to another historic bug, which created libcs targeted for i386
containing the locking code for i486, as I was told back when I first
showed interest for real i386 hardware.

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw@...-owl.de              +49-172-7608481
Signature of:                 Friends are relatives you make for yourself.
the second  :

Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)