From: Namhyung Kim <namhyung@kernel.org>
To: James Clark <james.clark@linaro.org>
Cc: Leo Yan <leo.yan@arm.com>, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Mark Rutland <mark.rutland@arm.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 00/25] perf arm_spe: Extend operations
Date: Wed, 19 Nov 2025 10:10:51 -0800 [thread overview]
Message-ID: <aR4IK-3rcbdbv2Er@google.com> (raw)
In-Reply-To: <ed4a5e23-f2f0-4f02-8b0a-e97329cb313f@linaro.org>
On Tue, Nov 18, 2025 at 10:23:57AM +0000, James Clark wrote:
>
>
> On 17/11/2025 7:20 am, Namhyung Kim wrote:
> > Hello,
> >
> > On Thu, Nov 13, 2025 at 09:01:47AM -0800, Ian Rogers wrote:
> > > On Wed, Nov 12, 2025 at 10:24 AM Leo Yan <leo.yan@arm.com> wrote:
> > > >
> > > > This series enhances tooling to support new operations:
> > > >
> > > > - Support for MTE tag since Arm SPE v1.3;
> > > > - Support for Advanced SIMD extension and SVE operations;
> > > > - Support memcpy, memset and GCS operations;
> > > > - Support extended operations for atomic, Acquire/Release and
> > > > Exclusive instructions.
> > > > - Enhance the data source for associated info, like floating-point,
> > > > conditional, data processing, etc.
> > > >
> > > > This series is divided into three parts:
> > > >
> > > > Patches 01 ~ 06: Support raw dump for new operations;
> > > > Patches 07 ~ 17: Export the operation info into records, so that the
> > > > information can be later consumed by samples.
> > > > Patches 18 ~ 25: Set the operation info into sample's data source and
> > > > SIMD flag, and updated the document.
> > > >
> > > > This patch series is tested on FVP for native parsing and x86_64 for
> > > > cross parsing.
> > > >
> > > > Signed-off-by: Leo Yan <leo.yan@arm.com>
> > >
> > > Reviewed-by: Ian Rogers <irogers@google.com>
> >
> > Can I get some comments from ARM folks? I think I can merge part 1 and
> > 2 before changing the kernel interface.
> >
> > Thanks,
> > Namhyung
> >
>
> Reviewed-by: James Clark <james.clark@linaro.org>
Thanks, applied the patch up to 17 to perf-tools-next!
Best regards,
Namhyung
prev parent reply other threads:[~2025-11-19 18:11 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 ` [PATCH v3 25/25] perf arm_spe: Improve SIMD flags setting Leo Yan
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 [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=aR4IK-3rcbdbv2Er@google.com \
--to=namhyung@kernel.org \
--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=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=mingo@redhat.com \
--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).