[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5085160.31r3eYUQgx@rafael.j.wysocki>
Date: Sun, 16 Nov 2025 13:34:29 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Linux PM <linux-pm@...r.kernel.org>
Cc: Christian Loehle <christian.loehle@....com>,
LKML <linux-kernel@...r.kernel.org>
Subject:
[PATCH v1 1/2] cpuidle: governors: teo: Fix tick_intercepts handling in
teo_update()
From: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
The condition deciding whether or not to increase cpu_data->tick_intercepts
in teo_update() is reverse, so fix it.
Fixes: d619b5cc6780 ("cpuidle: teo: Simplify counting events used for tick management")
Cc: All applicable <stable@...r.kernel.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
---
I'm planning to apply this for 6.19 on top of
https://lore.kernel.org/linux-pm/6228387.lOV4Wx5bFT@rafael.j.wysocki/
because that patch (indirectly) depends on commit d619b5cc6780.
---
drivers/cpuidle/governors/teo.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/cpuidle/governors/teo.c
+++ b/drivers/cpuidle/governors/teo.c
@@ -251,7 +251,7 @@ static void teo_update(struct cpuidle_dr
cpu_data->state_bins[idx_timer].hits += PULSE;
} else {
cpu_data->state_bins[idx_duration].intercepts += PULSE;
- if (TICK_NSEC <= measured_ns)
+ if (measured_ns <= TICK_NSEC)
cpu_data->tick_intercepts += PULSE;
}
}
Powered by blists - more mailing lists