From: Leo Yan <leo.yan@arm.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Leo Yan <leo.yan@arm.com>
Subject: [PATCH v3 25/25] perf arm_spe: Improve SIMD flags setting
Date: Wed, 12 Nov 2025 18:24:51 +0000 [thread overview]
Message-ID: <20251112-perf_support_arm_spev1-3-v3-25-e63c9829f9d9@arm.com> (raw)
In-Reply-To: <20251112-perf_support_arm_spev1-3-v3-0-e63c9829f9d9@arm.com>
Fill in ASE and SME operations for the SIMD arch field.
Also set the predicate flags for SVE and SME, but differences between
them: SME does not have a predicate flag, so the setting is based on
events. SVE provides a predicate flag to indicate whether the predicate
is disabled, which allows it to be distinguished into four cases: full
predicates, empty predicates, fully predicated, and disabled predicates.
After:
perf report -s +simd
...
0.06% 0.06% sve-test sve-test [.] setz [p] SVE
0.06% 0.06% sve-test [kernel.kallsyms] [k] do_raw_spin_lock
0.06% 0.06% sve-test sve-test [.] getz [p] SVE
0.06% 0.06% sve-test [kernel.kallsyms] [k] timekeeping_advance
0.06% 0.06% sve-test sve-test [.] getz [d] SVE
0.06% 0.06% sve-test [kernel.kallsyms] [k] update_load_avg
0.06% 0.06% sve-test sve-test [.] getz [e] SVE
0.05% 0.05% sve-test sve-test [.] setz [e] SVE
0.05% 0.05% sve-test [kernel.kallsyms] [k] update_curr
0.05% 0.05% sve-test sve-test [.] setz [d] SVE
0.05% 0.05% sve-test [kernel.kallsyms] [k] do_raw_spin_unlock
0.05% 0.05% sve-test [kernel.kallsyms] [k] timekeeping_update_from_shadow.constprop.0
0.05% 0.05% sve-test sve-test [.] getz [f] SVE
0.05% 0.05% sve-test sve-test [.] setz [f] SVE
Signed-off-by: Leo Yan <leo.yan@arm.com>
---
tools/perf/util/arm-spe.c | 26 ++++++++++++++++++++------
1 file changed, 20 insertions(+), 6 deletions(-)
diff --git a/tools/perf/util/arm-spe.c b/tools/perf/util/arm-spe.c
index 3b2d767f7a3e156594a69e7b546f3156cceb4951..6b76a6e9457adc650b7b790b4ab38cfe9eca5e22 100644
--- a/tools/perf/util/arm-spe.c
+++ b/tools/perf/util/arm-spe.c
@@ -353,12 +353,26 @@ static struct simd_flags arm_spe__synth_simd_flags(const struct arm_spe_record *
if (record->op & ARM_SPE_OP_SVE)
simd_flags.arch |= SIMD_OP_FLAGS_ARCH_SVE;
-
- if (record->type & ARM_SPE_SVE_PARTIAL_PRED)
- simd_flags.pred |= SIMD_OP_FLAGS_PRED_PARTIAL;
-
- if (record->type & ARM_SPE_SVE_EMPTY_PRED)
- simd_flags.pred |= SIMD_OP_FLAGS_PRED_EMPTY;
+ else if (record->op & ARM_SPE_OP_SME)
+ simd_flags.arch |= SIMD_OP_FLAGS_ARCH_SME;
+ else if (record->op & (ARM_SPE_OP_ASE | ARM_SPE_OP_SIMD_FP))
+ simd_flags.arch |= SIMD_OP_FLAGS_ARCH_ASE;
+
+ if (record->op & ARM_SPE_OP_SVE) {
+ if (!(record->op & ARM_SPE_OP_PRED))
+ simd_flags.pred = SIMD_OP_FLAGS_PRED_DISABLED;
+ else if (record->type & ARM_SPE_SVE_PARTIAL_PRED)
+ simd_flags.pred = SIMD_OP_FLAGS_PRED_PARTIAL;
+ else if (record->type & ARM_SPE_SVE_EMPTY_PRED)
+ simd_flags.pred = SIMD_OP_FLAGS_PRED_EMPTY;
+ else
+ simd_flags.pred = SIMD_OP_FLAGS_PRED_FULL;
+ } else {
+ if (record->type & ARM_SPE_SVE_PARTIAL_PRED)
+ simd_flags.pred = SIMD_OP_FLAGS_PRED_PARTIAL;
+ else if (record->type & ARM_SPE_SVE_EMPTY_PRED)
+ simd_flags.pred = SIMD_OP_FLAGS_PRED_EMPTY;
+ }
return simd_flags;
}
--
2.34.1
next prev parent reply other threads:[~2025-11-12 18:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 18:24 [PATCH v3 00/25] perf arm_spe: Extend operations Leo Yan
2025-11-12 18:24 ` [PATCH v3 01/25] perf arm_spe: Fix memset subclass in operation Leo Yan
2025-11-12 18:24 ` [PATCH v3 02/25] perf arm_spe: Unify operation naming Leo Yan
2025-11-12 18:24 ` [PATCH v3 03/25] perf arm_spe: Decode GCS operation Leo Yan
2025-11-12 18:24 ` [PATCH v3 04/25] perf arm_spe: Rename SPE_OP_PKT_IS_OTHER_SVE_OP macro Leo Yan
2025-11-12 18:24 ` [PATCH v3 05/25] perf arm_spe: Decode ASE and FP fields in other operation Leo Yan
2025-11-12 18:24 ` [PATCH v3 06/25] perf arm_spe: Decode SME data processing packet Leo Yan
2025-11-12 18:24 ` [PATCH v3 07/25] perf arm_spe: Remove unused operation types Leo Yan
2025-11-12 18:24 ` [PATCH v3 08/25] perf arm_spe: Consolidate " Leo Yan
2025-11-12 18:24 ` [PATCH v3 09/25] perf arm_spe: Introduce data processing macro for SVE operations Leo Yan
2025-11-12 18:24 ` [PATCH v3 10/25] perf arm_spe: Report register access in record Leo Yan
2025-11-12 18:24 ` [PATCH v3 11/25] perf arm_spe: Report MTE allocation tag " Leo Yan
2025-11-12 18:24 ` [PATCH v3 12/25] perf arm_spe: Report extended memory operations in records Leo Yan
2025-11-12 18:24 ` [PATCH v3 13/25] perf arm_spe: Report associated info for SVE / SME operations Leo Yan
2025-11-12 18:24 ` [PATCH v3 14/25] perf arm_spe: Report memset and memcpy in records Leo Yan
2025-11-12 18:24 ` [PATCH v3 15/25] perf arm_spe: Report GCS in record Leo Yan
2025-11-12 18:24 ` [PATCH v3 16/25] perf arm_spe: Expose SIMD information in other operations Leo Yan
2025-11-12 18:24 ` [PATCH v3 17/25] perf arm_spe: Synthesize memory samples for SIMD operations Leo Yan
2025-11-12 18:24 ` [PATCH v3 18/25] perf/uapi: Extend data source fields Leo Yan
2025-11-18 17:05 ` Leo Yan
2025-11-12 18:24 ` [PATCH v3 19/25] tools/include: Sync uapi/linux/perf.h with the kernel sources Leo Yan
2025-11-12 18:24 ` [PATCH v3 20/25] perf mem: Print extended fields Leo Yan
2025-11-12 18:24 ` [PATCH v3 21/25] perf arm_spe: Set extended fields in data source Leo Yan
2025-11-12 18:24 ` [PATCH v3 22/25] perf sort: Support sort ASE and SME Leo Yan
2025-11-12 18:24 ` [PATCH v3 23/25] perf sort: Sort disabled and full predicated flags Leo Yan
2025-11-12 18:24 ` [PATCH v3 24/25] perf report: Update document for SIMD flags Leo Yan
2025-11-12 18:24 ` Leo Yan [this message]
2025-11-13 17:01 ` [PATCH v3 00/25] perf arm_spe: Extend operations Ian Rogers
2025-11-17 7:20 ` Namhyung Kim
2025-11-18 10:23 ` James Clark
2025-11-19 18:10 ` 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=20251112-perf_support_arm_spev1-3-v3-25-e63c9829f9d9@arm.com \
--to=leo.yan@arm.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--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=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 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).