From: Thomas Gleixner <tglx@linutronix.de>
To: Ulf Hansson <ulf.hansson@linaro.org>,
"Rafael J . Wysocki" <rafael@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Marc Zyngier <maz@kernel.org>,
Maulik Shah <quic_mkshah@quicinc.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Ben Horgan <ben.horgan@arm.com>,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH v4 1/2] smp: Introduce a helper function to check for pending IPIs
Date: Thu, 13 Nov 2025 16:29:31 +0100 [thread overview]
Message-ID: <874iqyc5no.ffs@tglx> (raw)
In-Reply-To: <20251105095415.17269-2-ulf.hansson@linaro.org>
On Wed, Nov 05 2025 at 10:54, Ulf Hansson wrote:
> When governors used during cpuidle try to find the most optimal idle state
> for a CPU or a group of CPUs, they are known to quite often fail. One
> reason for this is, that they are not taking into account whether there has
> been an IPI scheduled for any of the CPUs that are affected by the selected
> idle state.
>
> To enable pending IPIs to be taken into account for cpuidle decisions,
> introduce a new helper function, cpus_peek_for_pending_ipi().
>
> Suggested-by: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
next prev parent reply other threads:[~2025-11-13 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 9:54 [PATCH v4 0/2] pmdomain: Improve idle state selection for CPUs Ulf Hansson
2025-11-05 9:54 ` [PATCH v4 1/2] smp: Introduce a helper function to check for pending IPIs Ulf Hansson
2025-11-13 15:29 ` Thomas Gleixner [this message]
2025-11-05 9:54 ` [PATCH v4 2/2] pmdomain: Extend the genpd governor for CPUs to account for IPIs Ulf Hansson
2025-11-14 16:16 ` [PATCH v4 0/2] pmdomain: Improve idle state selection for CPUs Ulf Hansson
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=874iqyc5no.ffs@tglx \
--to=tglx@linutronix.de \
--cc=ben.horgan@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=quic_mkshah@quicinc.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=ulf.hansson@linaro.org \
--cc=vincent.guittot@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.