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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sat, 22 Sep 2007 10:40:07 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Dave Jones <davej@...hat.com>
Cc:	Sam Ravnborg <sam@...nborg.org>, Andi Kleen <ak@...e.de>,
	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, 22 Sep 2007 10:23:25 -0400 Dave Jones wrote:

> On Sat, Sep 22, 2007 at 08:57:24AM +0200, Sam Ravnborg wrote:
> 
>  > > 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.
>  > 
>  > As a bare minimum requirement the list presented here shall use same
>  > names as used in /proc/cpuinfo
>  > 
>  > On this box I read:
>  > 
>  > vendor_id	: GenuineIntel
>  > model name	: Pentium III (Coppermine)
> 
> There are *dozens* of possible entries here, and always new ones.
> The list will become so cumbersome that searching for the name
> through the help text of each possible option will become a
> really boring task, that I doubt anyone will seriously do.

Yep.  help text:  see www.wikipedia.org :)

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
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/