[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1459365375-14285-1-git-send-email-kan.liang@intel.com>
Date: Wed, 30 Mar 2016 12:16:15 -0700
From: kan.liang@...el.com
To: acme@...nel.org
Cc: jolsa@...hat.com, ak@...ux.intel.com,
alexander.shishkin@...ux.intel.com, linux-kernel@...r.kernel.org,
Kan Liang <kan.liang@...el.com>
Subject: [PATCH 1/1] perf tools: fix format max value calculation
From: Kan Liang <kan.liang@...el.com>
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 bit to 1.
Signed-off-by: Kan Liang <kan.liang@...el.com>
---
tools/perf/util/pmu.c | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/tools/perf/util/pmu.c b/tools/perf/util/pmu.c
index adef23b..bf34468 100644
--- a/tools/perf/util/pmu.c
+++ b/tools/perf/util/pmu.c
@@ -602,14 +602,13 @@ static void pmu_format_value(unsigned long *format, __u64 value, __u64 *v,
static __u64 pmu_format_max_value(const unsigned long *format)
{
- int w;
+ __u64 w = 0;
+ int fbit;
- w = bitmap_weight(format, PERF_PMU_FORMAT_BITS);
- if (!w)
- return 0;
- if (w < 64)
- return (1ULL << w) - 1;
- return -1;
+ for_each_set_bit(fbit, format, PERF_PMU_FORMAT_BITS)
+ w |= (1ULL << fbit);
+
+ return w;
}
/*
--
2.5.0
Powered by blists - more mailing lists