From: Thomas Richter <tmricht@linux.ibm.com>
To: ian Rogers <irogers@google.com>
Cc: "linux-perf-use." <linux-perf-users@vger.kernel.org>,
Jan Polensky <japo@linux.ibm.com>,
Sumanth Korikkar <sumanthk@linux.ibm.com>
Subject: Test case '105: perf stat tests' fails for s390.
Date: Mon, 9 Mar 2026 14:04:28 +0100 [thread overview]
Message-ID: <61a60089-c0a1-47d8-91c7-c1fe68d19f5e@linux.ibm.com> (raw)
Ian,
test case '105: perf stat tests' fails for s390 (linux 7.0.0rc2) . It boils down to this command
# ./perf stat -C 0-31 -a true
Error:
No supported events found.
The first bad commit is this one:
commit cee275edcdb1 ("perf metricgroup: Don't early exit if no CPUID table exists")
Before this commit the output of above command is:
Output before that commit:
./perf stat -C 0-31 -a true
Performance counter stats for 'system wide':
105 context-switches # 3579.8 cs/sec cs_per_second
29.33 msec cpu-clock # 7.8 CPUs CPUs_utilized
34 cpu-migrations # 1159.2 migrations/sec migrations_per_second
52 page-faults # 1772.9 faults/sec page_faults_per_second
5,026,832 cpu-cycles # 0.2 GHz cycles_frequency
3,029,266 instructions # 0.6 instructions insn_per_cycle
0.000851608 seconds time elapsed
Since this is executed on an s390 LPAR, hardware event CPU_CYCLES is available, so it
should be used. This is something I will look into.
Also some other test cases fail after the bad commit:
./perf test 2>&1 | grep FAILED
99: perf stat CSV output linter : FAILED!
102: perf stat JSON output linter : FAILED!
104: perf stat STD output linter : FAILED!
105: perf stat tests : FAILED!
133: perftool-testsuite_report : FAILED!
Before the bad commit the output is
./perf test 2>&1 | grep FAILED
133: perftool-testsuite_report : FAILED!
Any ideas where to look too narrow down the debuggung are very welcome.
Thanks a lot.
--
Thomas Richter, Dept 3303, IBM s390 Linux Development, Boeblingen, Germany
--
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Wolfgang Wendt
Geschäftsführung: David Faller
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
next reply other threads:[~2026-03-09 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 13:04 Thomas Richter [this message]
2026-03-09 18:23 ` Test case '105: perf stat tests' fails for s390 Ian Rogers
2026-03-11 5:52 ` Thomas Richter
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=61a60089-c0a1-47d8-91c7-c1fe68d19f5e@linux.ibm.com \
--to=tmricht@linux.ibm.com \
--cc=irogers@google.com \
--cc=japo@linux.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=sumanthk@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