From: Hector Martin <marcan@marcan.st>
To: linux-perf-users@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Cc: Marc Zyngier <maz@kernel.org>, Asahi Linux <asahi@lists.linux.dev>
Subject: [REGRESSION] Perf (userspace) broken on big.LITTLE systems since v6.5
Date: Tue, 21 Nov 2023 21:08:48 +0900 [thread overview]
Message-ID: <08f1f185-e259-4014-9ca4-6411d5c1bc65@marcan.st> (raw)
Perf broke on all Apple ARM64 systems (tested almost everything), and
according to maz also on Juno (so, probably all big.LITTLE) since v6.5.
Test command:
sudo taskset -c 0 ./perf stat -e apple_icestorm_pmu/cycles/ -e
apple_firestorm_pmu/cycles/ -e cycles ls
Since this is taskset to CPU #0 (LITTLE core, icestorm), only events for
icestorm are expected.
I bisected the breakage to two distinct points:
5ea8f2ccffb is the first bad commit. With its parent, the output is as
expected (same as v6.4):
3,297,462 apple_icestorm_pmu/cycles/
<not counted> apple_firestorm_pmu/cycles/
(0.00%)
<not counted> cycles
(0.00%)
With 5ea8f2ccffb everything breaks:
<not supported> apple_icestorm_pmu/cycles/
<not supported> apple_firestorm_pmu/cycles/
<not counted> cycles
(0.00%)
Somewhere along the way to 82fe2e45cdb00 things get even worse (didn't
bother bisecting this range). With its parent:
<not supported> apple_icestorm_pmu/cycles/
<not supported> apple_firestorm_pmu/cycles/
<not supported> apple_icestorm_pmu/cycles/
<not supported> apple_firestorm_pmu/cycles/
Then 82fe2e45cdb00 leads to the current v6.5 behavior:
<not counted> apple_icestorm_pmu/cycles/
(0.00%)
<not counted> apple_firestorm_pmu/cycles/
(0.00%)
<not counted> cycles
(0.00%)
If I taskset the task to CPU#2 (big core, firestorm), I get events:
1,454,858 apple_icestorm_pmu/cycles/
1,454,760 apple_firestorm_pmu/cycles/
1,454,384 cycles
So the current behavior is that all output seems to come from the
firestorm PMU event counter, regardless of requested event.
This is all unchanged and still broken in v6.7-rc2.
- Hector
next reply other threads:[~2023-11-21 12:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 12:08 Hector Martin [this message]
2023-11-21 13:40 ` [REGRESSION] Perf (userspace) broken on big.LITTLE systems since v6.5 Marc Zyngier
2023-11-21 15:24 ` Marc Zyngier
2023-11-21 15:40 ` Mark Rutland
2023-11-21 15:46 ` Ian Rogers
2023-11-21 16:02 ` Mark Rutland
2023-11-21 16:09 ` Ian Rogers
2023-11-21 16:15 ` Mark Rutland
2023-11-21 16:38 ` Ian Rogers
2023-11-22 3:23 ` Hector Martin
2023-11-22 13:06 ` Arnaldo Carvalho de Melo
2023-11-22 15:33 ` Ian Rogers
2023-11-22 15:49 ` Mark Rutland
2023-11-22 16:04 ` Ian Rogers
2023-11-22 16:26 ` Arnaldo Carvalho de Melo
2023-11-22 16:33 ` Ian Rogers
2023-11-22 16:19 ` Arnaldo Carvalho de Melo
2023-11-22 13:03 ` Mark Rutland
2023-11-22 15:29 ` Ian Rogers
2023-11-22 16:08 ` Mark Rutland
2023-11-22 16:29 ` Ian Rogers
2023-11-22 16:55 ` Arnaldo Carvalho de Melo
2023-11-22 16:59 ` Ian Rogers
2023-11-23 4:33 ` Ian Rogers
2023-11-21 15:41 ` Ian Rogers
2023-11-21 15:56 ` Mark Rutland
2023-11-21 16:03 ` Ian Rogers
2023-11-21 16:08 ` Mark Rutland
2023-11-23 14:23 ` Mark Rutland
2023-11-23 14:45 ` Marc Zyngier
2023-11-23 15:14 ` Ian Rogers
2023-11-23 16:48 ` Mark Rutland
2023-11-23 17:08 ` James Clark
2023-11-23 17:15 ` Mark Rutland
2023-11-21 23:43 ` Bagas Sanjaya
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=08f1f185-e259-4014-9ca4-6411d5c1bc65@marcan.st \
--to=marcan@marcan.st \
--cc=asahi@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=maz@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 read-only IMAP folder(s) and NNTP newsgroup(s).