From: Lukasz Luba <lukasz.luba@arm.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Yu-Che Cheng <giver@chromium.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Zhang Rui <rui.zhang@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Chen-Yu Tsai <wenst@chromium.org>
Subject: Re: [PATCH] thermal: gov_power_allocator: Update total_weight on bind and cdev updates
Date: Fri, 21 Feb 2025 10:43:00 +0000 [thread overview]
Message-ID: <32fe0e71-e8d9-4404-8b48-a8b8e9ec71e7@arm.com> (raw)
In-Reply-To: <CAJZ5v0h8MyqEgC8Hf1_s4=kCj2W3Y0TWdVnbhwAiVLqED7WPow@mail.gmail.com>
On 2/20/25 19:40, Rafael J. Wysocki wrote:
> On Wed, Feb 19, 2025 at 8:07 AM Yu-Che Cheng <giver@chromium.org> wrote:
>>
>> params->total_weight is not initialized during bind and not updated when
>> the bound cdev changes. The cooling device weight will not be used due
>> to the uninitialized total_weight, until we trigger an update via sysfs.
>>
>> The bound cdev update will be triggered during thermal zone registration,
>> where each cooling device will be bound to the thermal zone one by one.
>>
>> The power_allocator_bind can be called without additional cdev update
>> when manually changing the policy of a thermal zone via sysfs.
Thanks Yu-Che for catching this.
>>
>> Update total_weight when bind and cdev updates to ensure total_weight is
>> correct.
>>
>> Fixes: a3cd6db4cc2e ("thermal: gov_power_allocator: Support new update callback of weights")
>> Signed-off-by: Yu-Che Cheng <giver@chromium.org>
>> ---
>> drivers/thermal/gov_power_allocator.c | 9 +++++----
>> 1 file changed, 5 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/thermal/gov_power_allocator.c b/drivers/thermal/gov_power_allocator.c
>> index 3b644de3292e..600cb0e367c3 100644
>> --- a/drivers/thermal/gov_power_allocator.c
>> +++ b/drivers/thermal/gov_power_allocator.c
>> @@ -656,11 +656,10 @@ static void power_allocator_update_tz(struct thermal_zone_device *tz,
>> if (power_actor_is_valid(instance))
>> num_actors++;
>>
>> - if (num_actors == params->num_actors)
>> - return;
>> + if (num_actors != params->num_actors)
>> + allocate_actors_buffer(params, num_actors);
>>
>> - allocate_actors_buffer(params, num_actors);
>> - break;
>> + fallthrough;
>
> This is basically fine, but I would add a new function, say
> power_allocator_update_weight(), for updating the weight.
>
>> case THERMAL_INSTANCE_WEIGHT_CHANGED:
>
> And I'd call it from here and from power_allocator_bind() below.
>
>> params->total_weight = 0;
>> list_for_each_entry(instance, &td->thermal_instances, trip_node)
>> @@ -731,6 +730,8 @@ static int power_allocator_bind(struct thermal_zone_device *tz)
>>
>> tz->governor_data = params;
>>
>> + power_allocator_update_tz(tz, THERMAL_INSTANCE_WEIGHT_CHANGED);
>
> Because this is kind of confusing (although it will work AFAICS).
>
Thanks Rafael, I agree with suggestions. It would look cleaner.
next prev parent reply other threads:[~2025-02-21 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 7:07 [PATCH] thermal: gov_power_allocator: Update total_weight on bind and cdev updates Yu-Che Cheng
2025-02-20 19:40 ` Rafael J. Wysocki
2025-02-21 10:43 ` Lukasz Luba [this message]
2025-02-21 23:31 ` Yu-Che Cheng
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=32fe0e71-e8d9-4404-8b48-a8b8e9ec71e7@arm.com \
--to=lukasz.luba@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=giver@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=wenst@chromium.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