[<prev] [next>] [day] [month] [year] [list]
Message-ID: <51cdde9e-f124-8e19-693c-4accc6f2e948@linaro.org>
Date: Thu, 16 Apr 2020 09:40:13 -0400
From: Thara Gopinath <thara.gopinath@...aro.org>
To: Paul Gortmaker <paul.gortmaker@...driver.com>
Cc: Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>, ionela.voinescu@....com,
vincent.guittot@...aro.org, dietmar.eggemann@....com,
rui.zhang@...el.com, qperret@...gle.com, daniel.lezcano@...aro.org,
viresh.kumar@...aro.org, rostedt@...dmis.org, will@...nel.org,
catalin.marinas@....com, sudeep.holla@....com,
juri.lelli@...hat.com, Jonathan Corbet <corbet@....net>,
LKML <linux-kernel@...r.kernel.org>, amit.kachhap@...il.com,
javi.merino@...nel.org, amit.kucheria@...durent.com
Subject: Re: [Patch v10 0/9] Introduce Thermal Pressure
On 4/14/20 11:57 AM, Paul Gortmaker wrote:
> On Fri, Feb 21, 2020 at 7:52 PM Thara Gopinath <thara.gopinath@...aro.org>
> wrote:
>
>> Thermal governors can respond to an overheat event of a cpu by
>> capping the cpu's maximum possible frequency. This in turn
>> means that the maximum available compute capacity of the
>> cpu is restricted. But today in the kernel, task scheduler is
>> not notified of capping of maximum frequency of a cpu.
>> In other words, scheduler is unaware of maximum capacity
>> restrictions placed on a cpu due to thermal activity.
>> This patch series attempts to address this issue.
>>
>
> I'm just seeing this now via -rc1 and "make oldconfig".
>
> I'd suggest taking some of the above info and using it to
> create a Kconfig help text for the new option that was added.
Hi Paul,
I will send a patch adding some details to the Kconfig text.
--
Warm Regards
Thara
Powered by blists - more mailing lists