linux-kernel - Re: [git pull] x86 fixes

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: <20080908114619.741b6786@infradead.org>
Date:	Mon, 8 Sep 2008 11:46:19 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	x86 maintainers <x86@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] x86 fixes

On Mon, 08 Sep 2008 11:22:24 -0700
"H. Peter Anvin" <hpa@...or.com> wrote:

> 
> The "ideal" way to do any of this would probably to have checkboxes
> for all the CPUs you want to support and then a drop-down box for the
> CPU to optimize for.  However, the combinatorics of that would be
> horrible, and it would be very unlikely we would avoid bugs.

the ideal case would be "support them all"

the second-most ideal case would be "support all as of <year>" I suppose

a third one for advanced users not distros would be "support only
<vendor>" since that would be the biggest part of code to drop

between models of the same vendor.. not too much to win there.


-- 
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/