Linux Perf Users
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Sandipan Das <sandipan.das@amd.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	James Clark <james.clark@linaro.org>,
	Ravi Bangoria <ravi.bangoria@amd.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] perf pmu-events AMD: Switch l2_itlb_misses to bp_l1_tlb_miss_l2_tlb_miss.all
Date: Thu, 14 May 2026 20:55:11 -0300	[thread overview]
Message-ID: <agZg3xXkkpK089T5@x1> (raw)
In-Reply-To: <CAP-5=fUMC-vWFvt3S0aNCqqSB=ka1FisUgRbJwBhoBKMYt_-nw@mail.gmail.com>

On Thu, May 14, 2026 at 10:48:23AM -0700, Ian Rogers wrote:
> On Tue, Apr 14, 2026 at 11:03 PM Sandipan Das <sandipan.das@amd.com> wrote:
> >
> > On 14-04-2026 23:28, Ian Rogers wrote:
> > > l2_itlb_misses is a valid legacy cache event name, hence allowing it
> > > in all_events in metric.py. l2_itlb_misses was also a json event for
> > > AMD zen1, zen2 and zen3. For zen4, zen5 and zen6 the checking that
> > > metric events are within the json was skipping l2_itlb_misses as it is
> > > a valid legacy event, however, the PMU driver lacks the event mapping
> > > causing it to be a bad event when used in the metric. Add
> > > bp_l1_tlb_miss_l2_tlb_miss.all as the l2 itlb miss event (bp = branch
> > > predictor, the AMD way to say itlb), so that is used in preference to
> > > l2_itlb_misses when the event exists. Remove l2_itlb_misses from
> > > metric.py as the legacy event isn't used by any metrics and having it
> > > is error prone for newer AMD zen models.
> > >
> > > Fixes: e596f329668e ("perf jevents: Add itlb metric group for AMD")
> > > Signed-off-by: Ian Rogers <irogers@google.com>
> > > ---
> > >  tools/perf/pmu-events/amd_metrics.py | 2 +-
> > >  tools/perf/pmu-events/metric.py      | 1 -
> > >  2 files changed, 1 insertion(+), 2 deletions(-)
> > >
> > > diff --git a/tools/perf/pmu-events/amd_metrics.py b/tools/perf/pmu-events/amd_metrics.py
> > > index 63e5098606c4..ee5381646a8d 100755
> > > --- a/tools/perf/pmu-events/amd_metrics.py
> > > +++ b/tools/perf/pmu-events/amd_metrics.py
> > > @@ -287,7 +287,7 @@ def AmdDtlb() -> Optional[MetricGroup]:
> > >  def AmdItlb():
> > >      global _zen_model
> > >      l2h = Event("bp_l1_tlb_miss_l2_tlb_hit", "bp_l1_tlb_miss_l2_hit")
> > > -    l2m = Event("l2_itlb_misses")
> > > +    l2m = Event("bp_l1_tlb_miss_l2_tlb_miss.all", "l2_itlb_misses",)
> > >      l2r = l2h + l2m
> > >
> > >      itlb_l1_mg = None
> > > diff --git a/tools/perf/pmu-events/metric.py b/tools/perf/pmu-events/metric.py
> > > index 0c41a502cf21..c1931b2a5170 100644
> > > --- a/tools/perf/pmu-events/metric.py
> > > +++ b/tools/perf/pmu-events/metric.py
> > > @@ -25,7 +25,6 @@ def LoadEvents(directory: str) -> None:
> > >        "cycles",
> > >        "duration_time",
> > >        "instructions",
> > > -      "l2_itlb_misses",
> > >    }
> > >    for file in os.listdir(os.fsencode(directory)):
> > >      filename = os.fsdecode(file)
> >
> > Reviewed-by: Sandipan Das <sandipan.das@amd.com>
> 
> Ping.

Thanks, applied to perf-tools-next, for v7.2.

- Arnaldo

      reply	other threads:[~2026-05-14 23:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14 17:58 [PATCH v1] perf pmu-events AMD: Switch l2_itlb_misses to bp_l1_tlb_miss_l2_tlb_miss.all Ian Rogers
2026-04-15  6:03 ` Sandipan Das
2026-05-14 17:48   ` Ian Rogers
2026-05-14 23:55     ` 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=agZg3xXkkpK089T5@x1 \
    --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=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@amd.com \
    --cc=sandipan.das@amd.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