[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <yapeufdqxobl7yn2ylmtktyon55nofcpwujnwjjrwol37pxw4t@wv3akoz5w6f2>
Date: Wed, 15 Oct 2025 10:33:08 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Christian Loehle <christian.loehle@....com>
Cc: 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:11), Christian Loehle wrote:
> (Also I can't send this email without at least recommending teo instead of menu
> for your platform / use-cases, if you deemed it unfit I'd love to know what
> didn't work for you!)
I can't tell for sure, I see a number of bugs evaluating teo vs menu,
one of which mentions the following:
on Tigerlake/Alderlake hardware [..] TEO leads to higher power
consumption (130mw more power usage in video conferencing) when
compared to menu.
Powered by blists - more mailing lists