summaryrefslogtreecommitdiffstats
path: root/tools/perf/perf.h
diff options
context:
space:
mode:
authorAndi Kleen <ak@linux.intel.com>2017-10-20 13:27:55 -0700
committerArnaldo Carvalho de Melo <acme@redhat.com>2017-11-28 14:19:39 -0300
commit59622fd496a3175c7bf549046e091d81c303ecff (patch)
tree2e5083d49399cb18fadca963f48b47d72fad2258 /tools/perf/perf.h
parentdffdcbdbb0205ac10daec64f7fa519f1904f5481 (diff)
downloadop-kernel-dev-59622fd496a3175c7bf549046e091d81c303ecff.zip
op-kernel-dev-59622fd496a3175c7bf549046e091d81c303ecff.tar.gz
perf record: Fix -c/-F options for cpu event aliases
The Intel PMU event aliases have a implicit period= specifier to set the default period. Unfortunately this breaks overriding these periods with -c or -F, because the alias terms look like they are user specified to the internal parser, and user specified event qualifiers override the command line options. Track that they are coming from aliases by adding a "weak" state to the term. Any weak terms don't override command line options. I only did it for -c/-F for now, I think that's the only case that's broken currently. Before: $ perf record -c 1000 -vv -e uops_issued.any ... { sample_period, sample_freq } 2000003 After: $ perf record -c 1000 -vv -e uops_issued.any ... { sample_period, sample_freq } 1000 Signed-off-by: Andi Kleen <ak@linux.intel.com> Acked-by: Jiri Olsa <jolsa@kernel.org> Link: http://lkml.kernel.org/r/20171020202755.21410-2-andi@firstfloor.org Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Diffstat (limited to 'tools/perf/perf.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud