[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <wd3rjb7lfwmi2cnx3up3wkfiv4tamoz66vgtv756rfaqmwaiwf@7wapktjpctsj>
Date: Wed, 15 Oct 2025 10:56:47 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: Christian Loehle <christian.loehle@....com>,
Sergey Senozhatsky <senozhatsky@...omium.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 (25/10/14 16:02), Rafael J. Wysocki wrote:
> > >> 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.
Test results for menu.c from linux-next are within regressed range: 78.5
Powered by blists - more mailing lists