From: Christian Loehle <christian.loehle@arm.com>
To: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>,
"Maulik Shah (mkshah)" <maulik.shah@oss.qualcomm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Daniel Lezcano <daniel.lezcano@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2] cpuidle: Deny idle entry when CPU already have IPI interrupt pending
Date: Fri, 21 Aug 2026 11:15:10 +0100 [thread overview]
Message-ID: <ed4ab782-e4a7-4bb4-b63c-3ecd24e73ad9@arm.com> (raw)
In-Reply-To: <6d5dfbaa-f0e0-425e-bacf-f177185d1eff@oss.qualcomm.com>
On 8/21/26 10:28, Daniel Lezcano wrote:
>
> Le 21/08/2026 à 07:03, Maulik Shah (mkshah) a écrit :
>
> [ ... ]
>>> What do we do about the cpuidle stats in that case?
>>> I'm thinking primiarly about last_residency_ns and rejected here.
>>
>> As the idle entry will not happen (call_cpuidle() is not invoked)
>> the stats would also not required to be updated.
> I agree, with the IPI pending it is like the idle task should have not be scheduled, so the idle call is aborted.
AFAICS since the ->select() callback has already run we should
set last_residency_ns == 0, like the need_resched() path in
call_cpuidle() does?
At least menu has a semantic difference in how it decays values
for get_typical_interval() between a UINT_MAX (i.e. invalid)
residency and one it's never seen?
next prev parent reply other threads:[~2026-08-21 10:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 4:08 Maulik Shah
2026-04-06 15:07 ` Rafael J. Wysocki
2026-04-13 5:03 ` Maulik Shah (mkshah)
2026-08-18 16:10 ` Christian Loehle
2026-08-21 5:03 ` Maulik Shah (mkshah)
2026-08-21 9:28 ` Daniel Lezcano
2026-08-21 10:15 ` Christian Loehle [this message]
2026-08-21 13:03 ` Rafael J. Wysocki (Intel)
2026-08-18 8:51 ` kernel test robot
2026-08-18 10:30 ` kernel test robot
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=ed4ab782-e4a7-4bb4-b63c-3ecd24e73ad9@arm.com \
--to=christian.loehle@arm.com \
--cc=daniel.lezcano@kernel.org \
--cc=daniel.lezcano@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=maulik.shah@oss.qualcomm.com \
--cc=rafael@kernel.org \
--cc=ulf.hansson@linaro.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
all inboxes | Powered by JetHome®