[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240925135523.367957-1-wutengda@huaweicloud.com>
Date: Wed, 25 Sep 2024 13:55:21 +0000
From: Tengda Wu <wutengda@...weicloud.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: song@...nel.org,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Ian Rogers <irogers@...gle.com>,
Adrian Hunter <adrian.hunter@...el.com>,
kan.liang@...ux.intel.com,
linux-perf-users@...r.kernel.org,
linux-kernel@...r.kernel.org,
bpf@...r.kernel.org
Subject: [PATCH -next 0/2] perf stat: a set of small fixes for bperf
Hi,
This is a set of small fixes for bperf (perf-stat --bpf-counters).
It aims to fix the following two issues:
1) bperf limited the number of events to a maximum of 16, which
caused failures in some scenarios and lacked friendly prompts.
2) bperf failed to correctly handle whether events were supported,
resulting in the incorrect display when the event count was 0.
The reason for fixing these issues is that bperf is very useful in
some cost-sensitive scenarios, such as top-down analysis scenarios.
Increasing the attr map size can allow these scenarios to collect
more events at the same time, making it possible to gather enough
information to perform complex metric calculations in top-down.
Thanks,
Tengda
Tengda Wu (2):
perf stat: Increase perf_attr_map entries
perf stat: Fix incorrect display of bperf when event count is 0
tools/lib/perf/include/perf/bpf_perf.h | 1 +
tools/perf/util/bpf_counter.c | 26 +++++++++++++++++---------
2 files changed, 18 insertions(+), 9 deletions(-)
--
2.34.1
Powered by blists - more mailing lists