From: Greg KH <gregkh@linuxfoundation.org>
To: Christian Loehle <christian.loehle@arm.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
stable@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, vincent.guittot@linaro.org,
qyousef@layalina.io, peterz@infradead.org,
daniel.lezcano@linaro.org, ulf.hansson@linaro.org,
anna-maria@linutronix.de, dsmythies@telus.net,
kajetan.puchalski@arm.com, lukasz.luba@arm.com,
dietmar.eggemann@arm.com
Subject: Re: [PATCH 6.1.y] cpuidle: teo: Remove recent intercepts metric
Date: Wed, 14 Aug 2024 13:40:34 +0200 [thread overview]
Message-ID: <2024081410-camping-letter-1d17@gregkh> (raw)
In-Reply-To: <86d4bf8f-186d-4a65-9f06-3e4d5a2a2e1c@arm.com>
On Tue, Aug 13, 2024 at 02:18:53PM +0100, Christian Loehle wrote:
> On 8/12/24 13:42, Greg KH wrote:
> > On Mon, Aug 05, 2024 at 03:58:09PM +0100, Christian Loehle wrote:
> >> commit 449914398083148f93d070a8aace04f9ec296ce3 upstream.
> >>
> >> The logic for recent intercepts didn't work, there is an underflow
> >> of the 'recent' value that can be observed during boot already, which
> >> teo usually doesn't recover from, making the entire logic pointless.
> >> Furthermore the recent intercepts also were never reset, thus not
> >> actually being very 'recent'.
> >>
> >> Having underflowed 'recent' values lead to teo always acting as if
> >> we were in a scenario were expected sleep length based on timers is
> >> too high and it therefore unnecessarily selecting shallower states.
> >>
> >> Experiments show that the remaining 'intercept' logic is enough to
> >> quickly react to scenarios in which teo cannot rely on the timer
> >> expected sleep length.
> >>
> >> See also here:
> >> https://lore.kernel.org/lkml/0ce2d536-1125-4df8-9a5b-0d5e389cd8af@arm.com/
> >>
> >> Fixes: 77577558f25d ("cpuidle: teo: Rework most recent idle duration values treatment")
> >> Link: https://patch.msgid.link/20240628095955.34096-3-christian.loehle@arm.com
> >> Signed-off-by: Christian Loehle <christian.loehle@arm.com>
> >> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> >> ---
> >> drivers/cpuidle/governors/teo.c | 79 ++++++---------------------------
> >> 1 file changed, 14 insertions(+), 65 deletions(-)
> >
> > We can't just take a 6.1.y backport without newer kernels also having
> > this fix. Can you resend this as backports for all relevant kernels
> > please?
>
> Hi Greg,
> the email thread might've looked a bit strange to you but as I wrote
> in a previous reply:
> https://lore.kernel.org/linux-pm/20240628095955.34096-1-christian.loehle@arm.com/T/#ma5bcd00c4b0ffa1fc34e8d7fa237b8de4ee8a25c
> @stable
> 4b20b07ce72f cpuidle: teo: Don't count non-existent intercepts
> 449914398083 cpuidle: teo: Remove recent intercepts metric
> 0a2998fa48f0 Revert: "cpuidle: teo: Introduce util-awareness"
> apply as-is to
> linux-6.10.y
> linux-6.6.y
> for linux-6.1.y only 449914398083 ("cpuidle: teo: Remove recent intercepts metric")
> is relevant, I'll reply with a backport.
Please send all of these as a patch series for the relevent branches so
we know exactly what is going on...
thanks,
greg k-h
prev parent reply other threads:[~2024-08-14 11:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 9:59 [PATCHv3 0/3] cpuidle: teo: Fixing utilization and intercept logic Christian Loehle
2024-06-28 9:59 ` [PATCH 1/3] Revert: "cpuidle: teo: Introduce util-awareness" Christian Loehle
2024-06-28 9:59 ` [PATCH 2/3] cpuidle: teo: Remove recent intercepts metric Christian Loehle
2024-06-28 9:59 ` [PATCH 3/3] cpuidle: teo: Don't count non-existent intercepts Christian Loehle
2024-06-28 18:48 ` Rafael J. Wysocki
2024-06-29 8:22 ` [PATCHv4 " Christian Loehle
2024-07-01 16:59 ` Rafael J. Wysocki
2024-06-28 19:06 ` [PATCHv3 0/3] cpuidle: teo: Fixing utilization and intercept logic Rafael J. Wysocki
2024-06-29 8:23 ` Christian Loehle
2024-08-05 14:53 ` Christian Loehle
2024-08-05 14:58 ` [PATCH 6.1.y] cpuidle: teo: Remove recent intercepts metric Christian Loehle
2024-08-12 12:42 ` Greg KH
2024-08-13 13:18 ` Christian Loehle
2024-08-14 11:40 ` Greg KH [this message]
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=2024081410-camping-letter-1d17@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=anna-maria@linutronix.de \
--cc=christian.loehle@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=dietmar.eggemann@arm.com \
--cc=dsmythies@telus.net \
--cc=kajetan.puchalski@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=peterz@infradead.org \
--cc=qyousef@layalina.io \
--cc=rafael@kernel.org \
--cc=stable@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=vincent.guittot@linaro.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