mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Clark <james.clark@linaro.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: John Garry <john.g.garry@oracle.com>,
	Will Deacon <will@kernel.org>, Mike Leach <mike.leach@linaro.org>,
	Leo Yan <leo.yan@linux.dev>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@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>,
	Al Grant <al.grant@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] perf arm_spe: Dump IMPDEF events
Date: Tue, 7 Apr 2026 09:18:01 +0100	[thread overview]
Message-ID: <d45195c7-ad32-4bc0-8d60-4b242cb3e2a7@linaro.org> (raw)
In-Reply-To: <adP44THdD-HBB8cY@google.com>



On 06/04/2026 7:18 pm, Namhyung Kim wrote:
> Hi James,
> 
> On Wed, Apr 01, 2026 at 03:25:48PM +0100, James Clark wrote:
>> In the Arm SPE raw data dump, IMPDEF events aren't printed. Add the
>> ability to add names for some known events or print the raw event number
>> for unknown events.
>>
>> For example:
>>
>>    $ perf report -D
>>
>>    ... ARM SPE data: size 0xd000 bytes
>>    00000000: b0 18 c6 32 80 00 80 ff a0  PC 0xff80008032c618 el1 ns=1
>>    00000009: 64 e7 42 00 00              CONTEXT 0x42e7 el1
>>    0000000e: 00 00 00 00 00              PAD
>>    00000013: 49 00                       LD GP-REG
>>    00000015: 52 16 10               	EV RETIRED L1D-ACCESS TLB-ACCESS
>>
>> On N1 the event line becomes:
>>
>>    00000015: 52 16 10                    EV RETIRED L1D-ACCESS TLB-ACCESS LATE-PREFETCH
>>
>> Or on other cores it becomes:
>>
>>    00000015: 52 16 10                    EV RETIRED L1D-ACCESS TLB-ACCESS IMPDEF:12
>>
>> Signed-off-by: James Clark <james.clark@linaro.org>
>> ---
>> James Clark (4):
>>        perf arm_spe: Make a function to get the MIDR
>>        perf arm_spe: Turn event name mappings into an array
>>        perf arm_spe: Decode Arm N1 IMPDEF events
>>        perf arm_spe: Print remaining IMPDEF event numbers
> 
> Will you send v2 or do you think it's ok to merge v1?
> 
> Thanks,
> Namhyung
> 

I'll send a v2, thanks.

>>
>>   tools/perf/util/arm-spe-decoder/Build              |   2 +
>>   .../util/arm-spe-decoder/arm-spe-pkt-decoder.c     | 147 ++++++++++++++-------
>>   .../util/arm-spe-decoder/arm-spe-pkt-decoder.h     |   5 +-
>>   tools/perf/util/arm-spe.c                          |  49 ++++---
>>   4 files changed, 135 insertions(+), 68 deletions(-)
>> ---
>> base-commit: 74e2dbe7be5037a5e5eed6bc1ad562747ac88566
>> change-id: 20260331-james-spe-impdef-decode-d944f4fdcff7
>>
>> Best regards,
>> -- 
>> James Clark <james.clark@linaro.org>
>>


      reply	other threads:[~2026-04-07  8:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01 14:25 James Clark
2026-04-01 14:25 ` [PATCH 1/4] perf arm_spe: Make a function to get the MIDR James Clark
2026-04-02  8:55   ` Leo Yan
2026-04-01 14:25 ` [PATCH 2/4] perf arm_spe: Turn event name mappings into an array James Clark
2026-04-02  9:13   ` Leo Yan
2026-04-02  9:48     ` James Clark
2026-04-02 15:30   ` Ian Rogers
2026-04-01 14:25 ` [PATCH 3/4] perf arm_spe: Decode Arm N1 IMPDEF events James Clark
2026-04-02  9:32   ` Leo Yan
2026-04-02  9:49     ` James Clark
2026-04-02 15:26   ` Ian Rogers
2026-04-07 12:35     ` James Clark
2026-04-07 18:26       ` Ian Rogers
2026-04-08  8:47         ` James Clark
2026-04-10  4:51           ` Namhyung Kim
2026-04-01 14:25 ` [PATCH 4/4] perf arm_spe: Print remaining IMPDEF event numbers James Clark
2026-04-02  9:46   ` Leo Yan
2026-04-06 18:18 ` [PATCH 0/4] perf arm_spe: Dump IMPDEF events Namhyung Kim
2026-04-07  8:18   ` 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=d45195c7-ad32-4bc0-8d60-4b242cb3e2a7@linaro.org \
    --to=james.clark@linaro.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=al.grant@arm.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=john.g.garry@oracle.com \
    --cc=jolsa@kernel.org \
    --cc=leo.yan@linux.dev \
    --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=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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®