On Tue, Aug 13, 2013 at 8:29 AM, Yan, Zheng <[email protected]> wrote: > From: "Yan, Zheng" <[email protected]> > > This patch adds support for the SNB-EP PCU uncore PMU extra_sel_bit > (bit 21) which is missing from the documentation in Table-2.75 of > Intel Xeon Processor E5-2600 Product Family Uncore Performance > Monitoring Guide. It is referred to later in Table-2.81. Without > this selection bit explicitly enabled by the kernel, some events > such as COREx_TRANSITION_CYCLES do not count correctly. > > Signed-off-by: Yan, Zheng <[email protected]>
Reviewed-by: Stephane Eranian <[email protected]> > --- > arch/x86/kernel/cpu/perf_event_intel_uncore.c | 2 +- > arch/x86/kernel/cpu/perf_event_intel_uncore.h | 1 + > 2 files changed, 2 insertions(+), 1 deletion(-) > > diff --git a/arch/x86/kernel/cpu/perf_event_intel_uncore.c > b/arch/x86/kernel/cpu/perf_event_intel_uncore.c > index 6b8b9c9..e9696d8 100644 > --- a/arch/x86/kernel/cpu/perf_event_intel_uncore.c > +++ b/arch/x86/kernel/cpu/perf_event_intel_uncore.c > @@ -301,7 +301,7 @@ static struct attribute *snbep_uncore_cbox_formats_attr[] > = { > }; > > static struct attribute *snbep_uncore_pcu_formats_attr[] = { > - &format_attr_event.attr, > + &format_attr_event_ext.attr, > &format_attr_occ_sel.attr, > &format_attr_edge.attr, > &format_attr_inv.attr, > diff --git a/arch/x86/kernel/cpu/perf_event_intel_uncore.h > b/arch/x86/kernel/cpu/perf_event_intel_uncore.h > index 628500e..a80ab71 100644 > --- a/arch/x86/kernel/cpu/perf_event_intel_uncore.h > +++ b/arch/x86/kernel/cpu/perf_event_intel_uncore.h > @@ -117,6 +117,7 @@ > (SNBEP_PMON_CTL_EV_SEL_MASK | \ > SNBEP_PCU_MSR_PMON_CTL_OCC_SEL_MASK | \ > SNBEP_PMON_CTL_EDGE_DET | \ > + SNBEP_PMON_CTL_EV_SEL_EXT | \ > SNBEP_PMON_CTL_INVERT | \ > SNBEP_PCU_MSR_PMON_CTL_TRESH_MASK | \ > SNBEP_PCU_MSR_PMON_CTL_OCC_INVERT | \ > -- > 1.8.1.4 > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
