From: Leo Yan <leo.yan@arm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
James Clark <james.clark@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
"Liang, Kan" <kan.liang@linux.intel.com>,
Will Deacon <will@kernel.org>, Mike Leach <mike.leach@linaro.org>,
Besar Wicaksono <bwicaksono@nvidia.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: Leo Yan <leo.yan@arm.com>
Subject: [PATCH v2 0/7] perf arm-spe: Refactor data source encoding
Date: Sat, 14 Sep 2024 23:08:54 +0100 [thread overview]
Message-ID: <20240914220901.756177-1-leo.yan@arm.com> (raw)
As more Arm CPU variants (not only Neoverse CPUs) support data source
encoding, they share the same format for the data source packet.
To extend supporting these CPU variants for Arm SPE data source, this
series refactors the code. It converts the Neoverse specific naming to
the common naming, and then based on the MIDR stored in the metadata to
decide if the CPU follows up the common encoding format.
At the last, it extends CPU list for Neoverse-V2 and Cortex CPUs.
This patch series is dependent on the metadata version 2 series [1] for
retrieving CPU MIDR. It has been verified for per CPU mode and per
thread mode on Cortex-A725 CPUs.
[1] https://lore.kernel.org/linux-perf-users/20240914215458.751802-1-leo.yan@arm.com/T/#t
Changes from v1:
- Dropped LDS bit checking in data source parsing.
Besar Wicaksono (1):
perf arm-spe: Add Neoverse-V2 to common data source encoding list
Leo Yan (6):
perf arm-spe: Rename arm_spe__synth_data_source_generic()
perf arm-spe: Rename the common data source encoding
perf arm-spe: Introduce arm_spe__is_homogeneous()
perf arm-spe: Use metadata to decide the data source feature
perf arm-spe: Remove the unused 'midr' field
perf arm-spe: Add Cortex CPUs to common data source encoding list
.../util/arm-spe-decoder/arm-spe-decoder.h | 18 +--
tools/perf/util/arm-spe.c | 135 +++++++++++++++---
2 files changed, 121 insertions(+), 32 deletions(-)
--
2.34.1
next reply other threads:[~2024-09-14 22:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 22:08 Leo Yan [this message]
2024-09-14 22:08 ` [PATCH v2 1/7] perf arm-spe: Rename arm_spe__synth_data_source_generic() Leo Yan
2024-09-14 22:08 ` [PATCH v2 2/7] perf arm-spe: Rename the common data source encoding Leo Yan
2024-09-14 22:08 ` [PATCH v2 3/7] perf arm-spe: Introduce arm_spe__is_homogeneous() Leo Yan
2024-09-14 22:08 ` [PATCH v2 4/7] perf arm-spe: Use metadata to decide the data source feature Leo Yan
2024-09-14 22:08 ` [PATCH v2 5/7] perf arm-spe: Remove the unused 'midr' field Leo Yan
2024-09-14 22:09 ` [PATCH v2 6/7] perf arm-spe: Add Neoverse-V2 to common data source encoding list Leo Yan
2024-09-14 22:09 ` [PATCH v2 7/7] perf arm-spe: Add Cortex CPUs " Leo Yan
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=20240914220901.756177-1-leo.yan@arm.com \
--to=leo.yan@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=bwicaksono@nvidia.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.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=mike.leach@linaro.org \
--cc=namhyung@kernel.org \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).