From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>,
linux@armlinux.org.uk, catalin.marinas@arm.com, will@kernel.org,
sudeep.holla@arm.com, rafael@kernel.org, viresh.kumar@linaro.org,
agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, mingo@redhat.com, peterz@infradead.org,
juri.lelli@redhat.com, rostedt@goodmis.org, bsegall@google.com,
mgorman@suse.de, bristot@redhat.com, vschneid@redhat.com,
lukasz.luba@arm.com, rui.zhang@intel.com, mhiramat@kernel.org,
daniel.lezcano@linaro.org, amit.kachhap@gmail.com,
corbet@lwn.net, gregkh@linuxfoundation.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Cc: qyousef@layalina.io
Subject: Re: [PATCH v3 1/5] cpufreq: Add a cpufreq pressure feedback for the scheduler
Date: Mon, 8 Jan 2024 17:35:08 +0100 [thread overview]
Message-ID: <158a8c60-cb54-43c1-8232-6a0a46cc6d42@arm.com> (raw)
In-Reply-To: <20240108134843.429769-2-vincent.guittot@linaro.org>
On 08/01/2024 14:48, Vincent Guittot wrote:
> Provide to the scheduler a feedback about the temporary max available
> capacity. Unlike arch_update_thermal_pressure, this doesn't need to be
> filtered as the pressure will happen for dozens ms or more.
Is this then related to the 'medium pace system pressure' you mentioned
in your OSPM '23 talk?
>
> Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
> ---
> drivers/cpufreq/cpufreq.c | 36 ++++++++++++++++++++++++++++++++++++
> include/linux/cpufreq.h | 10 ++++++++++
> 2 files changed, 46 insertions(+)
>
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> index 44db4f59c4cc..fa2e2ea26f7f 100644
> --- a/drivers/cpufreq/cpufreq.c
> +++ b/drivers/cpufreq/cpufreq.c
> @@ -2563,6 +2563,40 @@ int cpufreq_get_policy(struct cpufreq_policy *policy, unsigned int cpu)
> }
> EXPORT_SYMBOL(cpufreq_get_policy);
>
> +DEFINE_PER_CPU(unsigned long, cpufreq_pressure);
> +
> +/**
> + * cpufreq_update_pressure() - Update cpufreq pressure for CPUs
> + * @policy: cpufreq policy of the CPUs.
> + *
> + * Update the value of cpufreq pressure for all @cpus in the policy.
> + */
> +static void cpufreq_update_pressure(struct cpufreq_policy *policy)
> +{
> + unsigned long max_capacity, capped_freq, pressure;
> + u32 max_freq;
> + int cpu;
> +
> + /*
> + * Handle properly the boost frequencies, which should simply clean
> + * the thermal pressure value.
^^^^^^^
IMHO, this is a copy & paste error from topology_update_thermal_pressure()?
> + */
> + if (max_freq <= capped_freq) {
max_freq seems to be uninitialized.
> + pressure = 0;
Is this x86 (turbo boost) specific? IMHO at arm we follow this max freq
(including boost) relates to 1024 in capacity? Or haven't we made this
discussion yet?
> + } else {
> + cpu = cpumask_first(policy->related_cpus);
> + max_capacity = arch_scale_cpu_capacity(cpu);
> + capped_freq = policy->max;
> + max_freq = arch_scale_freq_ref(cpu);
> +
> + pressure = max_capacity -
> + mult_frac(max_capacity, capped_freq, max_freq);
> + }
> +
> + for_each_cpu(cpu, policy->related_cpus)
> + WRITE_ONCE(per_cpu(cpufreq_pressure, cpu), pressure);
> +}
> +
[...]
next prev parent reply other threads:[~2024-01-08 16:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 13:48 [PATCH v3 0/5] Rework system pressure interface to the scheduler Vincent Guittot
2024-01-08 13:48 ` [PATCH v3 1/5] cpufreq: Add a cpufreq pressure feedback for " Vincent Guittot
2024-01-08 16:35 ` Dietmar Eggemann [this message]
2024-01-08 16:46 ` Vincent Guittot
2024-01-09 11:24 ` Vincent Guittot
2024-01-08 13:48 ` [PATCH v3 2/5] sched: Take cpufreq feedback into account Vincent Guittot
2024-01-09 11:22 ` Dietmar Eggemann
2024-01-09 14:30 ` Vincent Guittot
2024-01-10 13:51 ` Dietmar Eggemann
2024-01-10 17:25 ` Vincent Guittot
2024-01-08 13:48 ` [PATCH v3 3/5] thermal/cpufreq: Remove arch_update_thermal_pressure() Vincent Guittot
2024-01-08 13:48 ` [PATCH v3 4/5] sched: Rename arch_update_thermal_pressure into arch_update_hw_pressure Vincent Guittot
2024-01-09 11:56 ` Dietmar Eggemann
2024-01-09 13:33 ` Vincent Guittot
2024-01-08 13:48 ` [PATCH v3 5/5] sched/pelt: Remove shift of thermal clock Vincent Guittot
2024-01-09 11:33 ` [PATCH v3 0/5] Rework system pressure interface to the scheduler Dietmar Eggemann
2024-01-09 13:29 ` Vincent Guittot
2024-01-10 18:10 ` Dietmar Eggemann
2024-01-19 17:57 ` Vincent Guittot
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=158a8c60-cb54-43c1-8232-6a0a46cc6d42@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=agross@kernel.org \
--cc=amit.kachhap@gmail.com \
--cc=andersson@kernel.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=daniel.lezcano@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=juri.lelli@redhat.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lukasz.luba@arm.com \
--cc=mgorman@suse.de \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=qyousef@layalina.io \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rui.zhang@intel.com \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=vschneid@redhat.com \
--cc=will@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