Linux Power Management development
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Christian Loehle <christian.loehle@arm.com>,
	Doug Smythies <dsmythies@telus.net>
Subject: [PATCH v1 1/5] cpuidle: governors: teo: Avoid selecting states with zero-size bins
Date: Wed, 14 Jan 2026 20:44:04 +0100	[thread overview]
Message-ID: <3033265.e9J7NaK4W3@rafael.j.wysocki> (raw)
In-Reply-To: <2257365.irdbgypaU6@rafael.j.wysocki>

From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

If the last two enabled idle states have the same target residency which
is at least equal to TICK_NSET, teo may select the next-to-last one even
though the size of that state's bin is 0, which is confusing.

Prevent that from happening by adding a target residency check to the
relevant code path.

Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
---
 drivers/cpuidle/governors/teo.c |   10 ++++++++++
 1 file changed, 10 insertions(+)

--- a/drivers/cpuidle/governors/teo.c
+++ b/drivers/cpuidle/governors/teo.c
@@ -388,6 +388,15 @@ static int teo_select(struct cpuidle_dri
 			while (min_idx < idx &&
 			       drv->states[min_idx].target_residency_ns < TICK_NSEC)
 				min_idx++;
+
+			/*
+			 * Avoid selecting a state with a lower index, but with
+			 * the same target residency as the current candidate
+			 * one.
+			 */
+			if (drv->states[min_idx].target_residency_ns ==
+					drv->states[idx].target_residency_ns)
+				goto constraint;
 		}
 
 		/*
@@ -410,6 +419,7 @@ static int teo_select(struct cpuidle_dri
 		}
 	}
 
+constraint:
 	/*
 	 * If there is a latency constraint, it may be necessary to select an
 	 * idle state shallower than the current candidate one.




  reply	other threads:[~2026-01-14 19:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14 19:42 [PATCH v1 0/5] cpuidle: governors: teo: Wakeup events classification change and some refinements Rafael J. Wysocki
2026-01-14 19:44 ` Rafael J. Wysocki [this message]
2026-01-21 13:09   ` [PATCH v1 1/5] cpuidle: governors: teo: Avoid selecting states with zero-size bins Christian Loehle
2026-01-23 20:46     ` Rafael J. Wysocki
2026-01-26  9:18       ` Christian Loehle
2026-01-26 11:40         ` Rafael J. Wysocki
2026-01-26 12:05           ` Christian Loehle
2026-01-14 19:44 ` [PATCH v1 2/5] cpuidle: governors: teo: Avoid fake intercepts produced by tick Rafael J. Wysocki
2026-01-21 13:34   ` Christian Loehle
2026-01-14 19:45 ` [PATCH v1 3/5] cpuidle: governors: teo: Refine tick_intercepts vs total events check Rafael J. Wysocki
2026-01-21 13:36   ` Christian Loehle
2026-01-14 19:46 ` [PATCH v1 4/5] cpuidle: governors: teo: Adjust the classification of wakeup events Rafael J. Wysocki
2026-01-14 19:47 ` [PATCH v1 5/5] cpuidle: governors: teo: Refine intercepts-based idle state lookup Rafael J. Wysocki
2026-01-16 11:52 ` [PATCH v1 0/5] cpuidle: governors: teo: Wakeup events classification change and some refinements Christian Loehle
2026-01-16 12:29   ` Rafael J. Wysocki
2026-01-19  9:53     ` Christian Loehle
2026-01-19 12:09       ` Rafael J. Wysocki
2026-01-19 16:20         ` Doug Smythies
2026-01-20 15:29 ` [Update][PATCH v1.1 4/5] cpuidle: governors: teo: Adjust the classification of wakeup events Rafael J. Wysocki
2026-01-25 17:21   ` Doug Smythies
2026-01-25 19:38     ` Christian Loehle

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=3033265.e9J7NaK4W3@rafael.j.wysocki \
    --to=rafael@kernel.org \
    --cc=christian.loehle@arm.com \
    --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