From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Christian Loehle <christian.loehle@arm.com>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
Doug Smythies <dsmythies@telus.net>,
Aboorva Devarajan <aboorvad@linux.ibm.com>
Subject: [PATCH v1 1/2] cpuidle: teo: Move candidate state lookup to separate function
Date: Thu, 03 Apr 2025 21:16:47 +0200 [thread overview]
Message-ID: <4991828.GXAFRqVoOG@rjwysocki.net> (raw)
In-Reply-To: <4661520.LvFx2qVVIh@rjwysocki.net>
From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Move the code looking up a new candidate idle state in teo, after
deciding that the initial candidate (the deepest enabled idle state) is
likely too deep, into a separate function in preparation for subsequent
changes.
No intentional functional impact.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
---
drivers/cpuidle/governors/teo.c | 120 +++++++++++++++++++++-------------------
1 file changed, 63 insertions(+), 57 deletions(-)
--- a/drivers/cpuidle/governors/teo.c
+++ b/drivers/cpuidle/governors/teo.c
@@ -259,6 +259,67 @@
return state_idx;
}
+static int teo_get_candidate(struct cpuidle_driver *drv,
+ struct cpuidle_device *dev,
+ struct teo_cpu *cpu_data,
+ int idx, unsigned int idx_intercepts)
+{
+ int first_suitable_idx = idx;
+ unsigned int intercepts = 0;
+ int i;
+
+ /*
+ * Look for the deepest idle state whose target residency had
+ * not exceeded the idle duration in over a half of the relevant
+ * cases in the past.
+ *
+ * Take the possible duration limitation present if the tick
+ * has been stopped already into account.
+ */
+ for (i = idx - 1; i >= 0; i--) {
+ intercepts += cpu_data->state_bins[i].intercepts;
+ if (2 * intercepts > idx_intercepts) {
+ /*
+ * Use the current state unless it is too
+ * shallow or disabled, in which case take the
+ * first enabled state that is deep enough.
+ */
+ if (teo_state_ok(i, drv) && !dev->states_usage[i].disable) {
+ idx = i;
+ break;
+ }
+
+ idx = first_suitable_idx;
+ break;
+ }
+
+ if (dev->states_usage[i].disable)
+ continue;
+
+ if (teo_state_ok(i, drv)) {
+ /*
+ * The current state is deep enough, but still
+ * there may be a better one.
+ */
+ first_suitable_idx = i;
+ continue;
+ }
+
+ /*
+ * The current state is too shallow, so if no suitable
+ * states other than the initial candidate have been
+ * found, give up (the remaining states to check are
+ * shallower still), but otherwise the first suitable
+ * state other than the initial candidate may turn out
+ * to be preferable.
+ */
+ if (first_suitable_idx == idx)
+ break;
+ }
+
+ return idx;
+}
+
/**
* teo_select - Selects the next idle state to enter.
* @drv: cpuidle driver containing state data.
@@ -355,63 +416,8 @@
* all of the deeper states, a shallower idle state is likely to be a
* better choice.
*/
- if (2 * idx_intercept_sum > cpu_data->total - idx_hit_sum) {
- int first_suitable_idx = idx;
-
- /*
- * Look for the deepest idle state whose target residency had
- * not exceeded the idle duration in over a half of the relevant
- * cases in the past.
- *
- * Take the possible duration limitation present if the tick
- * has been stopped already into account.
- */
- intercept_sum = 0;
-
- for (i = idx - 1; i >= 0; i--) {
- struct teo_bin *bin = &cpu_data->state_bins[i];
-
- intercept_sum += bin->intercepts;
-
- if (2 * intercept_sum > idx_intercept_sum) {
- /*
- * Use the current state unless it is too
- * shallow or disabled, in which case take the
- * first enabled state that is deep enough.
- */
- if (teo_state_ok(i, drv) &&
- !dev->states_usage[i].disable) {
- idx = i;
- break;
- }
- idx = first_suitable_idx;
- break;
- }
-
- if (dev->states_usage[i].disable)
- continue;
-
- if (teo_state_ok(i, drv)) {
- /*
- * The current state is deep enough, but still
- * there may be a better one.
- */
- first_suitable_idx = i;
- continue;
- }
-
- /*
- * The current state is too shallow, so if no suitable
- * states other than the initial candidate have been
- * found, give up (the remaining states to check are
- * shallower still), but otherwise the first suitable
- * state other than the initial candidate may turn out
- * to be preferable.
- */
- if (first_suitable_idx == idx)
- break;
- }
- }
+ if (2 * idx_intercept_sum > cpu_data->total - idx_hit_sum)
+ idx = teo_get_candidate(drv, dev, cpu_data, idx, idx_intercept_sum);
/*
* If there is a latency constraint, it may be necessary to select an
next prev parent reply other threads:[~2025-04-03 19:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 19:16 [PATCH v1 0/2] cpuidle: teo: Refine handling of short idle intervals Rafael J. Wysocki
2025-04-03 19:16 ` Rafael J. Wysocki [this message]
2025-04-03 19:18 ` [PATCH v1 2/2] " Rafael J. Wysocki
2025-04-16 15:00 ` Christian Loehle
2025-04-16 15:28 ` Rafael J. Wysocki
2025-04-17 11:58 ` Christian Loehle
2025-04-17 15:21 ` Rafael J. Wysocki
2025-04-17 17:18 ` Christian Loehle
2025-04-17 19:05 ` Rafael J. Wysocki
2025-04-09 6:52 ` [PATCH v1 0/2] " Artem Bityutskiy
2025-04-09 12:06 ` Rafael J. Wysocki
2025-04-09 14:36 ` Doug Smythies
2025-04-09 14:41 ` Rafael J. Wysocki
2025-04-14 7:15 ` Aboorva Devarajan
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=4991828.GXAFRqVoOG@rjwysocki.net \
--to=rjw@rjwysocki.net \
--cc=aboorvad@linux.ibm.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=christian.loehle@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=dsmythies@telus.net \
--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