mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: sched/core] cpufreq: Use the fixed and coherent frequency for scaling capacity
Date: Sat, 23 Dec 2023 16:09:54 -0000	[thread overview]
Message-ID: <170334779477.398.11717943380884738392.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20231211104855.558096-3-vincent.guittot@linaro.org>

The following commit has been merged into the sched/core branch of tip:

Commit-ID:     599457ba15403037b489fe536266a3d5f9efaed7
Gitweb:        https://git.kernel.org/tip/599457ba15403037b489fe536266a3d5f9efaed7
Author:        Vincent Guittot <vincent.guittot@linaro.org>
AuthorDate:    Mon, 11 Dec 2023 11:48:50 +01:00
Committer:     Ingo Molnar <mingo@kernel.org>
CommitterDate: Sat, 23 Dec 2023 15:52:34 +01:00

cpufreq: Use the fixed and coherent frequency for scaling capacity

cpuinfo.max_freq can change at runtime because of boost as an example. This
implies that the value could be different from the frequency that has been
used to compute the capacity of a CPU.

The new arch_scale_freq_ref() returns a fixed and coherent frequency
that can be used to compute the capacity for a given frequency.

[ Also fix a arch_set_freq_scale()  newline style wart in <linux/cpufreq.h>. ]

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>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Acked-by: Rafael J. Wysocki <rafael@kernel.org>
Link: https://lore.kernel.org/r/20231211104855.558096-3-vincent.guittot@linaro.org
---
 drivers/cpufreq/cpufreq.c | 4 ++--
 include/linux/cpufreq.h   | 1 +
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 934d35f..44db4f5 100644
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
@@ -454,7 +454,7 @@ void cpufreq_freq_transition_end(struct cpufreq_policy *policy,
 
 	arch_set_freq_scale(policy->related_cpus,
 			    policy->cur,
-			    policy->cpuinfo.max_freq);
+			    arch_scale_freq_ref(policy->cpu));
 
 	spin_lock(&policy->transition_lock);
 	policy->transition_ongoing = false;
@@ -2174,7 +2174,7 @@ unsigned int cpufreq_driver_fast_switch(struct cpufreq_policy *policy,
 
 	policy->cur = freq;
 	arch_set_freq_scale(policy->related_cpus, freq,
-			    policy->cpuinfo.max_freq);
+			    arch_scale_freq_ref(policy->cpu));
 	cpufreq_stats_record_transition(policy, freq);
 
 	if (trace_cpu_frequency_enabled()) {
diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
index 1c5ca92..afda5f2 100644
--- a/include/linux/cpufreq.h
+++ b/include/linux/cpufreq.h
@@ -1203,6 +1203,7 @@ void arch_set_freq_scale(const struct cpumask *cpus,
 {
 }
 #endif
+
 /* the following are really really optional */
 extern struct freq_attr cpufreq_freq_attr_scaling_available_freqs;
 extern struct freq_attr cpufreq_freq_attr_scaling_boost_freqs;

  reply	other threads:[~2023-12-23 16:10 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-bot2 for Vincent Guittot [this message]
2023-12-11 10:48 ` [PATCH v7 3/7] cpufreq/schedutil: Use a fixed reference frequency Vincent Guittot
2023-12-23 16:09   ` [tip: sched/core] " tip-bot2 for Vincent Guittot
2024-01-23  1:55   ` [PATCH v7 3/7] " 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=170334779477.398.11717943380884738392.tip-bot2@tip-bot2 \
    --to=tip-bot2@linutronix.de \
    --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®