From: Lukasz Luba <lukasz.luba@arm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: catalin.marinas@arm.com, will@kernel.org,
linux-trace-kernel@vger.kernel.org, amit.kachhap@gmail.com,
daniel.lezcano@linaro.org, mhiramat@kernel.org,
vschneid@redhat.com, bristot@redhat.com, mgorman@suse.de,
bsegall@google.com, juri.lelli@redhat.com, peterz@infradead.org,
mingo@redhat.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, konrad.dybcio@linaro.org,
andersson@kernel.org, agross@kernel.org, rui.zhang@intel.com,
viresh.kumar@linaro.org, rafael@kernel.org, sudeep.holla@arm.com,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 0/5] Rework system pressure interface to the scheduler
Date: Fri, 15 Dec 2023 15:54:13 +0000 [thread overview]
Message-ID: <2b0524b9-3b54-4548-9054-2ba48eed6b65@arm.com> (raw)
In-Reply-To: <2c2fad2b-89ce-437e-96b3-f06e6f99639f@arm.com>
On 12/14/23 08:32, Lukasz Luba wrote:
>
>
> On 12/14/23 08:29, Vincent Guittot wrote:
>> On Thu, 14 Dec 2023 at 09:21, Lukasz Luba <lukasz.luba@arm.com> wrote:
>>>
>>> Hi Vincent,
>>>
>>> I've been waiting for this feature, thanks!
>>>
>>>
>>> On 12/12/23 14:27, Vincent Guittot wrote:
>>>> Following the consolidation and cleanup of CPU capacity in [1], this
>>>> serie
>>>> reworks how the scheduler gets the pressures on CPUs. We need to
>>>> take into
>>>> account all pressures applied by cpufreq on the compute capacity of
>>>> a CPU
>>>> for dozens of ms or more and not only cpufreq cooling device or HW
>>>> mitigiations. we split the pressure applied on CPU's capacity in 2
>>>> parts:
>>>> - one from cpufreq and freq_qos
>>>> - one from HW high freq mitigiation.
>>>>
>>>> The next step will be to add a dedicated interface for long standing
>>>> capping of the CPU capacity (i.e. for seconds or more) like the
>>>> scaling_max_freq of cpufreq sysfs. The latter is already taken into
>>>> account by this serie but as a temporary pressure which is not
>>>> always the
>>>> best choice when we know that it will happen for seconds or more.
>>>>
>>>> [1]
>>>> https://lore.kernel.org/lkml/20231211104855.558096-1-vincent.guittot@linaro.org/
>>>>
>>>> Vincent Guittot (4):
>>>> cpufreq: Add a cpufreq pressure feedback for the scheduler
>>>> sched: Take cpufreq feedback into account
>>>> thermal/cpufreq: Remove arch_update_thermal_pressure()
>>>> sched: Rename arch_update_thermal_pressure into
>>>> arch_update_hw_pressure
>>>>
>>>> arch/arm/include/asm/topology.h | 6 +--
>>>> arch/arm64/include/asm/topology.h | 6 +--
>>>> drivers/base/arch_topology.c | 26 ++++-----
>>>> drivers/cpufreq/cpufreq.c | 48 +++++++++++++++++
>>>> drivers/cpufreq/qcom-cpufreq-hw.c | 4 +-
>>>> drivers/thermal/cpufreq_cooling.c | 3 --
>>>> include/linux/arch_topology.h | 8 +--
>>>> include/linux/cpufreq.h | 10 ++++
>>>> include/linux/sched/topology.h | 8 +--
>>>> .../{thermal_pressure.h => hw_pressure.h} | 14 ++---
>>>> include/trace/events/sched.h | 2 +-
>>>> init/Kconfig | 12 ++---
>>>> kernel/sched/core.c | 8 +--
>>>> kernel/sched/fair.c | 53
>>>> ++++++++++---------
>>>> kernel/sched/pelt.c | 18 +++----
>>>> kernel/sched/pelt.h | 16 +++---
>>>> kernel/sched/sched.h | 4 +-
>>>> 17 files changed, 152 insertions(+), 94 deletions(-)
>>>> rename include/trace/events/{thermal_pressure.h => hw_pressure.h}
>>>> (55%)
>>>>
>>>
>>> I would like to test it, but something worries me. Why there is 0/5 in
>>> this subject and only 4 patches?
>>
>> I removed a patch from the series but copied/pasted the cover letter
>> subject without noticing the /5 instead of /4
>
> OK
>
>>
>>>
>>> Could you tell me your base branch that I can apply this, please?
>>
>> It applies on top of tip/sched/core + [1]
>> and you can find it here:
>> https://git.linaro.org/people/vincent.guittot/kernel.git/log/?h=sched/system-pressure
>
> Thanks for the info and handy link.
>
I've tested your patches with: DTPM/PowerCap + thermal gov + cpufreq
sysfs scaling_max_freq. It works fine all my cases (couldn't cause
any issues). If you like to test DTPM you will need 2 fixed pending
in Rafael's tree.
So, I'm looking for a your v2 to continue reviewing it.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-12-15 15:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 14:27 [PATCH 0/5] Rework system pressure interface to the scheduler Vincent Guittot
2023-12-12 14:27 ` [PATCH 1/4] cpufreq: Add a cpufreq pressure feedback for " Vincent Guittot
2023-12-13 7:17 ` Viresh Kumar
2023-12-13 8:05 ` Vincent Guittot
2023-12-14 0:41 ` Tim Chen
2023-12-14 5:36 ` Viresh Kumar
2023-12-14 5:43 ` Viresh Kumar
2023-12-14 7:57 ` Vincent Guittot
2023-12-14 9:08 ` Lukasz Luba
2023-12-14 9:40 ` Rafael J. Wysocki
2023-12-14 10:41 ` Lukasz Luba
2023-12-14 9:21 ` Lukasz Luba
2023-12-14 11:06 ` Vincent Guittot
2023-12-12 14:27 ` [PATCH 2/4] sched: Take cpufreq feedback into account Vincent Guittot
2023-12-15 16:03 ` Lukasz Luba
2023-12-12 14:27 ` [PATCH 3/4] thermal/cpufreq: Remove arch_update_thermal_pressure() Vincent Guittot
2023-12-15 15:38 ` Lukasz Luba
2023-12-12 14:27 ` [PATCH 4/4] sched: Rename arch_update_thermal_pressure into arch_update_hw_pressure Vincent Guittot
2023-12-14 8:31 ` Lukasz Luba
2023-12-14 8:36 ` Vincent Guittot
2023-12-14 8:54 ` Lukasz Luba
2023-12-14 8:54 ` Vincent Guittot
2023-12-14 8:22 ` [PATCH 0/5] Rework system pressure interface to the scheduler Lukasz Luba
2023-12-14 8:29 ` Vincent Guittot
2023-12-14 8:32 ` Lukasz Luba
2023-12-15 15:54 ` Lukasz Luba [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=2b0524b9-3b54-4548-9054-2ba48eed6b65@arm.com \
--to=lukasz.luba@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=daniel.lezcano@linaro.org \
--cc=dietmar.eggemann@arm.com \
--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-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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