linux-kernel - Re: [PATCH -tip] x86: cpu/proc.c adding extended_cpuid

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: <878wl1mntw.fsf@basil.nowhere.org>
Date:	Wed, 13 May 2009 10:03:39 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Jaswinder Singh Rajput <jaswinder@...nel.org>,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -tip] x86: cpu/proc.c adding extended_cpuid_level for /proc/cpuinfo

Andrew Morton <akpm@...ux-foundation.org> writes:

> On Tue, 12 May 2009 12:44:42 +0530 Jaswinder Singh Rajput <jaswinder@...nel.org> wrote:
>
>> +		   "ext cpuid level\t: 0x%x\n"
>
> It's unobvious what "ext" means.  External?
>
> Can we make it "extended cpuid level"?
>
> One would hope that google(extended cpuid level) tells you what an
> extended cpuid level is, but alas, unclear.

AMD has an own cpuid range in 0x8000_0000+. But it's only useful
if you actually access it using cpuid. Everyone who needs it 
already needs to call cpuid and if they do that they 
can as well retrieve it by themselves.

Without accessing CPUID it has no value at whatsoever. It would
also seem pretty dumb to spend a few thousand cycles getting
it from the kernel when you can as well get it directly
from CPUID and you need to have that code anyways.

The useful information in 8000_0000+ is all reported by the kernel 
anyways. 

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/