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, rui.zhang@intel.com
Subject: Re: [PATCH v2 2/2] thermal: power_allocator: update once cooling devices when temp is low
Date: Tue, 20 Apr 2021 15:21:16 +0100 [thread overview]
Message-ID: <55943d6f-0f72-215d-1dd4-bf3996092df7@arm.com> (raw)
In-Reply-To: <c69e2ba0-b382-01a0-292f-019fffd365e0@linaro.org>
Hi Daniel,
On 4/20/21 2:30 PM, Daniel Lezcano wrote:
> On 19/04/2021 10:45, Lukasz Luba wrote:
[snip]
>> - instance->cdev->updated = false;
>> + if (update)
>> + instance->cdev->updated = false;
>> +
>> mutex_unlock(&instance->cdev->lock);
>> - (instance->cdev);
>> +
>> + if (update)
>> + thermal_cdev_update(instance->cdev);
>
> This cdev update has something bad IMHO. It is protected by a mutex but
> the 'updated' field is left unprotected before calling
> thermal_cdev_update().
>
> It is not the fault of this code but how the cooling device are updated
> and how it interacts with the thermal instances.
>
> IMO, part of the core code needs to revisited.
I agree, but please check my comments below.
>
> This change tight a bit more the knot.
>
> Would it make sense to you if we create a function eg.
> __thermal_cdev_update()
I'm not sure if I assume it right that the function would only have the:
list_for_each_entry(instance, &cdev->thermal_instances, cdev_node)
loop from the thermal_cdev_update(). But if it has only this loop then
it's too little.
>
> And then we have:
>
> void thermal_cdev_update(struct thermal_cooling_device *cdev)
> {
> mutex_lock(&cdev->lock);
> /* cooling device is updated*/
> if (cdev->updated) {
> mutex_unlock(&cdev->lock);
> return;
> }
>
> __thermal_cdev_update(cdev);
>
> thermal_cdev_set_cur_state(cdev, target);
Here we are actually setting the 'target' state via:
cdev->ops->set_cur_state(cdev, target)
then we notify, then updating stats.
>
> cdev->updated = true;
> mutex_unlock(&cdev->lock);
> trace_cdev_update(cdev, target);
Also this trace is something that I'm using in my tests...
> dev_dbg(&cdev->device, "set to state %lu\n", target);
> }
>
> And in this file we do instead:
>
> - instance->cdev->updated = false;
> + if (update)
> + __thermal_cdev_update(instance->cdev);
> mutex_unlock(&instance->cdev->lock);
> - thermal_cdev_update(instance->cdev);
Without the line above, we are not un-throttling the devices.
Regards,
Lukasz
next prev parent reply other threads:[~2021-04-20 14:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 8:45 [PATCH v2 0/2] Improve IPA mechanisms in low temperature state Lukasz Luba
2021-04-19 8:45 ` [PATCH v2 1/2] thermal: power_allocator: maintain the device statistics from going stale Lukasz Luba
2021-04-19 8:45 ` [PATCH v2 2/2] thermal: power_allocator: update once cooling devices when temp is low Lukasz Luba
2021-04-20 13:30 ` Daniel Lezcano
2021-04-20 14:21 ` Lukasz Luba [this message]
2021-04-20 15:24 ` Daniel Lezcano
2021-04-20 20:01 ` Lukasz Luba
2021-04-20 21:03 ` Daniel Lezcano
2021-04-21 8:46 ` 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=55943d6f-0f72-215d-1dd4-bf3996092df7@arm.com \
--to=lukasz.luba@arm.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
/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®