[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0iF0NE07KcK4J2_Pko-1p2wuQXjLSD7iOTBr4QcDCX4vA@mail.gmail.com>
Date: Tue, 14 Oct 2025 16:02:05 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Christian Loehle <christian.loehle@....com>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>, "Rafael J. Wysocki" <rafael@...nel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Artem Bityutskiy <artem.bityutskiy@...ux.intel.com>, Sasha Levin <sashal@...nel.org>,
Daniel Lezcano <daniel.lezcano@...aro.org>, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, Tomasz Figa <tfiga@...omium.org>, stable@...r.kernel.org
Subject: Re: stable: commit "cpuidle: menu: Avoid discarding useful
information" causes regressions
On Tue, Oct 14, 2025 at 3:59 PM Christian Loehle
<christian.loehle@....com> wrote:
>
> On 10/14/25 14:56, Sergey Senozhatsky wrote:
> > On (25/10/14 15:47), Rafael J. Wysocki wrote:
> >> On Tue, Oct 14, 2025 at 12:23 PM Sergey Senozhatsky
> >> <senozhatsky@...omium.org> wrote:
> >>>
> >>>> Any details would be much appreciated.
> >>>> How do the idle state usages differ with and without
> >>>> "cpuidle: menu: Avoid discarding useful information"?
> >>>> What do the idle states look like in your platform?
> >>>
> >>> Sure, I can run tests.
> >>
> >> Would it be possible to check if the mainline has this issue? That
> >> is, compare the benchmark results on unmodified 6.17 (say) and on 6.17
> >> with commit 85975daeaa4 reverted?
> >
> > I don't think mainline kernel can run on those devices (due to
> > a bunch of downstream patches). Best bet is 6.12, I guess.
>
> Depending on what Rafael is expecting here you might just get
> away with copying menu.c from mainline, the interactions to other
> subsystems are limited fortunately.
Yeah, that'd be sufficiently close.
Powered by blists - more mailing lists