mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: linux-perf-users@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	 coresight@lists.linaro.org, linux-kernel@vger.kernel.org,
	acme@kernel.org,  Mike Leach <mike.leach@arm.com>
Cc: suzuki.poulose@arm.com, leo.yan@arm.com, james.clark@linaro.org,
	 peterz@infradead.org, mingo@redhat.com, will@kernel.org,
	 mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
	jolsa@redhat.com,  irogers@google.com
Subject: Re: [PATCH v2 1/2] perf: tools: cs-etm: Fix print issue for Coresight debug in ETE/TRBE trace
Date: Thu, 19 Mar 2026 10:24:35 -0700	[thread overview]
Message-ID: <177394107584.14914.545377108953674625.b4-ty@b4> (raw)
In-Reply-To: <20260318103640.464982-1-mike.leach@arm.com>

On Wed, 18 Mar 2026 10:36:39 +0000, Mike Leach wrote:

> Building perf with CORESIGHT=1 and the optional CSTRACE_RAW=1 enables
> additional debug printing of raw trace data when using command:-
> perf report --dump.
> 
> This raw trace prints the CoreSight formatted trace frames, which may be
> used to investigate suspected issues with trace quality / corruption /
> decode.
> 
> [...]

Applied to perf-tools-next, thanks!

Best regards,
Namhyung


      parent reply	other threads:[~2026-03-19 17:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-18 10:36 Mike Leach
2026-03-18 10:36 ` [PATCH v2 2/2] perf: tools: cs-etm: Enhance raw Coresight trace debug display Mike Leach
2026-03-19 17:24 ` 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=177394107584.14914.545377108953674625.b4-ty@b4 \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=coresight@lists.linaro.org \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@redhat.com \
    --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=mike.leach@arm.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=suzuki.poulose@arm.com \
    --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®