From: Ian Rogers <irogers@google.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
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>,
Kan Liang <kan.liang@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: [PATCH v2 2/2] perf test: Add sched latency and script shell tests
Date: Wed, 18 Jun 2025 17:20:34 -0700 [thread overview]
Message-ID: <20250619002034.97007-2-irogers@google.com> (raw)
In-Reply-To: <20250619002034.97007-1-irogers@google.com>
Add shell tests covering the `perf sched latency` and `perf sched
script` commands. The test creates 2 noploop processes on the same
forced CPU, it then checks that the process appears in the `perf
sched` output.
Signed-off-by: Ian Rogers <irogers@google.com>
---
v2: Skip the test if not root due to permissions.
---
tools/perf/tests/shell/sched.sh | 91 +++++++++++++++++++++++++++++++++
1 file changed, 91 insertions(+)
create mode 100755 tools/perf/tests/shell/sched.sh
diff --git a/tools/perf/tests/shell/sched.sh b/tools/perf/tests/shell/sched.sh
new file mode 100755
index 000000000000..0a4fe3f414e1
--- /dev/null
+++ b/tools/perf/tests/shell/sched.sh
@@ -0,0 +1,91 @@
+#!/bin/bash
+# perf sched tests
+# SPDX-License-Identifier: GPL-2.0
+
+set -e
+
+if [ "$(id -u)" != 0 ]; then
+ echo "[Skip] No root permission"
+ exit 2
+fi
+
+err=0
+perfdata=$(mktemp /tmp/__perf_test_sched.perf.data.XXXXX)
+PID1=0
+PID2=0
+
+cleanup() {
+ rm -f "${perfdata}"
+ rm -f "${perfdata}".old
+
+ trap - EXIT TERM INT
+}
+
+trap_cleanup() {
+ echo "Unexpected signal in ${FUNCNAME[1]}"
+ cleanup
+ exit 1
+}
+trap trap_cleanup EXIT TERM INT
+
+start_noploops() {
+ # Start two noploop workloads on CPU0 to trigger scheduling.
+ taskset -c 0 perf test -w noploop 10 &
+ PID1=$!
+ taskset -c 0 perf test -w noploop 10 &
+ PID2=$!
+
+ if ! grep -q 'Cpus_allowed_list:\s*0$' "/proc/$PID1/status"
+ then
+ echo "Sched [Error taskset did not work for the 1st noploop ($PID1)]"
+ grep Cpus_allowed /proc/$PID1/status
+ err=1
+ fi
+
+ if ! grep -q 'Cpus_allowed_list:\s*0$' "/proc/$PID2/status"
+ then
+ echo "Sched [Error taskset did not work for the 2nd noploop ($PID2)]"
+ grep Cpus_allowed /proc/$PID2/status
+ err=1
+ fi
+}
+
+cleanup_noploops() {
+ kill "$PID1" "$PID2"
+}
+
+test_sched_latency() {
+ echo "Sched latency"
+
+ start_noploops
+
+ perf sched record --no-inherit -o "${perfdata}" sleep 1
+ if ! perf sched latency -i "${perfdata}" | grep -q perf-noploop
+ then
+ echo "Sched latency [Failed missing output]"
+ err=1
+ fi
+
+ cleanup_noploops
+}
+
+test_sched_script() {
+ echo "Sched script"
+
+ start_noploops
+
+ perf sched record --no-inherit -o "${perfdata}" sleep 1
+ if ! perf sched script -i "${perfdata}" | grep -q perf-noploop
+ then
+ echo "Sched script [Failed missing output]"
+ err=1
+ fi
+
+ cleanup_noploops
+}
+
+test_sched_latency
+test_sched_script
+
+cleanup
+exit $err
--
2.50.0.rc2.701.gf1e915cc24-goog
next prev parent reply other threads:[~2025-06-19 0:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 0:20 [PATCH v2 1/2] perf test workload noploop: Name the noploop process Ian Rogers
2025-06-19 0:20 ` Ian Rogers [this message]
2025-06-20 10:01 ` [PATCH v2 2/2] perf test: Add sched latency and script shell tests James Clark
2025-06-20 19:41 ` Namhyung Kim
2025-06-28 1:25 ` Ian Rogers
2025-06-20 10:01 ` [PATCH v2 1/2] perf test workload noploop: Name the noploop process James Clark
2025-06-20 19:36 ` Namhyung Kim
2025-06-23 15:12 ` Ian Rogers
2025-06-23 17:45 ` Arnaldo Carvalho de Melo
2025-06-23 18:05 ` Ian Rogers
2025-06-23 18:14 ` Namhyung Kim
2025-06-23 19:18 ` Arnaldo Carvalho de Melo
2025-06-23 19:41 ` Ian Rogers
2025-06-23 23:14 ` Namhyung Kim
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=20250619002034.97007-2-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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®