From: Leo Yan <leo.yan@arm.com>
To: Mike Leach <mike.leach@arm.com>
Cc: linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, coresight@lists.linaro.org,
linux-kernel@vger.kernel.org, acme@kernel.org,
leo.yan@linaro.org, peterz@infradead.org, mingo@redhat.com,
will@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
namhyung@kernel.org
Subject: Re: [PATCH 2/2] perf: tools: cs-etm: Enhance raw Coresight trace debug display
Date: Fri, 13 Mar 2026 14:45:18 +0000 [thread overview]
Message-ID: <20260313144518.GN4153946@e132581.arm.com> (raw)
In-Reply-To: <20260313132129.2743468-3-mike.leach@arm.com>
On Fri, Mar 13, 2026 at 01:21:29PM +0000, Coresight ML wrote:
[...]
> ETE trace output changes from:
>
> Idx:0; ID:14; I_ASYNC : Alignment Synchronisation.
> Idx:12; ID:14; I_TRACE_INFO : Trace Info.; INFO=0x0 { CC.0, TSTATE.0 };
> Decoder Sync point TINFO
> Idx:15; ID:14; I_ADDR_L_64IS0 : Address, Long, 64 bit, IS0.;
> Addr=0xFFFF80007CF7F56C;
> becoming:
>
> Idx:0; ID:14;[0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x80];
> I_ASYNC : Alignment Synchronisation.
> Idx:12; ID:14; [0x01 0x01 0x00 ]; I_TRACE_INFO : Trace Info.; INFO=0x0
> { CC.0, TSTATE.0 }; Decoder Sync point TINFO
> Idx:15; ID:14; [0x9d 0x5b 0x7a 0xf7 0x7c 0x00 0x80 0xff 0xff ];
> I_ADDR_L_64IS0 : Address, Long, 64 bit, IS0.;
> Addr=0xFFFF80007CF7F56C;
>
> Signed-off-by: Mike Leach <mike.leach@arm.com>
LGTM and I tested it:
Tested-by: Leo Yan <leo.yan@arm.com>
next prev parent reply other threads:[~2026-03-13 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 13:21 [PATCH 0/2] perf: tools: cs-etm: Fixes for CoreSight debug dump Mike Leach
2026-03-13 13:21 ` [PATCH 1/2] perf: tools: cs-etm: Fix print issue for Coresight debug in ETE/TRBE trace Mike Leach
2026-03-13 14:42 ` Leo Yan
2026-03-17 15:09 ` Mike Leach
2026-03-13 13:21 ` [PATCH 2/2] perf: tools: cs-etm: Enhance raw Coresight trace debug display Mike Leach
2026-03-13 14:45 ` Leo Yan [this message]
2026-03-18 12:56 ` Arnaldo Carvalho de Melo
2026-03-18 18:45 ` 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=20260313144518.GN4153946@e132581.arm.com \
--to=leo.yan@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=jolsa@redhat.com \
--cc=leo.yan@linaro.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=mike.leach@arm.com \
--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