From: James Clark <james.clark@linaro.org>
To: Leo Yan <leo.yan@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>, Jiri Olsa <jolsa@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Kieran Hejmadi <kieran.hejmadi@arm.com>
Subject: Re: [PATCH] perf arm-spe: Add Neoverse V3AE data source decoding
Date: Tue, 29 Sep 2026 12:54:06 +0100 [thread overview]
Message-ID: <50a0338e-e395-407c-bccd-cfb90f113e58@linaro.org> (raw)
In-Reply-To: <20260928-perf_arm_spe_add_neoverse_v3ae-v1-1-738c9ed12d31@arm.com>
On 28/09/2026 17:12, Leo Yan wrote:
> Add all Neoverse V3AE revisions to the list so the common decoder can
> populate the memory source and snoop information.
>
> Signed-off-by: Leo Yan <leo.yan@arm.com>
> ---
> tools/perf/util/arm-spe.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/perf/util/arm-spe.c b/tools/perf/util/arm-spe.c
> index 7805a1a98a89a2853ad02ee7751472eddb1054ed..8d95df23be6f654caee77e9d155af7ebf5129c91 100644
> --- a/tools/perf/util/arm-spe.c
> +++ b/tools/perf/util/arm-spe.c
> @@ -626,6 +626,7 @@ static const struct midr_range common_ds_encoding_cpus[] = {
> MIDR_ALL_VERSIONS(MIDR_NEOVERSE_V1),
> MIDR_ALL_VERSIONS(MIDR_NEOVERSE_V2),
> MIDR_ALL_VERSIONS(MIDR_NEOVERSE_V3),
> + MIDR_ALL_VERSIONS(MIDR_NEOVERSE_V3AE),
> MIDR_ALL_VERSIONS(MIDR_NVIDIA_OLYMPUS),
> {},
> };
>
> ---
> base-commit: 0ae6fc78c5ce0dfd18d8712a50f0fd4602eff103
> change-id: 20260928-perf_arm_spe_add_neoverse_v3ae-917f280b2c7c
>
> Best regards,
Reviewed-by: James Clark <james.clark@linaro.org>
prev parent reply other threads:[~2026-09-29 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 16:12 [PATCH] perf arm-spe: Add Neoverse V3AE data source decoding Leo Yan
2026-09-28 16:17 ` sashiko-bot
2026-09-29 11:54 ` James Clark [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=50a0338e-e395-407c-bccd-cfb90f113e58@linaro.org \
--to=james.clark@linaro.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kieran.hejmadi@arm.com \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=namhyung@kernel.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.