From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
Christian Loehle <christian.loehle@arm.com>,
Sasha Levin <sashal@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Tomasz Figa <tfiga@chromium.org>,
stable@vger.kernel.org
Subject: Re: stable: commit "cpuidle: menu: Avoid discarding useful information" causes regressions
Date: Tue, 14 Oct 2025 09:47:24 +0200 [thread overview]
Message-ID: <2025101451-unlinked-strongly-2fb3@gregkh> (raw)
In-Reply-To: <36iykr223vmcfsoysexug6s274nq2oimcu55ybn6ww4il3g3cv@cohflgdbpnq7>
On Tue, Oct 14, 2025 at 04:43:43PM +0900, Sergey Senozhatsky wrote:
> Hello,
>
> We are observing performance regressions (cpu usage, power
> consumption, dropped frames in video playback test, etc.)
> after updating to recent stable kernels. We tracked it down
> to commit 3cd2aa93674e in linux-6.1.y and commit 3cd2aa93674
> in linux-6.6.y ("cpuidle: menu: Avoid discarding useful information",
> upstream commit 85975daeaa4).
>
> Upstream fixup fa3fa55de0d ("cpuidle: governors: menu: Avoid using
> invalid recent intervals data") doesn't address the problems we are
> observing. Revert seems to be bringing performance metrics back to
> pre-regression levels.
>
For some reason that commit was not added to the 6.1 releases, sorry
about that. Can you submit a working/tested backport so we can queue it
up after the next round of releases in a few days?
thanks,
greg k-h
next prev parent reply other threads:[~2025-10-14 7:47 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 7:43 stable: commit "cpuidle: menu: Avoid discarding useful information" causes regressions Sergey Senozhatsky
2025-10-14 7:47 ` Greg Kroah-Hartman [this message]
2025-10-14 7:54 ` Sergey Senozhatsky
2025-10-14 8:02 ` Greg Kroah-Hartman
2025-10-14 11:08 ` Sergey Senozhatsky
2025-10-14 9:50 ` Christian Loehle
2025-10-14 10:23 ` Sergey Senozhatsky
2025-10-14 10:25 ` Christian Loehle
2025-10-14 11:55 ` Sergey Senozhatsky
2025-10-14 15:11 ` Christian Loehle
2025-10-14 15:54 ` Rafael J. Wysocki
2025-10-14 17:19 ` Christian Loehle
2025-10-14 17:32 ` Rafael J. Wysocki
2025-10-14 17:50 ` Rafael J. Wysocki
2025-10-15 1:29 ` Sergey Senozhatsky
2025-10-15 3:41 ` Doug Smythies
2025-10-15 4:50 ` Sergey Senozhatsky
2025-10-15 14:11 ` Doug Smythies
2025-10-16 4:59 ` Sergey Senozhatsky
2025-10-16 9:48 ` Rafael J. Wysocki
2025-10-16 10:00 ` Sergey Senozhatsky
2025-10-16 10:05 ` Rafael J. Wysocki
2025-10-15 11:49 ` Rafael J. Wysocki
2025-10-15 14:32 ` Doug Smythies
2025-10-16 9:50 ` Rafael J. Wysocki
2025-10-15 12:31 ` Rafael J. Wysocki
2025-10-16 4:57 ` Sergey Senozhatsky
2025-10-15 1:33 ` Sergey Senozhatsky
2025-10-14 13:47 ` Rafael J. Wysocki
2025-10-14 13:56 ` Sergey Senozhatsky
2025-10-14 13:58 ` Christian Loehle
2025-10-14 14:02 ` Rafael J. Wysocki
2025-10-15 1:56 ` Sergey Senozhatsky
2025-10-15 13:08 ` Rafael J. Wysocki
2025-10-16 4:54 ` Sergey Senozhatsky
2025-10-16 9:47 ` 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=2025101451-unlinked-strongly-2fb3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=artem.bityutskiy@linux.intel.com \
--cc=christian.loehle@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=sashal@kernel.org \
--cc=senozhatsky@chromium.org \
--cc=stable@vger.kernel.org \
--cc=tfiga@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.