From: Lin Ming <ming.m.lin@intel.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Stephane Eranian <eranian@google.com>,
Andi Kleen <andi@firstfloor.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>,
Arjan van de Ven <arjan@infradead.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: [RFC PATCH 0/3 v3] perf: Add Intel Nehalem uncore pmu support
Date: Thu, 02 Dec 2010 13:19:38 +0800 [thread overview]
Message-ID: <1291267178.2405.311.camel@minggr.sh.intel.com> (raw)
Hi, all
Here are the v3 patches to add uncore pmu support to perf, applied on
top of current tip/master(74f6deb).
Changelogs of v3:
- Allocate uncore data with kmalloc_node, like AMD NB stuff. (Peter
Zijlstra)
- per-task uncore event is not allowed. Simply set pmu::task_ctx_nr =
perf_invalid_context. (Peter Zijlstra)
- Route interrupts to the first core that accesses uncore pmu. (Stephane
Eranian)
- Check CPUID signatures with boot_cpu_data. (Andi Kleen)
- Remove unneeded include files. (Andi Kleen)
Changelogs of v2:
- modify the NMI handling code to handle all counters enabled by all 4
cores.
- allocate uncore_events[] table dynamically using kmalloc_node() to
avoid unnecessary remote memory accesses. (Stephane Eranian)
- add support for the fixed uncore counter. (Stephane Eranian)
- Handling of exclude_* bits. Uncore PMU measures at all privilege level
all the time. So it doesn't make sense to specify any exclude bits.
(Stephane Eranian)
- let uncore code be more self contained, that is, not include it in
arch/x86/kernel/cpu/perf_event.c (Peter Zijlstra)
- uncore pmu interrupt have its own NMI_DIE notifier entry. (Peter
Zijlstra)
Known bugs:
- When hyper thread is enabled, both HTs will receive the NMI. In this
case, the overflow status bits are not acked correctly.
TODO:
- Add support for uncore address/opcode match thing
- Add a new sub-command for uncore events statistics.
For example, perf package -p <package-id> -e <event>
As usual, any comment is very appreciated.
Lin Ming
reply other threads:[~2010-12-02 5:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1291267178.2405.311.camel@minggr.sh.intel.com \
--to=ming.m.lin@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®