From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf pmu: Consider raw events as legacy events
Date: Wed, 7 May 2025 14:50:19 -0700 [thread overview]
Message-ID: <aBvVm2xkiwqDT5EX@google.com> (raw)
In-Reply-To: <CAP-5=fVvth_HnfnPNxtHe=FzxT9hNNKKDLGCSvQfLqwTY4WpHg@mail.gmail.com>
Hi Ian,
On Wed, May 07, 2025 at 08:42:27AM -0700, Ian Rogers wrote:
> On Tue, May 6, 2025 at 3:23 PM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > When it finds a matching pmu for a legacy event, it should look for
> > core pmus. The raw events also refers to core events so it should be
> > handled together.
> >
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> > ---
> > tools/perf/util/pmus.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/tools/perf/util/pmus.c b/tools/perf/util/pmus.c
> > index b99292de76693dbb..0134321fc520b1fc 100644
> > --- a/tools/perf/util/pmus.c
> > +++ b/tools/perf/util/pmus.c
> > @@ -726,7 +726,8 @@ struct perf_pmu *evsel__find_pmu(const struct evsel *evsel)
> > pmu = perf_pmus__find_by_type(evsel->core.attr.type);
> > legacy_core_type =
> > evsel->core.attr.type == PERF_TYPE_HARDWARE ||
> > - evsel->core.attr.type == PERF_TYPE_HW_CACHE;
> > + evsel->core.attr.type == PERF_TYPE_HW_CACHE ||
> > + evsel->core.attr.type == PERF_TYPE_RAW;
>
> I don't think this is right. The PERF_TYPE_RAW isn't a legacy type as
> we map sysfs/json names to the format encoding. More than this, the
> extended type information will not be present for a raw type and so
> this change could cause an invalid PMU to be looked up on
> hybrid/BIG.little systems. On x86 the cpu or cpu_core PMU will have
> type PERF_TYPE_RAW (4). As is common ARM decided to do things
> differently, meaning there is no type 4 to a PMU mapping. I think we
> need a change like:
> ```
> diff --git a/tools/perf/util/pmus.c b/tools/perf/util/pmus.c
> index b99292de7669..6632209c6664 100644
> --- a/tools/perf/util/pmus.c
> +++ b/tools/perf/util/pmus.c
> @@ -727,14 +727,21 @@ struct perf_pmu *evsel__find_pmu(const struct
> evsel *evsel)
> legacy_core_type =
> evsel->core.attr.type == PERF_TYPE_HARDWARE ||
> evsel->core.attr.type == PERF_TYPE_HW_CACHE;
> - if (!pmu && legacy_core_type) {
> - if (perf_pmus__supports_extended_type()) {
> - u32 type = evsel->core.attr.config >>
> PERF_PMU_TYPE_SHIFT;
> + if (!pmu && legacy_core_type && perf_pmus__supports_extended_type()) {
> + u32 type = evsel->core.attr.config >> PERF_PMU_TYPE_SHIFT;
>
> - pmu = perf_pmus__find_by_type(type);
> - } else {
> - pmu = perf_pmus__find_core_pmu();
> - }
> + pmu = perf_pmus__find_by_type(type);
> + }
> + if (!pmu && (legacy_core_type || evsel->core.attr.type ==
> PERF_TYPE_RAW)) {
> + /*
> + * For legacy events, if there was no extended type info then
> + * assume the PMU is the first core PMU.
> + *
> + * On architectures like ARM there is no sysfs PMU with type
> + * PERF_TYPE_RAW, assume the RAW events are going to be handled
> + * by the first core PMU.
> + */
> + pmu = perf_pmus__find_core_pmu();
> }
> ((struct evsel *)evsel)->pmu = pmu;
> return pmu;
> ```
> which handles both the case that the extended type was missing on
> hybrid/BIG.little and the ARM raw type problem.
Looks good to me. Thanks for the suggestion!
Thanks,
Namhyung
prev parent reply other threads:[~2025-05-07 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 22:23 Namhyung Kim
2025-05-07 15:42 ` Ian Rogers
2025-05-07 21:50 ` Namhyung Kim [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=aBvVm2xkiwqDT5EX@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
/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®