lkml.org 
[lkml]   [2009]   [Jun]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH -tip] x86: cpu/proc.c adding extended_cpuid_level for /proc/cpuinfo
From
Date
On Fri, 2009-06-05 at 13:55 -0700, H. Peter Anvin wrote:
> 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@kernel.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.
>

cpuid level is as important as cpu family, model and stepping.

For Intel, in some cases cpuid level is more important then cpu family,
model and stepping. Like you cannot tell by looking at cpu family, model
and stepping which model is new and which is old like 05_01 or 06_1A or
0F_03H ?

But by looking at cpuid level and extended cpuid level you can tell
which is new and which is old and which supports more features.

So cpuid level and extended cpuid level is better scale than cpu family,
model and stepping. So I think hiding this valuable information is a
crime.

Thanks,
--
JSR




\
 
 \ /
  Last update: 2009-06-06 06:25    [W:0.082 / U:0.148 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site