From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Lukasz Luba <lukasz.luba@arm.com>, linux-kernel@vger.kernel.org
Cc: linux-pm@vger.kernel.org, amitk@kernel.org, rui.zhang@intel.com
Subject: Re: [PATCH v3 3/3] thermal: create a helper __thermal_cdev_update() without a lock
Date: Thu, 22 Apr 2021 09:58:43 +0200 [thread overview]
Message-ID: <3d08d5cf-9e3b-ae26-cfd5-bf9a40d11643@linaro.org> (raw)
In-Reply-To: <20210421174145.8213-4-lukasz.luba@arm.com>
On 21/04/2021 19:41, Lukasz Luba wrote:
> There is a need to have a helper function which updates cooling device
> state from the governors code. With this change governor can use
> lock and unlock while calling helper function. This avoid unnecessary
> second time lock/unlock which was in previous solution present in
> governor implementation. This new helper function must be called
> with mutex 'cdev->lock' hold.
>
> The changed been discussed and part of code presented in thread:
> https://lore.kernel.org/linux-pm/20210419084536.25000-1-lukasz.luba@arm.com/
>
> Co-developed-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
> ---
> drivers/thermal/gov_power_allocator.c | 5 +----
> drivers/thermal/thermal_core.h | 1 +
> drivers/thermal/thermal_helpers.c | 28 +++++++++++++++++----------
Why not add this patch first (without the ipa changes) and then replace
patch 2 by using the new function ? That will prevent to go back and forth.
> 3 files changed, 20 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/thermal/gov_power_allocator.c b/drivers/thermal/gov_power_allocator.c
> index f379f1aaa3b5..a6cdb2e892da 100644
> --- a/drivers/thermal/gov_power_allocator.c
> +++ b/drivers/thermal/gov_power_allocator.c
> @@ -595,12 +595,9 @@ static void allow_maximum_power(struct thermal_zone_device *tz, bool update)
> cdev->ops->get_requested_power(cdev, &req_power);
>
> if (update)
> - instance->cdev->updated = false;
> + __thermal_cdev_update(instance->cdev);
>
> mutex_unlock(&instance->cdev->lock);
> -
> - if (update)
> - thermal_cdev_update(instance->cdev);
> }
> mutex_unlock(&tz->lock);
> }
> diff --git a/drivers/thermal/thermal_core.h b/drivers/thermal/thermal_core.h
> index 86b8cef7310e..726e327b4205 100644
> --- a/drivers/thermal/thermal_core.h
> +++ b/drivers/thermal/thermal_core.h
> @@ -66,6 +66,7 @@ static inline bool cdev_is_power_actor(struct thermal_cooling_device *cdev)
> }
>
> void thermal_cdev_update(struct thermal_cooling_device *);
> +void __thermal_cdev_update(struct thermal_cooling_device *cdev);
>
> /**
> * struct thermal_trip - representation of a point in temperature domain
> diff --git a/drivers/thermal/thermal_helpers.c b/drivers/thermal/thermal_helpers.c
> index 7f50f412e02a..3d7fd46104de 100644
> --- a/drivers/thermal/thermal_helpers.c
> +++ b/drivers/thermal/thermal_helpers.c
> @@ -192,18 +192,12 @@ static void thermal_cdev_set_cur_state(struct thermal_cooling_device *cdev,
> thermal_cooling_device_stats_update(cdev, target);
> }
>
> -void thermal_cdev_update(struct thermal_cooling_device *cdev)
> +
> +void __thermal_cdev_update(struct thermal_cooling_device *cdev)
> {
> struct thermal_instance *instance;
> unsigned long target = 0;
>
> - mutex_lock(&cdev->lock);
> - /* cooling device is updated*/
> - if (cdev->updated) {
> - mutex_unlock(&cdev->lock);
> - return;
> - }
> -
> /* Make sure cdev enters the deepest cooling state */
> list_for_each_entry(instance, &cdev->thermal_instances, cdev_node) {
> dev_dbg(&cdev->device, "zone%d->target=%lu\n",
> @@ -216,11 +210,25 @@ void thermal_cdev_update(struct thermal_cooling_device *cdev)
>
> thermal_cdev_set_cur_state(cdev, target);
>
> - cdev->updated = true;
> - mutex_unlock(&cdev->lock);
> trace_cdev_update(cdev, target);
> dev_dbg(&cdev->device, "set to state %lu\n", target);
> }
> +
> +/**
> + * thermal_cdev_update - update cooling device state if needed
> + * @cdev: pointer to struct thermal_cooling_device
> + *
> + * Update the cooling device state if there is a need.
> + */
> +void thermal_cdev_update(struct thermal_cooling_device *cdev)
> +{
> + mutex_lock(&cdev->lock);
> + if (!cdev->updated) {
> + __thermal_cdev_update(cdev);
> + cdev->updated = true;
> + }
> + mutex_unlock(&cdev->lock);
> +}
> EXPORT_SYMBOL(thermal_cdev_update);
>
> /**
>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2021-04-22 7:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 17:41 [PATCH v3 0/3] Improve IPA mechanisms in low temperature state Lukasz Luba
2021-04-21 17:41 ` [PATCH v3 1/3] thermal: power_allocator: maintain the device statistics from going stale Lukasz Luba
2021-04-21 17:41 ` [PATCH v3 2/3] thermal: power_allocator: update once cooling devices when temp is low Lukasz Luba
2021-04-21 17:41 ` [PATCH v3 3/3] thermal: create a helper __thermal_cdev_update() without a lock Lukasz Luba
2021-04-22 7:58 ` Daniel Lezcano [this message]
2021-04-22 8:21 ` Lukasz Luba
2021-04-22 10:26 ` Daniel Lezcano
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=3d08d5cf-9e3b-ae26-cfd5-bf9a40d11643@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=amitk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).