From: Christian Loehle <christian.loehle@arm.com>
To: Chris Friesen <chris.friesen@windriver.com>,
daniel.lezcano@linaro.org, kgene@kernel.org,
krzysztof.kozlowski@linaro.org, linux-pm@vger.kernel.org
Subject: Re: question about behaviour of cpuidle on 6.6...seeing *many* missed estimates
Date: Fri, 27 Jun 2025 08:49:01 +0100 [thread overview]
Message-ID: <7d43a796-d831-430b-92d9-53b3d8351fb6@arm.com> (raw)
In-Reply-To: <0dd1f3be-3bdf-44c9-a6d5-623077714149@windriver.com>
On 6/26/25 19:26, Chris Friesen wrote:
> Hi,
>
> I've got an Ice Lake server running 6.6 PREEMPT_RT, currently using the acpi_idle cpuidle driver and the "menu" governor. I'm seeing some weird behaviour with cpuidle and C-states and was hoping someone might be able to shed some light on what's happening.
Does your kernel include
3cd2aa93674e cpuidle: menu: Avoid discarding useful information
(since v6.6.93)?
> [snip]
next prev parent reply other threads:[~2025-06-27 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 18:26 question about behaviour of cpuidle on 6.6...seeing *many* missed estimates Chris Friesen
2025-06-27 7:49 ` Christian Loehle [this message]
2025-06-27 14:41 ` Chris Friesen
2025-07-08 14:56 ` Chris Friesen
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=7d43a796-d831-430b-92d9-53b3d8351fb6@arm.com \
--to=christian.loehle@arm.com \
--cc=chris.friesen@windriver.com \
--cc=daniel.lezcano@linaro.org \
--cc=kgene@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-pm@vger.kernel.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