|| ||Vince Weaver <vweaver1-AT-eecs.utk.edu> |
|| ||Ingo Molnar <mingo-AT-elte.hu> |
|| ||Re: [PATCH 1/1] perf tools: Add missing user space support for
|| ||Mon, 25 Apr 2011 13:12:15 -0400 (EDT)|
|| ||Arnaldo Carvalho de Melo <acme-AT-infradead.org>,
linux-kernel-AT-vger.kernel.org, Andi Kleen <ak-AT-linux.intel.com>,
Peter Zijlstra <peterz-AT-infradead.org>,
Stephane Eranian <eranian-AT-gmail.com>,
Lin Ming <ming.m.lin-AT-intel.com>,
Arnaldo Carvalho de Melo <acme-AT-redhat.com>,
Thomas Gleixner <tglx-AT-linutronix.de>,
Peter Zijlstra <a.p.zijlstra-AT-chello.nl>|
|| ||Article, Thread
sorry for the late reply on this thread, it happened inconveniently over
the long weekend.
On Fri, 22 Apr 2011, Ingo Molnar wrote:
> But this kind of usability is absolutely unacceptable - users should not
> be expected to type in magic, CPU and model specific incantations to get
> access to useful hardware functionality.
That's why people use libpfm4. or PAPI. And they do.
Current PAPI snapshots support offcore response on recent git kernels.
With full names, no hex values, thanks to libpfm4.
All the world is not perf.
> The proper solution is to expose useful offcore functionality via
> generalized events - that way users do not have to care which specific
> CPU model they are using, they can use the conceptual event and not some
> model specific quirky hexa number.
No no no no.
Blocking access to raw events is the wrong idea. If anything, the whole
"generic events" thing in the kernel should be ditched. Wrong events are
used at times (see AMD branch events a few releases back, now Nehalem
cache events). This all belongs in userspace, as was pointed out at the
start. The kernel has no business telling users which perf events are
interesting, or limiting them! What is this, windows?
If you do block access to any raw events, we're going to have to start
recommending people ditch perf_events and start patching the kernel with
perfctr again. We already do for P4/netburst users, as Pentium 4 support
is currently hosed due to NMI event conflicts.
Also with perfctr it's much easier to get low-latency access to the
to post comments)