| 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
| ||
|
Date: Tue, 12 May 2009 17:57:02 +0200 From: Nick Piggin <npiggin@...e.de> To: "H. Peter Anvin" <hpa@...or.com> Cc: Jan Beulich <JBeulich@...ell.com>, Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org Subject: Re: uses of cmpxchg/xadd in spinlock.h and rwsem.h vs. CONFIG_M386 On Tue, May 12, 2009 at 08:51:12AM -0700, H. Peter Anvin wrote: > Jan Beulich wrote: > > While looking at a completely different issue I happened to grep for uses of > > xadd, and it would appear to me that there got uses added that would make > > a M386-configured SMP kernel die on an actual i386. > > > > Oh, for the rwsem case I see - it would use the RWSEM_GENERIC_SPINLOCK case > > when selecting M386. But I see nothing similar for the ticket spinlocks - am > > I overlooking something? > > It's quite possible we break 386 on a regular basis... I'm not sure how > many people even in the embedded industry run current kernels on > 386-compatible hardware. Most embedded hardware is at least 486. Is it time to get rid of attempts to support SMP kernels that run on 386, then? Considering we don't actually support SMP 386, and if there is any 386 systems then they're going to be running custom kernels anyway. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists