From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Chun-Tse Shao <ctshao@google.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] perf jevents: Add mesh bandwidth saturation for CWF, EMR, GRR, SNR, SPR, SRF
Date: Sun, 13 Sep 2026 21:43:48 -0300 [thread overview]
Message-ID: <aqdDRJ7kD_fyR2OI@x2> (raw)
In-Reply-To: <20260909220445.2117921-1-irogers@google.com>
On Wed, Sep 09, 2026 at 03:04:45PM -0700, Ian Rogers wrote:
> Extend the mesh bandwidth saturation's list of events to include
> events from clearwaterforest, emeraldrapids, grandridge,
> graniterapids, sapphirerapids and sierraforest. This makes the
> lpm_mem_sat metric available for those CPU models.
Thanks, applied to perf-tools-next, for v7.4.
- Arnaldo
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/pmu-events/intel_metrics.py | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tools/perf/pmu-events/intel_metrics.py b/tools/perf/pmu-events/intel_metrics.py
> index bc2b920d3a0d..9780bf978a41 100755
> --- a/tools/perf/pmu-events/intel_metrics.py
> +++ b/tools/perf/pmu-events/intel_metrics.py
> @@ -1099,7 +1099,8 @@ def UncoreMemSat() -> Optional[Metric]:
> try:
> clocks = Event("UNC_CHA_CLOCKTICKS", "UNC_C_CLOCKTICKS")
> sat = Event("UNC_CHA_DISTRESS_ASSERTED.VERT", "UNC_CHA_FAST_ASSERTED.VERT",
> - "UNC_C_FAST_ASSERTED")
> + "UNC_C_FAST_ASSERTED", "UNC_CHA_DISTRESS_ASSERTED.DPT_ANY",
> + "UNC_CHA_DISTRESS_ASSERTED.DPT_NONLOCAL")
> except:
> return None
>
> --
> 2.55.0.1003.g10538fe699-goog
prev parent reply other threads:[~2026-09-14 0:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 22:04 [PATCH v1] perf jevents: Add mesh bandwidth saturation for CWF, EMR, GRR, SNR, SPR, SRF Ian Rogers
2026-09-09 22:08 ` sashiko-bot
2026-09-14 0:43 ` 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=aqdDRJ7kD_fyR2OI@x2 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ctshao@google.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 \
/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.