linux-kernel - Re: [PATCH] [4/50] x86: add cpu codenames for Kconfig.cpu

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 21 Sep 2007 18:45:39 -0400
From:	Dave Jones <davej@...hat.com>
To:	Andi Kleen <ak@...e.de>
Cc:	oliver.pntr@...il.com, patches@...-64.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [4/50] x86: add cpu codenames for Kconfig.cpu

On Sat, Sep 22, 2007 at 12:32:02AM +0200, Andi Kleen wrote:


 > +	  Select this for:
 > +	    Pentiums (Pentium 4, Pentium D, Celeron, Celeron D) corename:
 > +		-Willamette
 > +		-Northwood
 > +		-Mobile Pentium 4
 > +		-Mobile Pentium 4 M
 > +		-Extreme Edition (Gallatin)
 > +		-Prescott
 > +		-Prescott 2M
 > +		-Cedar Mill
 > +		-Presler
 > +		-Smithfiled
 > +	    Xeons (Intel Xeon, Xeon MP, Xeon LV, Xeon MV) corename:
 > +	    	-Foster
 > +		-Prestonia
 > +		-Gallatin
 > +		-Nocona
 > +		-Irwindale
 > +		-Cranford
 > +		-Potomac
 > +		-Paxville
 > +		-Dempsey

This seems like yet another list that will need to be perpetually
kept up to date, and given 99% of users don't know the codename
of their core, just the marketing name, I question its value.

 > +	  more info: http://balusc.xs4all.nl/srv/har-cpu.html
 
This URL is dead already.

 >  config MPSC
 >         bool "Intel P4 / older Netburst based Xeon"
 >         help

sidenote: I always wondered what 'PSC' stood for ?

	Dave

-- 
http://www.codemonkey.org.uk
-
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/