From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Nia Su <nia.su@sifive.com>, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Thomas Falcon <thomas.falcon@intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] perf evlist: Don't restrict uncore events to PMU CPUs
Date: Fri, 25 Sep 2026 15:29:51 +0200 [thread overview]
Message-ID: <arZ3T-H6SndL592d@x2> (raw)
In-Reply-To: <CAP-5=fU2UOT8pZFLOifxHo7U4XsPv9YbYnAitjdvxsB=0AYuoQ@mail.gmail.com>
On Tue, Sep 15, 2026 at 12:42:43PM -0700, Ian Rogers wrote:
> On Wed, Sep 9, 2026 at 7:31 PM Nia Su <nia.su@sifive.com> wrote:
> > The PMU CPU map has different semantics for core and uncore PMUs.
<SNIP>
> > Add evsel->is_pmu_uncore, set once from pmu->is_uncore at parse time,
> > to skip the intersection for uncore PMUs. Core PMUs, and other
> > non-core PMUs such as software events, breakpoints, or tracepoints,
> > continue to be restricted to their PMU CPU map.
> > Fixes: 811082e4b668 ("perf parse-events: Support user CPUs mixed with threads/processes")
> > Assisted-by: Claude Sonnet 5
> > Signed-off-by: Nia Su <nia.su@sifive.com>
> Reviewed-by: Ian Rogers <irogers@google.com>
Thanks, applied to perf-tools-next, for v7.4.
- Arnaldo
prev parent reply other threads:[~2026-09-25 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 2:31 [PATCH v2] perf evlist: Don't restrict uncore events to PMU CPUs Nia Su
2026-09-10 2:40 ` sashiko-bot
2026-09-15 19:42 ` Ian Rogers
2026-09-25 13:29 ` Arnaldo Carvalho de Melo [this message]
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=arZ3T-H6SndL592d@x2 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nia.su@sifive.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.