From: Christian Loehle <christian.loehle@arm.com>
To: Sergey Senozhatsky <senozhatsky@chromium.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.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 14:58:50 +0100 [thread overview]
Message-ID: <a9857ceb-bf3e-4229-9c2f-ecab6eb2e1b0@arm.com> (raw)
In-Reply-To: <ns2dglxkdqiidj445xal2w4onk56njkzllgoads377oaix7wuh@afvq7yinhpl7>
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@chromium.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.
next prev parent reply other threads:[~2025-10-14 13:59 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
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 [this message]
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=a9857ceb-bf3e-4229-9c2f-ecab6eb2e1b0@arm.com \
--to=christian.loehle@arm.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox