[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 10 Oct 2012 15:44:05 +0200
From: Stephane Eranian <eranian@...gle.com>
To: Jiri Olsa <jolsa@...hat.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Ingo Molnar <mingo@...e.hu>, Paul Mackerras <paulus@...ba.org>,
Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCHv4 0/8] perf, tool: Allow to use hw events in PMU syntax
On Wed, Oct 10, 2012 at 3:40 PM, Jiri Olsa <jolsa@...hat.com> wrote:
> On Wed, Oct 10, 2012 at 03:34:53PM +0200, Stephane Eranian wrote:
>> On Wed, Oct 10, 2012 at 2:53 PM, Jiri Olsa <jolsa@...hat.com> wrote:
>> > hi,
>> > here's the change to make following syntax available:
>> > perf stat -e cpu/event=instructions/u ls
>> > perf stat -e cpu/cycles/u ls
>> >
>> Unless, I am mistaken but I did not see in your patch where you adjust the list
>> of generic Hw events (and encodings) you expose via sysfs based on CPU model
>> number. Some generic HW PMU may not have actual physical mappings. Look
>> at IvyBridge, for instance.
>
> hm, path 2 remove any attribute that is not defined via x86_pmu.event_map,
> if that's what you mean..
>
Ok, you're right, so this should be okay then.
Thanks.
> jirka
--
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