All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: andi@firstfloor.org, Ingo Molnar <mingo@kernel.org>,
	linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: perf: hsw model numbers
Date: Wed, 11 Dec 2013 12:24:14 +0100	[thread overview]
Message-ID: <20131211112414.GA22034@pd.tnic> (raw)
In-Reply-To: <20131211103631.GJ13532@twins.programming.kicks-ass.net>

On Wed, Dec 11, 2013 at 11:36:31AM +0100, Peter Zijlstra wrote:
> Hi Andi,
> 
> arch/x86/kernel/cpu/perf_event_intel.c
> 
> 3a632cb229bfb (Andi Kleen       2013-06-17 17:36:48 -0700 2500)         case 60: /* Haswell Client */
> 3a632cb229bfb (Andi Kleen       2013-06-17 17:36:48 -0700 2501)         case 70:
> 3a632cb229bfb (Andi Kleen       2013-06-17 17:36:48 -0700 2502)         case 71:
> 3a632cb229bfb (Andi Kleen       2013-06-17 17:36:48 -0700 2503)         case 63:
> 0499bd867bd17 (Andi Kleen       2013-08-08 17:26:23 -0700 2504)         case 69:
> 
> Can you add comments with each model number describing what actual part
> it is?
> 
> Also, we seem to lack snb/ivb EX part numbers, are those already known?

Yeah, it would be nice if Intel generally documented that whole model
mapping somewhere. For example, I spent some serious time grepping and
searching the net what family 6, model 47 actually is.

I asked hpa at some point about such doc and he said, CPUID doc needs to
get updated.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2013-12-11 11:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 10:36 perf: hsw model numbers Peter Zijlstra
2013-12-11 11:24 ` Borislav Petkov [this message]
2013-12-11 18:53 ` Andi Kleen
2013-12-11 20:18   ` Peter Zijlstra

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=20131211112414.GA22034@pd.tnic \
    --to=bp@alien8.de \
    --cc=andi@firstfloor.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.