public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Richter <robert.richter@amd.com>
To: John Villalovos <sodarock@gmail.com>
Cc: "andi@firstfloor.org" <andi@firstfloor.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"oprofile-list@lists.sf.net" <oprofile-list@lists.sf.net>
Subject: Re: [PATCH V2] Oprofile: Change CPUIDS from decimal to hex, and add some comments
Date: Mon, 10 May 2010 14:33:52 +0200	[thread overview]
Message-ID: <20100510123352.GF6450@erda.amd.com> (raw)
In-Reply-To: <20100507164140.GA6128@linuxjohn.usersys.redhat.com>

On 07.05.10 12:41:40, John Villalovos wrote:
> Version 2:
> 
> Incorporating suggested changes from Robert Richter.
> 
> Back when the patch was submitted for "Add Xeon 7500 series support to
> oprofile", Robert Richter had asked for a followon patch that converted all the
> CPU ID values to hex.
> 
> I have done that here for the "i386/core_i7" and "i386/atom" class
> processors in the ppro_init() function and also added some comments on
> where to find documentation on the Intel processors.
> 
> Signed-off-by: John L. Villalovos <john.l.villalovos@intel.com>
> 
> diff --git a/arch/x86/oprofile/nmi_int.c b/arch/x86/oprofile/nmi_int.c
> index 9f001d9..2de5f44 100644
> --- a/arch/x86/oprofile/nmi_int.c
> +++ b/arch/x86/oprofile/nmi_int.c
> @@ -586,6 +586,13 @@ static int __init ppro_init(char **cpu_type)
>  	if (force_arch_perfmon && cpu_has_arch_perfmon)
>  		return 0;
>  
> +	/* Documentation on identifying Intel processors by CPU Family and Model
> +	 * can be found in the Intel Software Developer's Manual (SDM).
> +	 * http://www.intel.com/products/processor/manuals/
> +	 * As of May 2010 the documentation for this was in the:
> +	 * "Intel 64 and IA-32 Architectures Software Developer's Manual Volume
> +	 * 3B: System Programming Guide",
> +	 * "Table B-1 CPUID Signature Values of DisplayFamily_DisplayModel" */
>  	switch (cpu_model) {
>  	case 0 ... 2:
>  		*cpu_type = "i386/ppro";

Patch applied, thanks John. I made some small style changes to your
comment:

       /*
        * Documentation on identifying Intel processors by CPU family
        * and model can be found in the Intel Software Developer's
        * Manuals (SDM):
        *
        *  http://www.intel.com/products/processor/manuals/
        *
        * As of May 2010 the documentation for this was in the:
        * "Intel 64 and IA-32 Architectures Software Developer's
        * Manual Volume 3B: System Programming Guide", "Table B-1
        * CPUID Signature Values of DisplayFamily_DisplayModel".
        */

-Robert

-- 
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@amd.com


      reply	other threads:[~2010-05-10 12:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07 16:41 [PATCH V2] Oprofile: Change CPUIDS from decimal to hex, and add some comments John Villalovos
2010-05-10 12:33 ` Robert Richter [this message]

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=20100510123352.GF6450@erda.amd.com \
    --to=robert.richter@amd.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oprofile-list@lists.sf.net \
    --cc=sodarock@gmail.com \
    --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