[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1291704978.3678.140.camel@minggr.sh.intel.com>
Date: Tue, 07 Dec 2010 14:56:18 +0800
From: Lin Ming <ming.m.lin@...el.com>
To: Cyrill Gorcunov <gorcunov@...il.com>
Cc: Ingo Molnar <mingo@...e.hu>, Don Zickus <dzickus@...hat.com>,
Jason Wessel <jason.wessel@...driver.com>,
Stephane Eranian <eranian@...gle.com>,
Peter Zijlstra <peterz@...radead.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] perf, x86: P4 PMU - Fix unflagged overflows handling v4
On Mon, 2010-12-06 at 06:34 +0800, Cyrill Gorcunov wrote:
> Don found that P4 PMU reads CCCR register instead of counter
> itself (in attempt to catch unflagged event) this makes P4
> NMI handler to consume all NMIs it observes. So the other
> NMI users such as kgdb simply have no chance to get NMI
> on their hands.
>
> v2: Call checking_wrmsrl only if needed.
> v3: Check the valuable bits.
> v4: Leave p4_pmu_clear_cccr_ovf early if P4_CCCR_OVF flag is set.
>
> Reported-by: Jason Wessel <jason.wessel@...driver.com>
> Reported-by: Don Zickus <dzickus@...hat.com>
> Signed-off-by: Cyrill Gorcunov <gorcunov@...nvz.org>
> CC: Lin Ming <ming.m.lin@...el.com>
> CC: Stephane Eranian <eranian@...gle.com>
> CC: Peter Zijlstra <peterz@...radead.org>
> ---
>
> Ming, Jason, mind to give this patch a shot? Note that it
> seems you have to disable nmi-watchdog at bootstrap to be
> able to run perf top. I believe it's a different issue
> unrelated to this particular nit.
perf top gets nothing with current -tip/master(93edb453), both with and
without this patch.
I'm checking where the problem is.
Lin Ming
>
> arch/x86/include/asm/perf_event_p4.h | 3 +++
> arch/x86/kernel/cpu/perf_event_p4.c | 28 +++++++++++++++-------------
> 2 files changed, 18 insertions(+), 13 deletions(-)
>
> Index: linux-2.6.git/arch/x86/include/asm/perf_event_p4.h
> =====================================================================
> --- linux-2.6.git.orig/arch/x86/include/asm/perf_event_p4.h
> +++ linux-2.6.git/arch/x86/include/asm/perf_event_p4.h
> @@ -20,6 +20,9 @@
> #define ARCH_P4_MAX_ESCR (ARCH_P4_TOTAL_ESCR - ARCH_P4_RESERVED_ESCR)
> #define ARCH_P4_MAX_CCCR (18)
>
> +#define ARCH_P4_CNTRVAL_BITS (40)
> +#define ARCH_P4_CNTRVAL_MASK ((1ULL << ARCH_P4_CNTRVAL_BITS) - 1)
> +
> #define P4_ESCR_EVENT_MASK 0x7e000000U
> #define P4_ESCR_EVENT_SHIFT 25
> #define P4_ESCR_EVENTMASK_MASK 0x01fffe00U
> Index: linux-2.6.git/arch/x86/kernel/cpu/perf_event_p4.c
> =====================================================================
> --- linux-2.6.git.orig/arch/x86/kernel/cpu/perf_event_p4.c
> +++ linux-2.6.git/arch/x86/kernel/cpu/perf_event_p4.c
> @@ -753,19 +753,21 @@ out:
>
> static inline int p4_pmu_clear_cccr_ovf(struct hw_perf_event *hwc)
> {
> - int overflow = 0;
> - u32 low, high;
> + u64 v;
>
> - rdmsr(hwc->config_base + hwc->idx, low, high);
> -
> - /* we need to check high bit for unflagged overflows */
> - if ((low & P4_CCCR_OVF) || !(high & (1 << 31))) {
> - overflow = 1;
> - (void)checking_wrmsrl(hwc->config_base + hwc->idx,
> - ((u64)low) & ~P4_CCCR_OVF);
> + /* an official way for overflow indication */
> + rdmsrl(hwc->config_base + hwc->idx, v);
> + if (v & P4_CCCR_OVF) {
> + wrmsrl(hwc->config_base + hwc->idx, v & ~P4_CCCR_OVF);
> + return 1;
> }
>
> - return overflow;
> + /* it might be unflagged overflow */
> + rdmsrl(hwc->event_base + hwc->idx, v);
> + if (!(v & ARCH_P4_CNTRVAL_MASK))
> + return 1;
> +
> + return 0;
> }
>
> static void p4_pmu_disable_pebs(void)
> @@ -1152,9 +1154,9 @@ static __initconst const struct x86_pmu
> */
> .num_counters = ARCH_P4_MAX_CCCR,
> .apic = 1,
> - .cntval_bits = 40,
> - .cntval_mask = (1ULL << 40) - 1,
> - .max_period = (1ULL << 39) - 1,
> + .cntval_bits = ARCH_P4_CNTRVAL_BITS,
> + .cntval_mask = ARCH_P4_CNTRVAL_MASK,
> + .max_period = (1ULL << (ARCH_P4_CNTRVAL_BITS - 1)) - 1,
> .hw_config = p4_hw_config,
> .schedule_events = p4_pmu_schedule_events,
> /*
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists