From: Lukasz Luba <lukasz.luba@arm.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Zhang Rui <rui.zhang@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: Re: [PATCH v1 03/10] thermal: core: Prepare for moving trips between sorted lists
Date: Thu, 24 Oct 2024 11:19:24 +0100 [thread overview]
Message-ID: <9e84763a-5dd2-43c6-88fd-06433e2749cb@arm.com> (raw)
In-Reply-To: <2960197.e9J7NaK4W3@rjwysocki.net>
On 10/16/24 12:24, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> Subsequently, trips will be moved between sorted lists in multiple
> places, so replace add_trip_to_sorted_list() with an analogous
> function, move_trip_to_sorted_list(), that will move a given trip
> to a given sorted list.
>
> To allow list_del() used in the new function to work, initialize the
> list_node fields in trip descriptors where applicable so they are
> always valid.
>
> No intentional functional impact.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
> drivers/thermal/thermal_core.c | 25 ++++++++++++++++++-------
> 1 file changed, 18 insertions(+), 7 deletions(-)
>
> Index: linux-pm/drivers/thermal/thermal_core.c
> ===================================================================
> --- linux-pm.orig/drivers/thermal/thermal_core.c
> +++ linux-pm/drivers/thermal/thermal_core.c
> @@ -408,11 +408,17 @@ static void handle_critical_trips(struct
> tz->ops.hot(tz);
> }
>
> -static void add_trip_to_sorted_list(struct thermal_trip_desc *td,
> - struct list_head *list)
> +static void move_trip_to_sorted_list(struct thermal_trip_desc *td,
> + struct list_head *list)
> {
> struct thermal_trip_desc *entry;
>
> + /*
> + * Delete upfront and then add to make relocation within the same list
> + * work.
> + */
> + list_del(&td->list_node);
> +
> /* Assume that the new entry is likely to be the last one. */
> list_for_each_entry_reverse(entry, list, list_node) {
> if (entry->notify_temp <= td->notify_temp) {
> @@ -453,7 +459,7 @@ static void handle_thermal_trip(struct t
> */
> if (tz->temperature < trip->temperature - trip->hysteresis) {
> td->notify_temp = trip->temperature - trip->hysteresis;
> - add_trip_to_sorted_list(td, way_down_list);
> + move_trip_to_sorted_list(td, way_down_list);
>
> if (trip->type == THERMAL_TRIP_PASSIVE) {
> tz->passive--;
> @@ -469,7 +475,7 @@ static void handle_thermal_trip(struct t
> * threshold is then set to the low temperature of the trip.
> */
> td->notify_temp = trip->temperature;
> - add_trip_to_sorted_list(td, way_up_list);
> + move_trip_to_sorted_list(td, way_up_list);
>
> td->threshold -= trip->hysteresis;
>
> @@ -538,7 +544,7 @@ void __thermal_zone_device_update(struct
> enum thermal_notify_event event)
> {
> struct thermal_governor *governor = thermal_get_tz_governor(tz);
> - struct thermal_trip_desc *td;
> + struct thermal_trip_desc *td, *next;
> LIST_HEAD(way_down_list);
> LIST_HEAD(way_up_list);
> int low = -INT_MAX, high = INT_MAX;
> @@ -586,11 +592,15 @@ void __thermal_zone_device_update(struct
>
> thermal_zone_set_trips(tz, low, high);
>
> - list_for_each_entry(td, &way_up_list, list_node)
> + list_for_each_entry_safe(td, next, &way_up_list, list_node) {
> thermal_trip_crossed(tz, &td->trip, governor, true);
> + list_del_init(&td->list_node);
> + }
>
> - list_for_each_entry_reverse(td, &way_down_list, list_node)
> + list_for_each_entry_safe_reverse(td, next, &way_down_list, list_node) {
> thermal_trip_crossed(tz, &td->trip, governor, false);
> + list_del_init(&td->list_node);
> + }
>
> if (governor->manage)
> governor->manage(tz);
> @@ -1490,6 +1500,7 @@ thermal_zone_device_register_with_trips(
> for_each_trip_desc(tz, td) {
> td->trip = *trip++;
> INIT_LIST_HEAD(&td->thermal_instances);
> + INIT_LIST_HEAD(&td->list_node);
> /*
> * Mark all thresholds as invalid to start with even though
> * this only matters for the trips that start as invalid and
>
>
>
Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
next prev parent reply other threads:[~2024-10-24 10:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 11:18 [PATCH v1 00/10] thermal: core: Use lists of trips for trip crossing detection and handling Rafael J. Wysocki
2024-10-16 11:21 ` [PATCH v1 01/10] thermal: core: Build sorted lists instead of sorting them later Rafael J. Wysocki
2024-10-24 10:14 ` Lukasz Luba
2024-10-16 11:23 ` [PATCH v1 02/10] thermal: core: Rename trip list node in struct thermal_trip_desc Rafael J. Wysocki
2024-10-24 10:16 ` Lukasz Luba
2024-10-16 11:24 ` [PATCH v1 03/10] thermal: core: Prepare for moving trips between sorted lists Rafael J. Wysocki
2024-10-24 10:19 ` Lukasz Luba [this message]
2024-10-16 11:26 ` [PATCH v1 04/10] thermal: core: Rearrange __thermal_zone_device_update() Rafael J. Wysocki
2024-10-24 10:20 ` Lukasz Luba
2024-10-16 11:27 ` [PATCH v1 05/10] thermal: core: Pass trip descriptor to thermal_trip_crossed() Rafael J. Wysocki
2024-10-24 10:22 ` Lukasz Luba
2024-10-16 11:29 ` [PATCH v1 06/10] thermal: core: Move some trip processing " Rafael J. Wysocki
2024-10-24 10:24 ` Lukasz Luba
2024-10-16 11:32 ` [PATCH v1 07/10] thermal: core: Relocate functions that update trip points Rafael J. Wysocki
2024-10-24 10:25 ` Lukasz Luba
2024-10-16 11:33 ` [PATCH v1 08/10] thermal: core: Eliminate thermal_zone_trip_down() Rafael J. Wysocki
2024-10-24 10:33 ` Lukasz Luba
2024-10-24 12:33 ` Rafael J. Wysocki
2024-10-24 13:39 ` Lukasz Luba
2024-10-16 11:35 ` [PATCH v1 09/10] thermal: core: Use trip lists for trip crossing detection Rafael J. Wysocki
2024-10-24 11:48 ` Lukasz Luba
2024-10-24 12:22 ` Rafael J. Wysocki
2024-10-16 11:36 ` [PATCH v1 10/10] thermal: core: Relocate thermal zone initialization routine Rafael J. Wysocki
2024-10-24 10:35 ` Lukasz Luba
2024-10-21 11:16 ` [PATCH v1 00/10] thermal: core: Use lists of trips for trip crossing detection and handling Rafael J. Wysocki
2024-10-22 22:52 ` Lukasz Luba
2024-10-23 8:53 ` Rafael J. Wysocki
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=9e84763a-5dd2-43c6-88fd-06433e2749cb@arm.com \
--to=lukasz.luba@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@linux.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®