public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] x86: cpu/proc.c adding extended_cpuid_level for /proc/cpuinfo
Date: Wed, 10 Jun 2009 22:10:44 +0530	[thread overview]
Message-ID: <1244652044.3295.10.camel@ht.satnam> (raw)
In-Reply-To: <1244262225.2449.22.camel@ht.satnam>

Hello Peter,

On Sat, 2009-06-06 at 09:53 +0530, Jaswinder Singh Rajput wrote:
> 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.
> 

                                              Highest Value in EAX
 Intel 64 or IA-32 Processors   Basic Information             Extended Function
                                                                 Information
Earlier Intel486 Processors   CPUID Not Implemented       CPUID Not Implemented
Later Intel486 Processors and          01H                     Not Implemented
Pentium Processors
Pentium Pro and Pentium II             02H                     Not Implemented
Processors, Intel Celeron
Processors
Pentium III Processors                 03H                     Not Implemented
Pentium 4 Processors                   02H                       80000004H
Intel Xeon Processors                  02H                       80000004H
Pentium M Processor                    02H                       80000004H
Pentium 4 Processor                    05H                       80000008H
supporting Hyper-Threading
Technology
Pentium D Processor (8xx)              05H                       80000008H
Pentium D Processor (9xx)              06H                       80000008H
Intel Core Duo Processor               0AH                       80000008H
Intel Core 2 Duo Processor             0AH                       80000008H
Intel Xeon Processor 3000,             0AH                       80000008H
5100, 5200, 5300, 5400
Series
Intel Core 2 Duo Processor             0DH                       80000008H
8000 Series
Intel Xeon Processor 5200,             0AH                       80000008H
5400 Series
Intel Atom Processor                   0AH                       80000008H
Intel Core i7 Processor                0BH                       80000008H

cpuid level and extended cpuid level tells the information about Intel
processor model.
Do you still think it is useless and should not be present
in /proc/cpuinfo .

Thanks,
--
JSR


  reply	other threads:[~2009-06-10 16:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12  7:14 [PATCH -tip] x86: cpu/proc.c adding extended_cpuid_level for /proc/cpuinfo Jaswinder Singh Rajput
2009-05-12 13:39 ` Borislav Petkov
2009-05-12 13:49   ` Jaswinder Singh Rajput
2009-05-12 14:10     ` Borislav Petkov
2009-05-12 16:40       ` H. Peter Anvin
2009-05-12 18:13         ` Borislav Petkov
2009-05-12 18:47           ` H. Peter Anvin
2009-05-12 19:49             ` Borislav Petkov
2009-06-05 19:20         ` Jaswinder Singh Rajput
2009-05-13  6:21 ` Andrew Morton
2009-05-13  8:03   ` Andi Kleen
2009-06-05 18:38   ` Jaswinder Singh Rajput
2009-06-05 20:55     ` H. Peter Anvin
2009-06-06  4:23       ` Jaswinder Singh Rajput
2009-06-10 16:40         ` Jaswinder Singh Rajput [this message]
2009-06-10 17:14           ` H. Peter Anvin
2009-06-10 17:42             ` Borislav Petkov
2009-06-10 17:48               ` H. Peter Anvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1244652044.3295.10.camel@ht.satnam \
    --to=jaswinder@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox