diff options
author | Kan Liang <kan.liang@intel.com> | 2016-03-30 12:16:15 -0700 |
---|---|---|
committer | Arnaldo Carvalho de Melo <acme@redhat.com> | 2016-04-01 18:46:24 -0300 |
commit | ac0e2cd555373ae6f8f3a3ad3fbbf5b6d1e7aaaa (patch) | |
tree | acb9929531a5d0f051be6a662dff099f3ea8252e /tools/perf/builtin-trace.c | |
parent | bd0c7a54219cc3745ce7f36970d8e5ffb3f8d80e (diff) | |
download | talos-obmc-linux-ac0e2cd555373ae6f8f3a3ad3fbbf5b6d1e7aaaa.tar.gz talos-obmc-linux-ac0e2cd555373ae6f8f3a3ad3fbbf5b6d1e7aaaa.zip |
perf tools: Fix PMU term format max value calculation
Currently the max value of format is calculated by the bits number. It
relies on the continuity of the format.
However, uncore event format is not continuous. E.g. uncore qpi event
format can be 0-7,21.
If bit 21 is set, there is parsing issues as below.
$ perf stat -a -e uncore_qpi_0/event=0x200002,umask=0x8/
event syntax error: '..pi_0/event=0x200002,umask=0x8/'
\___ value too big for format, maximum is 511
This patch return the real max value by setting all possible bits to 1.
Signed-off-by: Kan Liang <kan.liang@intel.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Andi Kleen <ak@linux.intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>
Link: http://lkml.kernel.org/r/1459365375-14285-1-git-send-email-kan.liang@intel.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Diffstat (limited to 'tools/perf/builtin-trace.c')
0 files changed, 0 insertions, 0 deletions