On Mon, Oct 03, 2016 at 09:47:06PM -0300, Arnaldo Carvalho de Melo wrote: > Em Thu, Sep 15, 2016 at 03:24:53PM -0700, Sukadev Bhattiprolu escreveu: > > From: Andi Kleen <a...@linux.intel.com> > > > > Make alias matching the events parser case-insensitive. This is useful > > with the JSON events. perf uses lower case events, but the CPU manuals > > generally use upper case event names. The JSON files use lower > > case by default too. But if we search case insensitively then > > users can cut-n-paste the upper case event names. > > > > So the following works: > > > > % perf stat -e BR_INST_EXEC.TAKEN_INDIRECT_NEAR_CALL true > > > > Performance counter stats for 'true': > > > > 305 BR_INST_EXEC.TAKEN_INDIRECT_NEAR_CALL > > > > 0.000492799 seconds time elapsed > > So now trying to figure this out: > > [acme@jouet linux]$ perf stat -e br_inst_exec.all_direct_near_call true > event syntax error: 'br_inst_exec.all_direct_near_call' > \___ 'period' is not usable in 'perf stat' > Run 'perf list' for a list of valid events
looks like you need also this one: 155128eaa62f Allow period= in perf stat CPU event descriptions. jirka
