From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Thomas Richter <tmricht@linux.ibm.com>
Cc: Ian Rogers <irogers@google.com>,
"linux-perf-use." <linux-perf-users@vger.kernel.org>,
Jan Polensky <japo@linux.ibm.com>
Subject: Re: perf stat issue with 7.0.0rc3
Date: Fri, 13 Mar 2026 12:19:11 -0300 [thread overview]
Message-ID: <abQq79_ajs8zFeEI@x1> (raw)
In-Reply-To: <66d0366b-8690-4bde-aba4-1d51f278dfa1@linux.ibm.com>
On Fri, Mar 13, 2026 at 02:13:18PM +0100, Thomas Richter wrote:
> Ian,
>
> I just discovered a strange behavior on linux 7.0.0rc3.
>
> I run these commands on my x86 virtual machine:
>
> bash-5.3# uname -m
> x86_64
> bash-5.3# perf -v
> perf version 6.18.13-200.fc43.x86_64
> bash-5.3# perf stat -- true
>
> Performance counter stats for 'true':
>
> 1.108.929 task-clock # 0,437 CPUs utilized
> 0 context-switches # 0,000 /sec
> 0 cpu-migrations # 0,000 /sec
> 55 page-faults # 49,597 K/sec
> <not supported> cycles
>
> 0,002536439 seconds time elapsed
>
> 0,001363000 seconds user
> 0,001393000 seconds sys
>
> bash-5.3#
>
> This is the epected output, however when I use the perf version 7.0.0rc3:
>
> bash-5.3# ./perf -v
> perf version 7.0.rc3.g1f318b96cc84
> bash-5.3# ./perf stat -- true
> Error:
> No supported events found.
> trace.args_alignment
And this last line is even stranger, in my case I get something else,
also on x86_64:
root@number:~# perf stat -- true
Error:
No supported events found.
addr2line.style
root@number:~#
On an ARM machine:
acme@raspberrypi:~/git/perf-tools $ perf stat -- true
Error:
No supported events found.
acme@raspberrypi:~/git/perf-tools $ uname -a
Linux raspberrypi 6.12.62+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.62-1+rpt1 (2025-12-18) aarch64 GNU/Linux
acme@raspberrypi:~/git/perf-tools $
I'll try to bisect this later, thanks for the report!
- Arnaldo
> bash-5.3#
>
> Same happens on my s390 systems (LPAR and z/VM).
> Is this a known already?
> I guess this is a perf tool issue, same result when you execute this on a 7.0.0rc3
> kernel.
>
> Any ideas where to start debugging
> --
> 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 prev parent reply other threads:[~2026-03-13 15:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 13:13 perf stat issue with 7.0.0rc3 Thomas Richter
2026-03-13 15:13 ` Leo Yan
2026-03-13 15:19 ` Arnaldo Carvalho de Melo [this message]
2026-03-13 15:41 ` Ian Rogers
2026-03-13 15:56 ` Arnaldo Melo
2026-03-13 16:10 ` Ian Rogers
2026-03-13 17:01 ` Arnaldo Melo
2026-03-13 18:27 ` Ian Rogers
2026-03-13 21:10 ` Namhyung Kim
2026-03-17 20:19 ` Arnaldo Carvalho de Melo
2026-03-17 19:39 ` Arnaldo Carvalho de Melo
2026-03-17 19:56 ` Arnaldo Carvalho de Melo
2026-03-17 20:12 ` Arnaldo Carvalho de Melo
2026-03-17 20:50 ` Ian Rogers
2026-03-18 0:37 ` Arnaldo Carvalho de Melo
2026-03-18 2:25 ` Ian Rogers
2026-03-19 1:01 ` [PATCH v1] perf metrics: Make common stalled metrics conditional on having the event Ian Rogers
2026-04-01 5:55 ` Ian Rogers
2026-04-04 0:15 ` Namhyung Kim
2026-03-24 4:19 ` perf stat issue with 7.0.0rc3 Ian Rogers
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=abQq79_ajs8zFeEI@x1 \
--to=acme@kernel.org \
--cc=irogers@google.com \
--cc=japo@linux.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=tmricht@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.