From: carsten.haitzler@foss.arm.com
To: linux-kernel@vger.kernel.org
Cc: coresight@lists.linaro.org, suzuki.poulose@arm.com,
mathieu.poirier@linaro.org, mike.leach@linaro.org,
leo.yan@linaro.org, linux-perf-users@vger.kernel.org,
acme@kernel.org
Subject: [PATCH v8 09/13] perf test: Add thread loop test shell scripts
Date: Tue, 6 Sep 2022 11:30:40 +0100 [thread overview]
Message-ID: <20220906103044.761250-10-carsten.haitzler@foss.arm.com> (raw)
In-Reply-To: <20220906103044.761250-1-carsten.haitzler@foss.arm.com>
From: Carsten Haitzler <carsten.haitzler@arm.com>
Add a script to drive the thread loop test that gathers data so
it passes a minimum bar (in this case do we get any perf context data
for every thread).
Signed-off-by: Carsten Haitzler <carsten.haitzler@arm.com>
---
.../coresight/thread_loop_check_tid_10.sh | 19 +++++++++++++++++++
.../coresight/thread_loop_check_tid_2.sh | 19 +++++++++++++++++++
2 files changed, 38 insertions(+)
create mode 100755 tools/perf/tests/shell/coresight/thread_loop_check_tid_10.sh
create mode 100755 tools/perf/tests/shell/coresight/thread_loop_check_tid_2.sh
diff --git a/tools/perf/tests/shell/coresight/thread_loop_check_tid_10.sh b/tools/perf/tests/shell/coresight/thread_loop_check_tid_10.sh
new file mode 100755
index 000000000000..7c13636fc778
--- /dev/null
+++ b/tools/perf/tests/shell/coresight/thread_loop_check_tid_10.sh
@@ -0,0 +1,19 @@
+#!/bin/sh -e
+# CoreSight / Thread Loop 10 Threads - Check TID
+
+# SPDX-License-Identifier: GPL-2.0
+# Carsten Haitzler <carsten.haitzler@arm.com>, 2021
+
+TEST="thread_loop"
+. $(dirname $0)/../lib/coresight.sh
+ARGS="10 1"
+DATV="check-tid-10th"
+DATA="$DATD/perf-$TEST-$DATV.data"
+STDO="$DATD/perf-$TEST-$DATV.stdout"
+
+SHOW_TID=1 perf record -s $PERFRECOPT -o "$DATA" "$BIN" $ARGS > $STDO
+
+perf_dump_aux_tid_verify "$DATA" "$STDO"
+
+err=$?
+exit $err
diff --git a/tools/perf/tests/shell/coresight/thread_loop_check_tid_2.sh b/tools/perf/tests/shell/coresight/thread_loop_check_tid_2.sh
new file mode 100755
index 000000000000..a067145af43c
--- /dev/null
+++ b/tools/perf/tests/shell/coresight/thread_loop_check_tid_2.sh
@@ -0,0 +1,19 @@
+#!/bin/sh -e
+# CoreSight / Thread Loop 2 Threads - Check TID
+
+# SPDX-License-Identifier: GPL-2.0
+# Carsten Haitzler <carsten.haitzler@arm.com>, 2021
+
+TEST="thread_loop"
+. $(dirname $0)/../lib/coresight.sh
+ARGS="2 20"
+DATV="check-tid-2th"
+DATA="$DATD/perf-$TEST-$DATV.data"
+STDO="$DATD/perf-$TEST-$DATV.stdout"
+
+SHOW_TID=1 perf record -s $PERFRECOPT -o "$DATA" "$BIN" $ARGS > $STDO
+
+perf_dump_aux_tid_verify "$DATA" "$STDO"
+
+err=$?
+exit $err
--
2.32.0
next prev parent reply other threads:[~2022-09-06 10:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 10:30 [PATCH v8 00/13] perf: test: Add trace data quality tests for CoreSight carsten.haitzler
2022-09-06 10:30 ` [PATCH v8 01/13] perf test: Add CoreSight shell lib shared code for future tests carsten.haitzler
2022-09-06 10:30 ` [PATCH v8 02/13] perf test: Add build infra for perf test tools for CoreSight tests carsten.haitzler
2022-09-08 12:44 ` Leo Yan
2022-09-06 10:30 ` [PATCH v8 03/13] perf test: Add asm pureloop test tool carsten.haitzler
2022-09-06 10:30 ` [PATCH v8 04/13] perf test: Add asm pureloop test shell script carsten.haitzler
2022-09-06 10:30 ` [PATCH v8 05/13] perf test: Add git ignore for perf data generated by the CoreSight tests carsten.haitzler
2022-09-06 10:30 ` [PATCH v8 06/13] perf test: Add memcpy thread test tool carsten.haitzler
2022-09-06 10:30 ` [PATCH v8 07/13] perf test: Add memcpy thread test shell script carsten.haitzler
2022-09-06 10:30 ` [PATCH v8 08/13] perf test: Add thread loop test tool carsten.haitzler
2022-09-06 10:30 ` carsten.haitzler [this message]
2022-09-06 10:30 ` [PATCH v8 10/13] perf test: Add unroll thread " carsten.haitzler
2022-09-06 10:30 ` [PATCH v8 11/13] perf test: Add unroll thread test shell script carsten.haitzler
2022-09-06 10:30 ` [PATCH v8 12/13] perf test: Add git ignore for tmp and output files of CoreSight tests carsten.haitzler
2022-09-06 10:30 ` [PATCH v8 13/13] perf test: Add relevant documentation about CoreSight testing carsten.haitzler
2022-09-07 2:59 ` kernel test robot
2022-09-08 12:27 ` Leo Yan
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=20220906103044.761250-10-carsten.haitzler@foss.arm.com \
--to=carsten.haitzler@foss.arm.com \
--cc=acme@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.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;
as well as URLs for NNTP newsgroup(s).