From: Thomas Richter <tmricht@linux.ibm.com>
To: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
acme@kernel.org, namhyung@kernel.org
Cc: svens@linux.ibm.com, gor@linux.ibm.com, sumanthk@linux.ibm.com,
hca@linux.ibm.com, Thomas Richter <tmricht@linux.ibm.com>
Subject: [PATCH] perf test: Fix fails of perf stat --bpf-counters --for-each-cgroup on s390
Date: Thu, 7 Dec 2023 13:57:16 +0100 [thread overview]
Message-ID: <20231207125716.1947860-1-tmricht@linux.ibm.com> (raw)
On s390 this test fails very often, as can be observed in the output
below. This is caused by the second test function
check_cpu_list_counted(). The perf stat is triggered for 2 CPUs
0 and 1. On s390, which usually has a lot more CPUs, most often
this ends up in no counter increments on these 2 CPUs 0 and 1.
Fix this and trigger explicit workload on CPU 0 and 1 for
systemd. This is a better approach than calculating a long
list of CPUs (which is basicly the same as option -a), or
wait a longer period of time.
Output before:
# for i in $(seq 10)
> do ./perf test 100
> done
100: perf stat --bpf-counters --for-each-cgroup test : FAILED!
100: perf stat --bpf-counters --for-each-cgroup test : Ok
100: perf stat --bpf-counters --for-each-cgroup test : FAILED!
100: perf stat --bpf-counters --for-each-cgroup test : Ok
100: perf stat --bpf-counters --for-each-cgroup test : Ok
100: perf stat --bpf-counters --for-each-cgroup test : Ok
100: perf stat --bpf-counters --for-each-cgroup test : FAILED!
100: perf stat --bpf-counters --for-each-cgroup test : Ok
100: perf stat --bpf-counters --for-each-cgroup test : FAILED!
100: perf stat --bpf-counters --for-each-cgroup test : Ok
#
Output after:
# for i in $(seq 10);
do ./perf test 100;
done
100: perf stat --bpf-counters --for-each-cgroup test : Ok
100: perf stat --bpf-counters --for-each-cgroup test : Ok
100: perf stat --bpf-counters --for-each-cgroup test : Ok
100: perf stat --bpf-counters --for-each-cgroup test : Ok
100: perf stat --bpf-counters --for-each-cgroup test : Ok
100: perf stat --bpf-counters --for-each-cgroup test : Ok
100: perf stat --bpf-counters --for-each-cgroup test : Ok
100: perf stat --bpf-counters --for-each-cgroup test : Ok
100: perf stat --bpf-counters --for-each-cgroup test : Ok
100: perf stat --bpf-counters --for-each-cgroup test : Ok
#
Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
---
tools/perf/tests/shell/stat_bpf_counters_cgrp.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/perf/tests/shell/stat_bpf_counters_cgrp.sh b/tools/perf/tests/shell/stat_bpf_counters_cgrp.sh
index e75d0780dc78..f67602321403 100755
--- a/tools/perf/tests/shell/stat_bpf_counters_cgrp.sh
+++ b/tools/perf/tests/shell/stat_bpf_counters_cgrp.sh
@@ -60,6 +60,7 @@ check_system_wide_counted()
check_cpu_list_counted()
{
+ taskset -c 0,1 systemctl daemon-reexec &
check_cpu_list_counted_output=$(perf stat -C 0,1 --bpf-counters --for-each-cgroup ${test_cgroups} -e cpu-clock -x, taskset -c 1 sleep 1 2>&1)
if echo ${check_cpu_list_counted_output} | grep -q -F "<not "; then
echo "Some CPU events are not counted"
--
2.43.0
next reply other threads:[~2023-12-07 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 12:57 Thomas Richter [this message]
2023-12-07 23:26 ` [PATCH] perf test: Fix fails of perf stat --bpf-counters --for-each-cgroup on s390 Namhyung Kim
2023-12-08 11:07 ` Thomas Richter
2023-12-08 11:29 ` Thomas Richter
2023-12-11 23:13 ` 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=20231207125716.1947860-1-tmricht@linux.ibm.com \
--to=tmricht@linux.ibm.com \
--cc=acme@kernel.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=sumanthk@linux.ibm.com \
--cc=svens@linux.ibm.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).