From: Ionela Voinescu <ionela.voinescu@arm.com>
To: Thara Gopinath <thara.gopinath@linaro.org>
Cc: mingo@redhat.com, peterz@infradead.org,
vincent.guittot@linaro.org, rui.zhang@intel.com,
qperret@google.com, daniel.lezcano@linaro.org,
viresh.kumar@linaro.org, linux-kernel@vger.kernel.org,
amit.kachhap@gmail.com, javi.merino@kernel.org,
amit.kucheria@verdurent.com
Subject: Re: [Patch v6 6/7] thermal/cpu-cooling: Update thermal pressure in case of a maximum frequency capping
Date: Mon, 23 Dec 2019 17:54:58 +0000 [thread overview]
Message-ID: <20191223175458.GC31446@arm.com> (raw)
In-Reply-To: <1576123908-12105-7-git-send-email-thara.gopinath@linaro.org>
On Wednesday 11 Dec 2019 at 23:11:47 (-0500), Thara Gopinath wrote:
[...]
> @@ -430,6 +430,10 @@ static int cpufreq_set_cur_state(struct thermal_cooling_device *cdev,
> unsigned long state)
> {
> struct cpufreq_cooling_device *cpufreq_cdev = cdev->devdata;
> + struct cpumask *cpus;
> + unsigned int frequency;
> + unsigned long capacity;
> + int ret;
>
> /* Request state should be less than max_level */
> if (WARN_ON(state > cpufreq_cdev->max_level))
> @@ -441,8 +445,19 @@ static int cpufreq_set_cur_state(struct thermal_cooling_device *cdev,
>
> cpufreq_cdev->cpufreq_state = state;
>
> - return freq_qos_update_request(&cpufreq_cdev->qos_req,
> - get_state_freq(cpufreq_cdev, state));
> + frequency = get_state_freq(cpufreq_cdev, state);
> +
> + ret = freq_qos_update_request(&cpufreq_cdev->qos_req, frequency);
> +
> + if (ret > 0) {
> + cpus = cpufreq_cdev->policy->cpus;
> + capacity = frequency *
> + arch_scale_cpu_capacity(cpumask_first(cpus));
> + capacity /= cpufreq_cdev->policy->cpuinfo.max_freq;
> + arch_set_thermal_pressure(cpus, capacity);
Given that you already get a CPU's capacity (orig) here, why don't
you pass thermal pressure directly to arch_set_thermal_pressure,
rather than passing the capped capacity and subtracting it later from
the same CPU capacity (arch_scale_cpu_capacity)?
If my math is correct this would work nicely:
pressure = cpufreq_cdev->policy->cpuinfo.max_freq;
pressure -= frequency;
pressure *= arch_scale_cpu_capacity(cpumask_first(cpus);
pressure /= cpufreq_cdev->policy->cpuinfo.max_freq;
Thanks,
Ionela.
> + }
> +
> + return ret;
> }
>
> /* Bind cpufreq callbacks to thermal cooling device ops */
> --
> 2.1.4
>
next prev parent reply other threads:[~2019-12-23 17:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 4:11 [Patch v6 0/7] Introduce Thermal Pressure Thara Gopinath
2019-12-12 4:11 ` [Patch v6 1/7] sched/pelt.c: Add support to track thermal pressure Thara Gopinath
2019-12-16 13:43 ` Peter Zijlstra
2019-12-17 12:54 ` Dietmar Eggemann
[not found] ` <CALD-y_xHS7CaZ8SU--VP5+2F5Y8cVb4sw0XuG+JUpP_jxE7yuQ@mail.gmail.com>
2020-01-09 12:24 ` Dietmar Eggemann
2019-12-23 17:56 ` Ionela Voinescu
2020-01-02 14:40 ` Thara Gopinath
2019-12-12 4:11 ` [Patch v6 2/7] sched: Add hook to read per cpu " Thara Gopinath
2019-12-16 14:35 ` Peter Zijlstra
2019-12-17 12:54 ` Dietmar Eggemann
2019-12-12 4:11 ` [Patch v6 3/7] Add infrastructure to store and update instantaneous " Thara Gopinath
2019-12-16 14:37 ` Peter Zijlstra
2019-12-17 12:54 ` Dietmar Eggemann
2019-12-23 17:50 ` Ionela Voinescu
2019-12-12 4:11 ` [Patch v6 4/7] sched/fair: Enable periodic update of average " Thara Gopinath
2019-12-16 14:39 ` Peter Zijlstra
2019-12-16 17:59 ` Quentin Perret
2019-12-17 12:57 ` Dietmar Eggemann
2019-12-27 15:22 ` Thara Gopinath
2019-12-12 4:11 ` [Patch v6 5/7] sched/fair: update cpu_capacity to reflect " Thara Gopinath
2019-12-17 12:54 ` Dietmar Eggemann
2019-12-23 17:52 ` Ionela Voinescu
2019-12-12 4:11 ` [Patch v6 6/7] thermal/cpu-cooling: Update thermal pressure in case of a maximum frequency capping Thara Gopinath
2019-12-23 17:54 ` Ionela Voinescu [this message]
2019-12-12 4:11 ` [Patch v6 7/7] sched/fair: Enable tuning of decay period Thara Gopinath
2019-12-23 17:55 ` Ionela Voinescu
2019-12-16 14:56 ` [Patch v6 0/7] Introduce Thermal Pressure Peter Zijlstra
2020-01-11 15:04 ` Thara Gopinath
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=20191223175458.GC31446@arm.com \
--to=ionela.voinescu@arm.com \
--cc=amit.kachhap@gmail.com \
--cc=amit.kucheria@verdurent.com \
--cc=daniel.lezcano@linaro.org \
--cc=javi.merino@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=qperret@google.com \
--cc=rui.zhang@intel.com \
--cc=thara.gopinath@linaro.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).