mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Clark <james.clark@linaro.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>,
	Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Ankur Arora <ankur.a.arora@oracle.com>,
	Howard Chu <howardchu95@gmail.com>,
	Thomas Falcon <thomas.falcon@intel.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 4/4] libperf evlist: Recompute CPU map when an evsel goes system wide
Date: Wed, 28 Oct 2026 09:35:06 +0000	[thread overview]
Message-ID: <d3886efa-5be4-4cdc-8990-ed56b044a5b3@linaro.org> (raw)
In-Reply-To: <20261027170415.2815859-4-irogers@google.com>



On 27/10/2026 17:04, Ian Rogers wrote:
> perf_evlist__go_system_wide() marks the evsel as system wide and then
> propagates the evlist's maps to it. __perf_evlist__propagate_maps()
> only assigns the PMU CPUs to evsel->cpus if the map is empty, but an
> evsel added after the evlist's maps were created already has the user
> requested CPUs propagated (e.g. the "any CPU" map of -1 in per-thread
> or workload mode). Going system wide then leaves the evsel opened on
> the wrong CPUs.
> 
> Drop the existing CPU map before propagating so the evsel is given all
> of its PMU's CPUs, as is expected for a system wide event.
> 
> Fixes: 811082e4b668 ("perf parse-events: Support user CPUs mixed with threads/processes")
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
>   tools/lib/perf/evlist.c | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/tools/lib/perf/evlist.c b/tools/lib/perf/evlist.c
> index c1c5b0684eed..46de69aa5a86 100644
> --- a/tools/lib/perf/evlist.c
> +++ b/tools/lib/perf/evlist.c
> @@ -835,7 +835,10 @@ void perf_evlist__go_system_wide(struct perf_evlist *evlist, struct perf_evsel *
>   {
>   	if (!evsel->system_wide) {
>   		evsel->system_wide = true;
> -		if (evlist->needs_map_propagation)
> +		if (evlist->needs_map_propagation) {
> +			perf_cpu_map__put(evsel->cpus);
> +			evsel->cpus = NULL;
>   			__perf_evlist__propagate_maps(evlist, evsel);
> +		}
>   	}
>   }

Reviewed-by: James Clark <james.clark@linaro.org>


  reply	other threads:[~2026-10-28  9:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 17:04 [PATCH v1 1/4] perf off-cpu: Use the CPU map index for the bpf-output file descriptor Ian Rogers
2026-10-27 17:04 ` [PATCH v1 2/4] perf off-cpu: Write the sample ID for PERF_SAMPLE_ID Ian Rogers
2026-10-28  9:34   ` James Clark
2026-10-27 17:04 ` [PATCH v1 3/4] perf off-cpu: Fix cgroup_filter map sizing Ian Rogers
2026-10-28  9:34   ` James Clark
2026-10-27 17:04 ` [PATCH v1 4/4] libperf evlist: Recompute CPU map when an evsel goes system wide Ian Rogers
2026-10-28  9:35   ` James Clark [this message]
2026-10-28  9:34 ` [PATCH v1 1/4] perf off-cpu: Use the CPU map index for the bpf-output file descriptor James Clark

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=d3886efa-5be4-4cdc-8990-ed56b044a5b3@linaro.org \
    --to=james.clark@linaro.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ankur.a.arora@oracle.com \
    --cc=howardchu95@gmail.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=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=thomas.falcon@intel.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

all inboxes | Powered by JetHome®