Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: James Clark <james.clark@linaro.org>
To: Linu Cherian <lcherian@marvell.com>,
	suzuki.poulose@arm.com, mike.leach@linaro.org
Cc: linux-arm-kernel@lists.infradead.org, coresight@lists.linaro.org,
	linux-kernel@vger.kernel.org, shuah@kernel.org,
	linux-kselftest@vger.kernel.org, sgoutham@marvell.com,
	gcherian@marvell.com
Subject: Re: [PATCH v2] selftests: arm coresight: sysfsmode testing
Date: Mon, 23 Dec 2024 14:38:28 +0000	[thread overview]
Message-ID: <b1ffbdda-f5b9-46da-bc78-e90ccfa41344@linaro.org> (raw)
In-Reply-To: <20241219142456.3474879-1-lcherian@marvell.com>



On 19/12/2024 2:24 pm, Linu Cherian wrote:
> Add sysfs mode selftest for ARM Coresight hardware tracer.
> 
> The test will run below sequence for all possible sinks for every
> trace source available on the system.
> 1. Enable source and sink device to start tracing in sysfs mode
> 3. Run a standard dd command to be traced
> 4. Stop tracing
> 5. Readback tracedata
> 
> - Test case is pass if the readback of tracedata is success else
> failure.
> - In case of ETR sink, the test is run with both default buffer mode and
> reserved buffer mode(if available).
> 
> Sample output:
> 
>   selftests: drivers/hwtracing/coresight: sysfs_test_trace.sh
>   Running sysfs trace with default settings
>   64+0 records in
>   64+0 records out
>   67108864 bytes (67 MB, 64 MiB) copied, 0.196945 s, 341 MB/s
>   32+0 records in
>   32+0 records out
>   16384 bytes (16 kB, 16 KiB) copied, 0.000805288 s, 20.3 MB/s
>   CoreSight path testing (CPU0 -> tmc_etf0): PASS
> 
> Signed-off-by: Linu Cherian <lcherian@marvell.com>
> ---
> Changelog from v1:
> - Added test description in commit message suggested by Shuah
> - Added config dependency file suggested by Shuah
> - Added TARGETS as suggested by James
> - Skipped TPIU as suggested by James
> - Added Reviewed-by tag
> 
> 
>   tools/testing/selftests/Makefile              |   1 +
>   .../drivers/hwtracing/coresight/Makefile      |   5 +
>   .../drivers/hwtracing/coresight/config        |   7 +
>   .../hwtracing/coresight/sysfs_test_trace.sh   | 146 ++++++++++++++++++
>   4 files changed, 159 insertions(+)
>   create mode 100644 tools/testing/selftests/drivers/hwtracing/coresight/Makefile
>   create mode 100644 tools/testing/selftests/drivers/hwtracing/coresight/config
>   create mode 100755 tools/testing/selftests/drivers/hwtracing/coresight/sysfs_test_trace.sh
> 

Reviewed-by: James Clark <james.clark@linaro.org>


      reply	other threads:[~2024-12-23 14:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19 14:24 [PATCH v2] selftests: arm coresight: sysfsmode testing Linu Cherian
2024-12-23 14:38 ` 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=b1ffbdda-f5b9-46da-bc78-e90ccfa41344@linaro.org \
    --to=james.clark@linaro.org \
    --cc=coresight@lists.linaro.org \
    --cc=gcherian@marvell.com \
    --cc=lcherian@marvell.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mike.leach@linaro.org \
    --cc=sgoutham@marvell.com \
    --cc=shuah@kernel.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