From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: kan.liang@linux.intel.com, namhyung@kernel.org,
adrian.hunter@intel.com, peterz@infradead.org, mingo@kernel.org,
linux-kernel@vger.kernel.org,
kernel test robot <oliver.sang@intel.com>
Subject: Re: [PATCH] perf jevents: Don't stop at the first matched pmu when searching a events table
Date: Wed, 31 Jul 2024 10:30:57 -0300 [thread overview]
Message-ID: <Zqo8kVXkN_UaTp6f@x1> (raw)
In-Reply-To: <CAP-5=fVZVU7kMOHz7CC7O1+2dX844dHqhqMebzEKWMA=59am-g@mail.gmail.com>
On Tue, Jul 16, 2024 at 09:30:01AM -0700, Ian Rogers wrote:
> On Tue, Jul 16, 2024 at 6:29 AM <kan.liang@linux.intel.com> wrote:
> >
> > From: Kan Liang <kan.liang@linux.intel.com>
> >
> > The "perf all PMU test" fails on a Coffee Lake machine.
> >
> > The failure is caused by the below change in the commit e2641db83f18
> > ("perf vendor events: Add/update skylake events/metrics").
> >
> > + {
> > + "BriefDescription": "This 48-bit fixed counter counts the UCLK cycles",
> > + "Counter": "FIXED",
> > + "EventCode": "0xff",
> > + "EventName": "UNC_CLOCK.SOCKET",
> > + "PerPkg": "1",
> > + "PublicDescription": "This 48-bit fixed counter counts the UCLK cycles.",
> > + "Unit": "cbox_0"
> > }
> >
> > The other cbox events have the unit name "CBOX", while the fixed counter
> > has a unit name "cbox_0". So the events_table will maintain separate
> > entries for cbox and cbox_0.
> >
> > The perf_pmus__print_pmu_events() calculates the total number of events,
> > allocate an aliases buffer, store all the events into the buffer, sort,
> > and print all the aliases one by one.
> >
> > The problem is that the calculated total number of events doesn't match
> > the stored events in the aliases buffer.
> >
> > The perf_pmu__num_events() is used to calculate the number of events. It
> > invokes the pmu_events_table__num_events() to go through the entire
> > events_table to find all events. Because of the
> > pmu_uncore_alias_match(), the suffix of uncore PMU will be ignored. So
> > the events for cbox and cbox_0 are all counted.
> >
> > When storing events into the aliases buffer, the
> > perf_pmu__for_each_event() only process the events for cbox.
> >
> > Since a bigger buffer was allocated, the last entry are all 0.
> > When printing all the aliases, null will be outputted, and trigger the
> > failure.
> >
> > The mismatch was introduced from the commit e3edd6cf6399 ("perf
> > pmu-events: Reduce processed events by passing PMU"). The
> > pmu_events_table__for_each_event() stops immediately once a pmu is set.
> > But for uncore, especially this case, the method is wrong and mismatch
> > what perf does in the perf_pmu__num_events().
> >
> > With the patch,
> > $ perf list pmu | grep -A 1 clock.socket
> > unc_clock.socket
> > [This 48-bit fixed counter counts the UCLK cycles. Unit: uncore_cbox_0
> > $ perf test "perf all PMU test"
> > 107: perf all PMU test : Ok
> >
> > Reported-by: kernel test robot <oliver.sang@intel.com>
> > Closes: https://lore.kernel.org/all/202407101021.2c8baddb-oliver.sang@intel.com/
> > Fixes: e3edd6cf6399 ("perf pmu-events: Reduce processed events by passing PMU")
> > Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
>
> Awesome sauce, thanks!
>
> Reviewed-by: Ian Rogers <irogers@google.com>
Thanks, applied to tmp.perf-tools-next,
- Arnaldo
next prev parent reply other threads:[~2024-07-31 13:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 13:29 kan.liang
2024-07-16 16:30 ` Ian Rogers
2024-07-31 13:30 ` Arnaldo Carvalho de Melo [this message]
2024-09-26 21:34 ` Ian Rogers
2024-09-30 20:22 ` Namhyung Kim
2024-09-30 20:30 ` Ian Rogers
2024-09-30 21:47 ` Namhyung Kim
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=Zqo8kVXkN_UaTp6f@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=oliver.sang@intel.com \
--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®