Re: [PATCH 20/41] perf tools: Let a user specify a PMU event without any config terms

From: Adrian Hunter
Date: Fri Aug 29 2014 - 14:49:00 EST

On 16/07/2014 9:22 p.m., Jiri Olsa wrote:
On Wed, Jul 16, 2014 at 06:04:44PM +0300, Adrian Hunter wrote:
On 16/07/2014 5:25 p.m., Jiri Olsa wrote:
On Mon, Jul 14, 2014 at 01:02:44PM +0300, Adrian Hunter wrote:
This enables a PMU event to be specified in the form:


which is effectively the same as:


This patch is a precursor to defining
default config for a PMU.

I understand the need for default config, but could you please elaborate
why do we want to parse 'pmu//' as an event string string?

Currently the parser requires the slashes to identify a PMU event
as opposed to a hardware or other kind of event.

right, so why do we want to parse 'pmu//' as an event string? ;-)

I am not sure what you mean. Here I am using 'pmu' as a placeholder
for a real PMU name. So actual event strings are 'intel_bts//' or
'intel_pt//' or 'intel_pt/tsc=0,noretcomp=1/'

The parser uses various tricks to decide what kind of event the event
name actually is e.g. colons indicate a tracepoint.

If you are asking why the parser isn't smart enough to know the event
name is a PMU name, I guess it is either to keep the namespaces separate,
or because it was easier to program it that way.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at