From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: "Yan, Zheng" <zheng.z.yan@intel.com>
Cc: eranian@google.com, mingo@elte.hu, andi@firstfloor.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 5/5] perf/x86: Add Intel Nehalem-EX uncore support
Date: Tue, 10 Jul 2012 14:17:01 +0200 [thread overview]
Message-ID: <1341922621.3462.130.camel@twins> (raw)
In-Reply-To: <4FF534F1.3030307@intel.com>
On Thu, 2012-07-05 at 14:32 +0800, Yan, Zheng wrote:
> The uncore subsystem in Nehalem-EX consists of 7 components
> (U-Box, C-Box, B-Box, S-Box, R-Box, M-Box and W-Box). This
> patch is large because the way to program these boxes is
> diverse.
>
Thanks, I added the below little delta.
Did you manage to fix that SNB-EP crash already?
Also, should we be adding 58 (IVB) to the SNB uncore? The SDM states it
should all be the same programming wise.
---
--- a/arch/x86/kernel/cpu/perf_event_intel_uncore.c
+++ b/arch/x86/kernel/cpu/perf_event_intel_uncore.c
@@ -893,7 +893,7 @@ static struct attribute_group nhmex_unco
static struct intel_uncore_type nhmex_uncore_cbox = {
.name = "cbox",
.num_counters = 6,
- .num_boxes = 8,
+ .num_boxes = 10,
.perf_ctr_bits = 48,
.event_ctl = NHMEX_C0_MSR_PMON_EV_SEL0,
.perf_ctr = NHMEX_C0_MSR_PMON_CTR0,
@@ -2806,9 +2806,9 @@ static int __init uncore_cpu_init(void)
max_cores = boot_cpu_data.x86_max_cores;
switch (boot_cpu_data.x86_model) {
case 26: /* Nehalem */
- case 30:
+ case 30: /* Nehalem-EP */
case 37: /* Westmere */
- case 44:
+ case 44: /* Westmere-EP */
msr_uncores = nhm_msr_uncores;
break;
case 42: /* Sandy Bridge */
@@ -2821,7 +2821,10 @@ static int __init uncore_cpu_init(void)
snbep_uncore_cbox.num_boxes = max_cores;
msr_uncores = snbep_msr_uncores;
break;
- case 46:
+ case 46: /* Nehalem-EX */
+ case 47: /* Westmere-EX aka. Xeon E7 */
+ if (nhmex_uncore_cbox.num_boxes > max_cores)
+ nhmex_uncore_cbox.num_boxes = max_cores;
msr_uncores = nhmex_msr_uncores;
break;
default:
next prev parent reply other threads:[~2012-07-10 12:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 6:00 [PATCH 0/5] perf/x86: Uncore updates Yan, Zheng
2012-07-04 6:00 ` [PATCH 1/5] perf/x86: Use 0xff as pseudo code for fixed uncore event Yan, Zheng
2012-07-04 6:00 ` [PATCH 2/5] perf/x86: Fix event constraint for SandyBridge-EP CBox Yan, Zheng
2012-07-04 6:00 ` [PATCH 3/5] perf/x86: Detect number of instances of uncore CBox Yan, Zheng
2012-07-06 6:32 ` [tip:perf/core] " tip-bot for Yan, Zheng
2012-07-04 6:00 ` [PATCH 4/5] perf/x86: Uncore filter support for SandyBridge-EP Yan, Zheng
2012-07-06 6:33 ` [tip:perf/core] " tip-bot for Yan, Zheng
2012-07-22 19:25 ` [PATCH 4/5] " Stephane Eranian
2012-07-04 6:00 ` [PATCH 5/5] perf/x86: Add Intel Nehalem-EX uncore support Yan, Zheng
2012-07-04 10:04 ` Peter Zijlstra
2012-07-04 16:00 ` Yan, Zheng
2012-07-04 16:53 ` Peter Zijlstra
2012-07-04 17:46 ` Yan, Zheng
2012-07-05 6:32 ` [PATCH V2 " Yan, Zheng
2012-07-05 14:51 ` Andi Kleen
2012-07-05 15:46 ` Yan, Zheng
2012-07-10 12:17 ` Peter Zijlstra [this message]
2012-07-11 2:06 ` Yan, Zheng
2012-07-11 9:57 ` Peter Zijlstra
2012-07-11 12:02 ` Yan, Zheng
2012-07-26 15:11 ` [tip:perf/core] " tip-bot for Yan, Zheng
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=1341922621.3462.130.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=zheng.z.yan@intel.com \
/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