From: Leo Yan <leo.yan@arm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"Liang, Kan" <kan.liang@linux.intel.com>,
Besar Wicaksono <bwicaksono@nvidia.com>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Will Deacon <will@kernel.org>,
John Garry <john.g.garry@oracle.com>,
James Clark <james.clark@linaro.org>,
Mike Leach <mike.leach@linaro.org>
Cc: Leo Yan <leo.yan@arm.com>
Subject: [PATCH v4 0/5] perf arm-spe: Introduce metadata version 2
Date: Thu, 3 Oct 2024 19:42:57 +0100 [thread overview]
Message-ID: <20241003184302.190806-1-leo.yan@arm.com> (raw)
This patch series enhances Arm SPE metadata in the Perf file to a
version 2 format and maintains backward compatibility for metadata v1.
The version 2 metadata contains a global structure with fields for
metadata header version number, header size, CPU numbers. It also
expands to store per-CPU metadata, which includes the CPU logical
number in the kernel, MIDR, and capacity values associated with Arm SPE.
This patch set has been tested the perf to decode the Arm SPE metadata
v1 and v2.
Changes from v3:
- Fixed a compilation error (James)
- Added James' review tags.
Changes from v2:
- Added comment for arm_spe_find_cpus (Namhyung)
- Corrected resource releasing in arm_spe_save_cpu_header() and
arm_spe_info_fill() (Namhyung)
- Changed to use calloc() for allocating metadata pointer array
(Namhyung)
Changes from v1:
- Dropped LDS bit exposing from Arm SPE driver (Will Deacon).
- To simplify the change, this series did not include multiple AUX event
support.
Leo Yan (5):
perf arm-spe: Define metadata header version 2
perf arm-spe: Calculate meta data size
perf arm-spe: Save per CPU information in metadata
perf arm-spe: Support metadata version 2
perf arm-spe: Dump metadata with version 2
tools/perf/arch/arm64/util/arm-spe.c | 122 ++++++++++++++++++++-
tools/perf/util/arm-spe.c | 155 +++++++++++++++++++++++++--
tools/perf/util/arm-spe.h | 38 ++++++-
3 files changed, 299 insertions(+), 16 deletions(-)
--
2.34.1
next reply other threads:[~2024-10-03 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 18:42 Leo Yan [this message]
2024-10-03 18:42 ` [PATCH v4 1/5] perf arm-spe: Define metadata header " Leo Yan
2024-10-03 18:42 ` [PATCH v4 2/5] perf arm-spe: Calculate meta data size Leo Yan
2024-10-03 18:43 ` [PATCH v4 3/5] perf arm-spe: Save per CPU information in metadata Leo Yan
2024-10-03 18:43 ` [PATCH v4 4/5] perf arm-spe: Support metadata version 2 Leo Yan
2024-10-03 18:43 ` [PATCH v4 5/5] perf arm-spe: Dump metadata with " Leo Yan
2024-10-04 19:29 ` [PATCH v4 0/5] perf arm-spe: Introduce metadata " 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=20241003184302.190806-1-leo.yan@arm.com \
--to=leo.yan@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bwicaksono@nvidia.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--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
all inboxes | Powered by JetHome®