From: Russell Haley <yumpusamongus@gmail.com>
To: lukasz.luba@arm.com
Cc: dietmar.eggemann@arm.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, rafael@kernel.org,
vincent.guittot@linaro.org, viresh.kumar@linaro.org
Subject: Re: [PATCH v2] cpufreq: schedutil: Move max CPU capacity to sugov_policy
Date: Mon, 3 Oct 2022 03:41:34 -0500 [thread overview]
Message-ID: <b2d905b2-5664-442b-bc12-fd759ac9fa9f@gmail.com> (raw)
In-Reply-To: <20220816130629.3178-1-lukasz.luba@arm.com>
>We can do that since all CPUs in the same frequency domain have the
>same max capacity
Do they? In the Intel Alder Lake datasheet [1], it says that a single
power rail supplies all IA ("Intel Architecture") cores, which includes
both P cores and E cores.
I don't have anything that new, but on Haswell and Skylake, despite the
fact that each CPU has a separate policy that lists only itself in
affected_cpus, with the userspace governor I find that every core runs
at the the highest frequency set among all cores. For clarity:
$ grep . cpufreq/policy*/scaling_{setspeed,cur_freq}
cpufreq/policy0/scaling_setspeed:3000000
cpufreq/policy1/scaling_setspeed:2000000
cpufreq/policy0/scaling_cur_freq:2999997
cpufreq/policy1/scaling_cur_freq:3000001
It seems that these cores are in the same frequency domain, even if
cpufreq doesn't know about it. I don't know if this affects the behavior
of the governors in any way, but it might be a bug in intel_pstate that
could one day be fixed. If it is, then any heterogeneous-uarch chips
with both CPU types sharing a voltage rail would have CPUs with
different max capacity in the same frequency domain.
This might present a problem for any future attempt to harmonize
treatment of big.LITTLE between ARM and x86.
[1]:
https://edc.intel.com/content/www/us/en/design/ipla/software-development-platforms/client/platforms/alder-lake-desktop/12th-generation-intel-core-processors-datasheet-volume-1-of-2/processor-power-rails_1/
prev parent reply other threads:[~2022-10-03 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 13:06 [PATCH v2] cpufreq: schedutil: Move max CPU capacity to sugov_policy Lukasz Luba
2022-08-23 18:04 ` Rafael J. Wysocki
2022-10-03 8:41 ` Russell Haley [this message]
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=b2d905b2-5664-442b-bc12-fd759ac9fa9f@gmail.com \
--to=yumpusamongus@gmail.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=vincent.guittot@linaro.org \
--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).