From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Tengda Wu <wutengda@huaweicloud.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] perf bpf_counter: Fix opening of "any"(-1) CPU events
Date: Wed, 8 Oct 2025 16:35:25 +0900 [thread overview]
Message-ID: <aOYUPWbyQv53hrjE@google.com> (raw)
In-Reply-To: <20251007185826.3674908-1-irogers@google.com>
Hi Ian,
On Tue, Oct 07, 2025 at 11:58:26AM -0700, Ian Rogers wrote:
> The bperf BPF counter code doesn't handle "any"(-1) CPU events, always
> wanting to aggregate a count against a CPU, which avoids the need for
> atomics. Force evsels used for BPF counters to require a CPU when not
> in system-wide mode so that the "any"(-1) value isn't used during map
> propagation and evsel's CPU map matches that of the PMU.
>
> Fixes: b91917c0c6fa ("perf bpf_counter: Fix handling of cpumap fixing hybrid")
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/builtin-stat.c | 12 ++++++++++++
> tools/perf/util/bpf_counter.c | 1 +
> 2 files changed, 13 insertions(+)
>
> diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
> index 7006f848f87a..7fdc7f273a48 100644
> --- a/tools/perf/builtin-stat.c
> +++ b/tools/perf/builtin-stat.c
> @@ -2797,6 +2797,18 @@ int cmd_stat(int argc, const char **argv)
>
> evlist__warn_user_requested_cpus(evsel_list, target.cpu_list);
>
> + if (target.use_bpf && !target.system_wide) {
The target.use_bpf only checks the --bpf-counters option. But IIUC it's
possible to use BPF only for selected events with ':b' modifier. I
think you need to check each evsel with evsel__is_bperf().
Also system_wide might not be set for -C/--cpu option. Probably you
want target__has_cpu() instead of target.system_wide.
Thanks,
Namhyung
> + /*
> + * Setup BPF counters to require CPUs as any(-1) isn't
> + * supported. evlist__create_maps below will propagate this
> + * information to the evsels.
> + */
> + struct evsel *counter;
> +
> + evlist__for_each_entry(evsel_list, counter)
> + counter->core.requires_cpu = true;
> + }
> +
> if (evlist__create_maps(evsel_list, &target) < 0) {
> if (target__has_task(&target)) {
> pr_err("Problems finding threads of monitor\n");
> diff --git a/tools/perf/util/bpf_counter.c b/tools/perf/util/bpf_counter.c
> index ca5d01b9017d..d3e5933b171b 100644
> --- a/tools/perf/util/bpf_counter.c
> +++ b/tools/perf/util/bpf_counter.c
> @@ -495,6 +495,7 @@ static int bperf_reload_leader_program(struct evsel *evsel, int attr_map_fd,
> * following evsel__open_per_cpu call
> */
> evsel->leader_skel = skel;
> + assert(!perf_cpu_map__has_any_cpu_or_is_empty(evsel->core.cpus));
> evsel__open(evsel, evsel->core.cpus, evsel->core.threads);
>
> out:
> --
> 2.51.0.710.ga91ca5db03-goog
>
next prev parent reply other threads:[~2025-10-08 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 18:58 [PATCH v1] perf bpf_counter: Fix opening of "any"(-1) CPU events Ian Rogers
2025-10-08 7:35 ` Namhyung Kim [this message]
2025-10-08 15:08 ` Ian Rogers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aOYUPWbyQv53hrjE@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=wutengda@huaweicloud.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).