public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel•org>
To: James Clark <james.clark@linaro•org>
Cc: Suzuki K Poulose <suzuki.poulose@arm•com>,
	Mike Leach <mike.leach@arm•com>, Leo Yan <leo.yan@arm•com>,
	Peter Zijlstra <peterz@infradead•org>,
	Ingo Molnar <mingo@redhat•com>,
	Namhyung Kim <namhyung@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>,
	John Garry <john.g.garry@oracle•com>,
	Will Deacon <will@kernel•org>, Amir Ayupov <aaupov@meta•com>,
	coresight@lists•linaro.org, linux-arm-kernel@lists•infradead.org,
	linux-perf-users@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: [PATCH 0/2] perf cs-etm: Queue context packets for frontend
Date: Fri, 29 May 2026 11:55:36 -0300	[thread overview]
Message-ID: <ahmo6AF3oGOvdzT8@x1> (raw)
In-Reply-To: <20260526-james-cs-context-tracking-fix-v1-0-ebd602e18287@linaro.org>

On Tue, May 26, 2026 at 12:14:35PM +0100, James Clark wrote:
> Fix thread tracking when decoding Coresight trace and add a new test for
> it.
> 
> Unfortunately the test has to be added as a separate binary like the
> other existing Coresight workloads which needs a bit of makefile
> boilerplate. Ideally it would be a builtin Perf test workload, but Perf
> has a lot of dependencies and generates a lot of trace when starting up
> which makes tracing tests very slow because all that has to be decoded.
> 
> Hopefully I can find a generic way to enable Perf events at the
> beginning of the workload and then I can migrate everything from
> tools/perf/tests/shell/coresight to Perf test workloads, but that will
> have to be done as a separate change.
> 
> Signed-off-by: James Clark <james.clark@linaro•org>

James, there are some review comments from Sashiko, some looks
legitimate, wdyt?

- Arnaldo


  parent reply	other threads:[~2026-05-29 14:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26 11:14 [PATCH 0/2] perf cs-etm: Queue context packets for frontend James Clark
2026-05-26 11:14 ` [PATCH 1/2] " James Clark
2026-05-26 11:14 ` [PATCH 2/2] perf test cs-etm: Test thread attribution James Clark
2026-05-29 14:55 ` Arnaldo Carvalho de Melo [this message]
2026-05-29 14:58   ` [PATCH 0/2] perf cs-etm: Queue context packets for frontend James Clark

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=ahmo6AF3oGOvdzT8@x1 \
    --to=acme@kernel$(echo .)org \
    --cc=aaupov@meta$(echo .)com \
    --cc=adrian.hunter@intel$(echo .)com \
    --cc=alexander.shishkin@linux$(echo .)intel.com \
    --cc=coresight@lists$(echo .)linaro.org \
    --cc=irogers@google$(echo .)com \
    --cc=james.clark@linaro$(echo .)org \
    --cc=john.g.garry@oracle$(echo .)com \
    --cc=jolsa@kernel$(echo .)org \
    --cc=leo.yan@arm$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-perf-users@vger$(echo .)kernel.org \
    --cc=mark.rutland@arm$(echo .)com \
    --cc=mike.leach@arm$(echo .)com \
    --cc=mingo@redhat$(echo .)com \
    --cc=namhyung@kernel$(echo .)org \
    --cc=peterz@infradead$(echo .)org \
    --cc=suzuki.poulose@arm$(echo .)com \
    --cc=will@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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