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: <4A29862D.6030601@zytor.com>
Date:	Fri, 05 Jun 2009 13:55:09 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jaswinder Singh Rajput <jaswinder@...nel.org>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>, 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

Jaswinder Singh Rajput wrote:
> Hello Andrew,
> 
> On Tue, 2009-05-12 at 23:21 -0700, Andrew Morton wrote:
>> 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"?
> 
> extended cpuid level will look like this :
> 
> fpu		: yes
> fpu_exception	: yes
> cpuid level	: 5
> wp		: yes
> extended cpuid level: 0x80000008
> flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe constant_tsc pebs bts pni dtes64 monitor ds_cpl cid
> 

The more I'm thinking about this I think it was a mistake to put cpuid
level: there in the first place, too.  My opinion is increasingly to
leave this to x86info or other user-space tools.

	-hpa
--
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/