From: "tip-bot2 for Vincent Guittot" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
Ingo Molnar <mingo@kernel.org>, Lukasz Luba <lukasz.luba@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: sched/core] cpufreq/schedutil: Use a fixed reference frequency
Date: Sat, 23 Dec 2023 16:09:54 -0000 [thread overview]
Message-ID: <170334779405.398.10634104096869499211.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20231211104855.558096-4-vincent.guittot@linaro.org>
The following commit has been merged into the sched/core branch of tip:
Commit-ID: b3edde44e5d4504c23a176819865cd603fd16d6c
Gitweb: https://git.kernel.org/tip/b3edde44e5d4504c23a176819865cd603fd16d6c
Author: Vincent Guittot <vincent.guittot@linaro.org>
AuthorDate: Mon, 11 Dec 2023 11:48:51 +01:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Sat, 23 Dec 2023 15:52:35 +01:00
cpufreq/schedutil: Use a fixed reference frequency
cpuinfo.max_freq can change at runtime because of boost as an example. This
implies that the value could be different than the one that has been
used when computing the capacity of a CPU.
The new arch_scale_freq_ref() returns a fixed and coherent reference
frequency that can be used when computing a frequency based on utilization.
Use this arch_scale_freq_ref() when available and fallback to
policy otherwise.
Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Tested-by: Lukasz Luba <lukasz.luba@arm.com>
Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
Acked-by: Rafael J. Wysocki <rafael@kernel.org>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Link: https://lore.kernel.org/r/20231211104855.558096-4-vincent.guittot@linaro.org
---
kernel/sched/cpufreq_schedutil.c | 26 ++++++++++++++++++++++++--
1 file changed, 24 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/cpufreq_schedutil.c b/kernel/sched/cpufreq_schedutil.c
index 4ee8ad7..95c3c09 100644
--- a/kernel/sched/cpufreq_schedutil.c
+++ b/kernel/sched/cpufreq_schedutil.c
@@ -115,6 +115,28 @@ static void sugov_deferred_update(struct sugov_policy *sg_policy)
}
/**
+ * get_capacity_ref_freq - get the reference frequency that has been used to
+ * correlate frequency and compute capacity for a given cpufreq policy. We use
+ * the CPU managing it for the arch_scale_freq_ref() call in the function.
+ * @policy: the cpufreq policy of the CPU in question.
+ *
+ * Return: the reference CPU frequency to compute a capacity.
+ */
+static __always_inline
+unsigned long get_capacity_ref_freq(struct cpufreq_policy *policy)
+{
+ unsigned int freq = arch_scale_freq_ref(policy->cpu);
+
+ if (freq)
+ return freq;
+
+ if (arch_scale_freq_invariant())
+ return policy->cpuinfo.max_freq;
+
+ return policy->cur;
+}
+
+/**
* get_next_freq - Compute a new frequency for a given cpufreq policy.
* @sg_policy: schedutil policy object to compute the new frequency for.
* @util: Current CPU utilization.
@@ -140,9 +162,9 @@ static unsigned int get_next_freq(struct sugov_policy *sg_policy,
unsigned long util, unsigned long max)
{
struct cpufreq_policy *policy = sg_policy->policy;
- unsigned int freq = arch_scale_freq_invariant() ?
- policy->cpuinfo.max_freq : policy->cur;
+ unsigned int freq;
+ freq = get_capacity_ref_freq(policy);
freq = map_util_freq(util, freq, max);
if (freq == sg_policy->cached_raw_freq && !sg_policy->need_freq_update)
next prev parent reply other threads:[~2023-12-23 16:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 10:48 [PATCH v7 0/7] consolidate and cleanup CPU capacity Vincent Guittot
2023-12-11 10:48 ` [PATCH v7 1/7] topology: Add a new arch_scale_freq_reference Vincent Guittot
2023-12-23 16:09 ` [tip: sched/core] sched/topology: Add a new arch_scale_freq_ref() method tip-bot2 for Vincent Guittot
2023-12-11 10:48 ` [PATCH v7 2/7] cpufreq: Use the fixed and coherent frequency for scaling capacity Vincent Guittot
2023-12-23 16:09 ` [tip: sched/core] " tip-bot2 for Vincent Guittot
2023-12-11 10:48 ` [PATCH v7 3/7] cpufreq/schedutil: Use a fixed reference frequency Vincent Guittot
2023-12-23 16:09 ` tip-bot2 for Vincent Guittot [this message]
2024-01-23 1:55 ` Mark Brown
2024-01-23 7:24 ` Vincent Guittot
2024-01-23 15:14 ` Mark Brown
2023-12-11 10:48 ` [PATCH v7 4/7] energy_model: " Vincent Guittot
2023-12-23 16:09 ` [tip: sched/core] " tip-bot2 for Vincent Guittot
2023-12-11 10:48 ` [PATCH v7 5/7] cpufreq/cppc: Move and rename cppc_cpufreq_{perf_to_khz|khz_to_perf} Vincent Guittot
2023-12-23 16:09 ` [tip: sched/core] cpufreq/cppc: Move and rename cppc_cpufreq_{perf_to_khz|khz_to_perf}() tip-bot2 for Vincent Guittot
2023-12-11 10:48 ` [PATCH v7 6/7] cpufreq/cppc: Set the frequency used for computing the capacity Vincent Guittot
2023-12-23 16:09 ` [tip: sched/core] " tip-bot2 for Vincent Guittot
2023-12-11 10:48 ` [PATCH v7 7/7] arm64/amu: Use capacity_ref_freq to set AMU ratio Vincent Guittot
2023-12-23 16:09 ` [tip: sched/core] arm64/amu: Use capacity_ref_freq() " tip-bot2 for Vincent Guittot
2023-12-11 19:52 ` [PATCH v7 0/7] consolidate and cleanup CPU capacity Rafael J. Wysocki
2023-12-12 8:32 ` Vincent Guittot
2023-12-12 11:55 ` Rafael J. Wysocki
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=170334779405.398.10634104096869499211.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mingo@kernel.org \
--cc=rafael@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=x86@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
all inboxes | Powered by JetHome®