linux-kernel - Re: [RFC 00/15] x86_64: Optimize percpu accesses

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]

Date:	Wed, 9 Jul 2008 23:12:56 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Mike Travis <travis@....com>
Cc:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Christoph Lameter <cl@...ux-foundation.org>,
	Jack Steiner <steiner@....com>, linux-kernel@...r.kernel.org
Subject: Re: [RFC 00/15] x86_64: Optimize percpu accesses

* Mike Travis <travis@....com> wrote:

> After that is taken care of, I'll start regression testing earlier 
> compilers. I think someone mentioned that gcc-2.something was the 
> minimum required...?

i think the current official minimum is around gcc-3.2 [2.x is out of 
question because we have a few feature dependencies on gcc-3.x] - but i 
stopped using it because it miscompiles the kernel so often. 4.0 was 
really bad due to large stack footprint. The 4.3.x series miscompiles 
the kernel too in certain situations - there was a high-rising 
kerneloops.org crash recently in ext3.

So in general, 'too new' is bad because it has new regressions, 'too 
old' is bad because it has unfixed old regressions. Somewhere in the 
middle, 4.2.x-ish, seems to be pretty robust in practice.

	Ingo
--
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/