The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@arm.com>
To: James Clark <james.clark@linaro.org>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>,
	Mike Leach <mike.leach@arm.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
	Ian Rogers <irogers@google.com>, Amir Ayupov <aaupov@meta.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Paschalis Mpeis <Paschalis.Mpeis@arm.com>,
	coresight@lists.linaro.org, linux-perf-users@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 08/18] perf test cs-etm: Replace memcpy test with raw dump stress test
Date: Wed, 3 Jun 2026 19:16:55 +0100	[thread overview]
Message-ID: <20260603181655.GK101133@e132581.arm.com> (raw)
In-Reply-To: <882922c0-042a-4108-bc2f-cec443d0db9f@linaro.org>

On Wed, Jun 03, 2026 at 05:11:30PM +0100, James Clark wrote:

[...]

> > I am not sure how we can map 2MiB trace data to 50MiB+ raw dump.  This
> 
> Why not? Decoding it is roughly equal to decompressing it, and with that
> amount of trace the small differences in compressibility average out and you
> do get the same amount every time. I think if we got less than half the
> amount expected then it would be worth investigating.

TBH, I don't know how to calculate decompressing size. Seems to me this
is a heuristics value.

Maybe Mike could help to confirm if this works or not.

[...]

> That would work, but that wouldn't be as thorough. The first thing it prints
> is " CoreSight .* Trace data: size .* bytes". If it stops working half way
> through or prints nothing then the test will still pass.
> 
> The reason I wanted to add a stress test is because all of the other tests
> have been reduced to just a few kb of trace so we have nothing that opens a
> file with a more reasonable amount of data.
> 
> I suppose with your suggestion we'd still check the exit code, but that's
> about it.

Is it possible to locate the end of raw dump with a specific parttern? like:

  Idx:36061; ID:1a;       I_IGNORE : Ignore.
  Idx:36062; ID:1a;       I_IGNORE : Ignore.
  Idx:36063; ID:1a;       I_IGNORE : Ignore.
  Idx:36064; ID:1a;       I_IGNORE : Ignore.
  Idx:36065; ID:1a;       I_IGNORE : Ignore.
  Idx:36066; ID:1a;       I_IGNORE : Ignore.
  Idx:36067; ID:1a;       I_IGNORE : Ignore.
  Idx:36068; ID:1a;       I_IGNORE : Ignore.
  Idx:36069; ID:1a;       I_IGNORE : Ignore.
  Idx:36070; ID:1a;       I_IGNORE : Ignore.
  Idx:36071; ID:1a;       I_IGNORE : Ignore.
  Idx:36072; ID:1a;       I_IGNORE : Ignore.
  Idx:36073; ID:1a;       I_IGNORE : Ignore.
  Idx:36074; ID:1a;       I_IGNORE : Ignore.
  Idx:36075; ID:1a;       I_IGNORE : Ignore.
  Idx:36076; ID:1a;       I_IGNORE : Ignore.
  Idx:36077; ID:1a;       I_IGNORE : Ignore.
  Idx:36078; ID:1a;       I_IGNORE : Ignore.
  Idx:36079; ID:1a;       I_IGNORE : Ignore.
  Idx:36080; ID:1a;       I_IGNORE : Ignore.
  Idx:36081; ID:1a;       I_IGNORE : Ignore.
  Idx:36082; ID:1a;       I_IGNORE : Ignore.
  Idx:36083; ID:1a;       I_IGNORE : Ignore.
  Idx:36084; ID:1a;       I_IGNORE : Ignore.
  Idx:36085; ID:1a;       I_IGNORE : Ignore.
  Idx:36086; ID:1a;       I_IGNORE : Ignore.
  Idx:36087; ID:1a;       I_IGNORE : Ignore.
  Idx:36088; ID:1a;       I_IGNORE : Ignore.
  Idx:36089; ID:1a;       I_IGNORE : Ignore.
  Idx:36090; ID:1a;       I_IGNORE : Ignore.
  Idx:36091; ID:1a;       I_IGNORE : Ignore.
  Idx:36092; ID:1a;       I_IGNORE : Ignore.
  Idx:36093; ID:1a;       I_IGNORE : Ignore.
  Idx:36094; ID:1a;       I_IGNORE : Ignore.
  Idx:36095; ID:1a;       I_IGNORE : Ignore.

Thanks,
Leo

  reply	other threads:[~2026-06-03 18:16 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02 14:26 [PATCH v2 00/18] perf cs-etm: Queue context packets for frontend James Clark
2026-06-02 14:26 ` [PATCH v2 01/18] " James Clark
2026-06-03  9:08   ` Leo Yan
2026-06-02 14:26 ` [PATCH v2 02/18] perf test: Add workload-ctl option James Clark
2026-06-03 10:40   ` Leo Yan
2026-06-03 10:46     ` James Clark
2026-06-03 10:50     ` Leo Yan
2026-06-03 19:21   ` Arnaldo Carvalho de Melo
2026-06-03 19:22     ` Arnaldo Carvalho de Melo
2026-06-02 14:26 ` [PATCH v2 03/18] perf test: Add a workload that forces context switches James Clark
2026-06-03 11:06   ` Leo Yan
2026-06-03 11:17     ` James Clark
2026-06-02 14:26 ` [PATCH v2 04/18] perf test cs-etm: Test process attribution James Clark
2026-06-03 11:10   ` Leo Yan
2026-06-03 11:20     ` James Clark
2026-06-02 14:26 ` [PATCH v2 05/18] perf test: Add deterministic workload James Clark
2026-06-03 11:27   ` Leo Yan
2026-06-03 13:10     ` James Clark
2026-06-03 13:43       ` Leo Yan
2026-06-03 15:53         ` James Clark
2026-06-02 14:26 ` [PATCH v2 06/18] perf test cs-etm: Replace unroll loop thread with deterministic decode test James Clark
2026-06-03 14:08   ` Leo Yan
2026-06-03 16:01     ` James Clark
2026-06-03 17:08       ` Leo Yan
2026-06-04 13:21         ` James Clark
2026-06-02 14:26 ` [PATCH v2 07/18] perf test cs-etm: Remove asm_pure_loop test James Clark
2026-06-03 14:10   ` Leo Yan
2026-06-02 14:26 ` [PATCH v2 08/18] perf test cs-etm: Replace memcpy test with raw dump stress test James Clark
2026-06-03 14:36   ` Leo Yan
2026-06-03 16:11     ` James Clark
2026-06-03 18:16       ` Leo Yan [this message]
2026-06-02 14:26 ` [PATCH v2 09/18] perf test: Add named_threads workload James Clark
2026-06-03 14:54   ` Leo Yan
2026-06-03 16:12     ` James Clark
2026-06-03 17:36       ` Leo Yan
2026-06-02 14:26 ` [PATCH v2 10/18] perf test cs-etm: Test decoding for concurrent threads test James Clark
2026-06-03 14:56   ` Leo Yan
2026-06-02 14:26 ` [PATCH v2 11/18] perf test cs-etm: Remove duplicate branch tests James Clark
2026-06-03 17:11   ` Leo Yan
2026-06-02 14:26 ` [PATCH v2 12/18] perf test cs-etm: Reduce snapshot size James Clark
2026-06-03 17:12   ` Leo Yan
2026-06-02 14:26 ` [PATCH v2 13/18] perf test cs-etm: Speed up basic test James Clark
2026-06-03 17:17   ` Leo Yan
2026-06-02 14:26 ` [PATCH v2 14/18] perf test cs-etm: Remove unused Coresight workloads James Clark
2026-06-03 17:25   ` Leo Yan
2026-06-04 13:31     ` James Clark
2026-06-04 13:34       ` James Clark
2026-06-02 14:26 ` [PATCH v2 15/18] perf test cs-etm: Make disassembly test use kcore James Clark
2026-06-03 17:32   ` Leo Yan
2026-06-04 12:18     ` James Clark
2026-06-02 14:26 ` [PATCH v2 16/18] perf test cs-etm: Add all branch instructions to test James Clark
2026-06-03 17:49   ` Leo Yan
2026-06-02 14:26 ` [PATCH v2 17/18] perf test cs-etm: Speed up disassembly test James Clark
2026-06-03 17:50   ` Leo Yan
2026-06-02 14:27 ` [PATCH v2 18/18] perf test cs-etm: Move existing tests to coresight folder James Clark
2026-06-03 18:02   ` Leo Yan
2026-06-04 12:22     ` 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=20260603181655.GK101133@e132581.arm.com \
    --to=leo.yan@arm.com \
    --cc=Paschalis.Mpeis@arm.com \
    --cc=aaupov@meta.com \
    --cc=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=corbet@lwn.net \
    --cc=coresight@lists.linaro.org \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mike.leach@arm.com \
    --cc=namhyung@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=suzuki.poulose@arm.com \
    /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