From: Lukasz Luba <lukasz.luba@arm.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
amitk@kernel.org, Dietmar.Eggemann@arm.com,
ionela.voinescu@arm.com
Subject: Re: [PATCH v4 0/3] Improve the estimations in Intelligent Power Allocation
Date: Thu, 26 Nov 2020 14:02:41 +0000 [thread overview]
Message-ID: <ef6bcc10-7034-0ac1-b832-938393682d2f@arm.com> (raw)
In-Reply-To: <f9899f7b-0bc9-40e2-4969-eb76bd11ed5b@linaro.org>
On 11/26/20 1:09 PM, Daniel Lezcano wrote:
> On 26/11/2020 13:49, Lukasz Luba wrote:
>> Hi Daniel,
>>
>> On 11/24/20 4:10 PM, Lukasz Luba wrote:
>>> Hi all,
>>>
>>> The Intelligent Power Allocation (IPA) estimates the needed
>>> coefficients for
>>> internal algorithm. It can also estimate the sustainable power value
>>> when the
>>> DT has not provided one. Fix the 'k_i' coefficient which might be to big
>>> related to the other values, when the sustainable power is in an abstract
>>> scale. Do the estimation of sustainable power only once and avoid
>>> expensive
>>> calculation every time the IPA is called. Do the estimation of PID
>>> constants
>>> when there was user update via sysfs to sustainable power.
>>>
>>> The patch set should apply on top next-20201124
>>>
>>> Changes:
>>> v4:
>>> - added new function get_sustainable_power() which handles use cases
>>> when the value should be estimated again or simply returned
>>> - added sustainable_power in the power_allocator_params to track if there
>>> was a change to sustainable_power by the user via sysfs
>>> - addressed Daniel's comments that sustainable power set via sysfs should
>>> trigger PID coefficients estimation
>>> - removed 'force' argument from estimate_pid_constants() and make it
>>> ready
>>> for updates due to new value for sust. power from sysfs
>>> - abandoned the design from v3 with a single function responsible for
>>> estimation both sust. power and PID const. requested by Ionela
>>> v3 [1]:
>>> - changed estimate_pid_constants to estimate_tzp_constants and related
>>> comments
>>> - estimate the PID coefficients always together with sust. power
>>> - added print indicating that we are estimating sust. power and PID
>>> const.
>>> - don't use local variable 'sustainable_power'
>>>
>>> Regards,
>>> Lukasz Luba
>>>
>>> [1]
>>> https://lore.kernel.org/lkml/20201009135850.14727-1-lukasz.luba@arm.com/
>>>
>>> Lukasz Luba (3):
>>> thermal: power allocator: change the 'k_i' coefficient estimation
>>> thermal: power allocator: refactor sustainable power estimation
>>> thermal: power allocator: change the 'k_*' always in
>>> estimate_pid_constants()
>>>
>>> drivers/thermal/gov_power_allocator.c | 76 +++++++++++++++++----------
>>> 1 file changed, 49 insertions(+), 27 deletions(-)
>>>
>>
>> Gentle ping. This is a self contained change to only power allocator
>> file. It addresses also your requirement regarding sustainable_power
>> changed via sysfs.
>>
>> Could you take it please? It should apply smoothly in your tree.
>
> Actually, I'm waiting for Ionela and Dietmar ack.
>
>
Are they maintainers of this file that you need their ACKs?
Maybe I should drop mine then.
next prev parent reply other threads:[~2020-11-26 14:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 16:10 Lukasz Luba
2020-11-24 16:10 ` [PATCH v4 1/3] thermal: power allocator: change the 'k_i' coefficient estimation Lukasz Luba
2020-11-26 16:00 ` Ionela Voinescu
2020-11-24 16:10 ` [PATCH v4 2/3] thermal: power allocator: refactor sustainable power estimation Lukasz Luba
2020-11-26 15:59 ` Ionela Voinescu
2020-11-26 16:26 ` Lukasz Luba
2020-11-24 16:10 ` [PATCH v4 3/3] thermal: power allocator: change the 'k_*' always in estimate_pid_constants() Lukasz Luba
2020-11-26 16:00 ` Ionela Voinescu
2020-11-26 12:49 ` [PATCH v4 0/3] Improve the estimations in Intelligent Power Allocation Lukasz Luba
2020-11-26 13:09 ` Daniel Lezcano
2020-11-26 14:02 ` Lukasz Luba [this message]
2020-11-26 14:30 ` Daniel Lezcano
2020-11-26 14:45 ` Lukasz Luba
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=ef6bcc10-7034-0ac1-b832-938393682d2f@arm.com \
--to=lukasz.luba@arm.com \
--cc=Dietmar.Eggemann@arm.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=ionela.voinescu@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.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®