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

[Andi Kleen <ak@suse.de>]

On Saturday 22 September 2007 00:45:39 Dave Jones wrote:
> 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.

The problem is that it is hard to distingush Core2 based Xeons
from P4 based Xeons.

There won't be any new Pentium 4 cores so that list should be static.
But yes the C2 list is a little problematic. Will remove that
and just say "family 6" 

Perhaps we should just bit the bullet and add a "optimize for current 
CPU" option.

> 
>  > +	  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 ?

Prescott; the Intel codename for their first x86-64 core.
Rhymes with K8 which was AMD's codename for the same.

Admittedly MCORE2 doesn't fit the pattern, it should have 
been MMEROM. But then when the C2 support was implemented
the Marketing name was already known, which wasn't the case
with the others.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/