From: Valentin Schneider <valentin.schneider@arm.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
linux-arm-msm@vger.kernel.org
Cc: agross@kernel.org, bjorn.andersson@linaro.org, rjw@rjwysocki.net,
viresh.kumar@linaro.org,
Ionela Voinescu <ionela.voinescu@arm.com>,
Quentin Perret <qperret@google.com>
Subject: Suspect broken frequency transitions on SDM845
Date: Tue, 4 Feb 2020 13:53:23 +0100 [thread overview]
Message-ID: <eb8c48fb-c9b1-79c1-21b3-cd41ea37e2c6@arm.com> (raw)
Hi folks,
We have a simple sanity test that asserts higher frequency leads to more
work done. It's fairly straightforward - we use the userspace governor,
go through increasing frequencies, run sysbench each time and assert the
values we get are increasing monotonically. We do that for one CPU of each
"type" (i.e. once for a LITTLE and once for a big).
We've been getting some sporadic failures on the big CPUs of a Pixel3
running mainline [1], here is an example of a correct run (CPU4):
| frequency (kHz) | sysbench events |
|-----------------+-----------------|
| 825600 | 236 |
| 1286400 | 369 |
| 1689600 | 483 |
| 2092800 | 600 |
| 2476800 | 711 |
and here is a failed one (still CPU4):
| frequency (kHz) | sysbench events |
|-----------------+-----------------|
| 825600 | 234 |
| 1286400 | 369 |
| 1689600 | 449 |
| 2092800 | 600 |
| 2476800 | 355 |
We've encountered something like this in the past with the exact same
test on h960 [2] but it is much harder to reproduce reliably this time
around.
I haven't found much time to dig into this; I did get a run of ~100
iterations with about ~15 failures, but nothing cpufreq related showed up in
dmesg. I briefly suspected fast-switch, but it's only used by schedutil, so
in this test I would expect the frequency transition to be complete before we
even try to start executing sysbench.
If anyone has the time and will to look into this, that would be much
appreciated.
[1]: https://git.linaro.org/people/amit.pundir/linux.git/log/?h=blueline-mainline-tracking
[2]: https://lore.kernel.org/lkml/d3ede0ab-b635-344c-faba-a9b1531b7f05@arm.com/
Cheers,
Valentin
next reply other threads:[~2020-02-04 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 12:53 Valentin Schneider [this message]
2020-02-12 15:53 ` Suspect broken frequency transitions on SDM845 Valentin Schneider
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=eb8c48fb-c9b1-79c1-21b3-cd41ea37e2c6@arm.com \
--to=valentin.schneider@arm.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=ionela.voinescu@arm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=qperret@google.com \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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).