From: Thomas Richter <tmricht@linux.ibm.com>
To: "linux-perf-use." <linux-perf-users@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Ian Rogers <irogers@google.com>
Subject: perf test failures in linux-next on s390
Date: Tue, 13 Jun 2023 14:54:51 +0200 [thread overview]
Message-ID: <d5319870-7569-c353-1777-31ee090f8da8@linux.ibm.com> (raw)
Hi all,
I have run the perf test suite on the current 6.4rc6 kernel and see just one error:
# ./perf test 2>&1 | fgrep FAILED
fgrep: warning: fgrep is obsolescent; using grep -F
42.3: BPF prologue generation : FAILED!
#
However when I download the linux-next tree and build kernel and perf
tool with the same kernel config file, I get a bunch of failing test cases,
many with perf tool dumping core:
# perf test 2>&1 | fgrep FAILED
fgrep: warning: fgrep is obsolescent; using grep -F
6.1: Test event parsing : FAILED!
10.3: Parsing of PMU event table metrics : FAILED!
10.4: Parsing of PMU event table metrics with fake PMUs : FAILED!
17: Setup struct perf_event_attr : FAILED!
24: Number of exit events of a simple workload : FAILED! core-dump
28: Use a dummy software event to keep tracking : FAILED!
35: Track with sched_switch : FAILED!
42.3: BPF prologue generation : FAILED!
66: Parse and process metrics : FAILED!
68: Event expansion for cgroups : FAILED!
69.2: Perf time to TSC : FAILED! core-dump
74: build id cache operations : FAILED! core-dump
81: kernel lock contention analysis test : FAILED!
86: Zstd perf.data compression/decompression : FAILED! core-dump
87: perf record tests : FAILED! core-dump
94: perf all metricgroups test : FAILED!
95: perf all metrics test : FAILED!
106: Test java symbol : FAILED! core-dump
#
I am afraid this will show up pretty soon in the linux tree.
I am going to look into each failure in the next few days.
What I already found out is that many test cases now fail due to the
event/PMU rework, here is one example:
# perf test -Fvvvv 95
95: perf all metrics test
--- start ---
Testing cpi
....
Metric 'transaction' not printed in:
Error:
The TX_NC_TABORT event is not supported.
---- end ----
perf all metrics test: FAILED!
# ls -l /sys/devices/cpum_cf/events/TX_NC_TABORT
-r--r--r--. 1 root root 4096 Jun 13 13:49 /sys/devices/cpum_cf/events/TX_NC_TABORT
#
As can be seen, the event is definitely there and supported.
This same test case succeeds in the linux tree!
Hopefully I can sort out some of the failures before this code show up
in the linux tree.
--
Thomas Richter, Dept 3303, IBM s390 Linux Development, Boeblingen, Germany
--
Vorsitzender des Aufsichtsrats: Gregor Pillen
Geschäftsführung: David Faller
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
next reply other threads:[~2023-06-13 12:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 12:54 Thomas Richter [this message]
2023-06-13 14:32 ` perf test failures in linux-next on s390 Ian Rogers
2023-06-14 8:31 ` Thomas Richter
2023-06-14 14:57 ` Ian Rogers
2023-06-15 8:57 ` Thomas Richter
2023-06-15 9:39 ` Thomas Richter
2023-06-15 14:34 ` Arnaldo Carvalho de Melo
2023-06-16 14:23 ` Ian Rogers
2023-06-16 14:36 ` Hybrid PMU issues on aarch64. was: " Arnaldo Carvalho de Melo
2023-06-16 14:44 ` Arnaldo Carvalho de Melo
2023-06-16 16:28 ` Ian Rogers
2023-06-16 16:53 ` Arnaldo Carvalho de Melo
2023-06-16 21:47 ` Arnaldo Carvalho de Melo
2023-06-16 22:09 ` Ian Rogers
2023-06-19 10:04 ` 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=d5319870-7569-c353-1777-31ee090f8da8@linux.ibm.com \
--to=tmricht@linux.ibm.com \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).