From: Frederic Weisbecker <frederic@kernel.org>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-pm@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v3] sched/idle: disable tick in idle=poll idle entry
Date: Wed, 10 Dec 2025 14:43:30 +0100 [thread overview]
Message-ID: <aTl5Ah_x3UKWYU57@localhost.localdomain> (raw)
In-Reply-To: <aQiWfnnSzxsnwa2o@tpad>
Le Mon, Nov 03, 2025 at 08:48:14AM -0300, Marcelo Tosatti a écrit :
>
> Commit a5183862e76fdc25f36b39c2489b816a5c66e2e5
> ("tick/nohz: Conditionally restart tick on idle exit") allows
> a nohz_full CPU to enter idle and return from it with the
> scheduler tick disabled (since the tick might be undesired noise).
>
> The idle=poll case still unconditionally restarts the tick when entering
> idle.
>
> To reduce the noise for that case as well, stop the tick when entering
> idle, for the idle=poll case.
>
> Change tick_nohz_full_kick_cpu to set NEED_RESCHED bit, to handle the
> case where a new timer is added from an interrupt. This breaks out of
> cpu_idle_poll and rearms the timer if necessary.
>
> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
>
> ---
>
> v3: Add comment with proper explanation (Frederic Weisbecker)
> Add signed-off-by (Thomas Gleixner)
> v2: Handle the case where a new timer is added from an interrupt (Frederic Weisbecker)
>
> include/linux/sched.h | 2 ++
> kernel/sched/core.c | 10 ++++++++++
> kernel/sched/idle.c | 2 +-
> kernel/time/tick-sched.c | 7 +++++++
> 4 files changed, 20 insertions(+), 1 deletion(-)
>
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index cbb7340c5866..1f6938dc20cd 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -2428,4 +2428,6 @@ extern void migrate_enable(void);
>
> DEFINE_LOCK_GUARD_0(migrate, migrate_disable(), migrate_enable())
>
> +void set_tif_resched_if_polling(int cpu);
> +
> #endif
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index f1ebf67b48e2..f0b84600084b 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -988,6 +988,11 @@ static bool set_nr_if_polling(struct task_struct *p)
> return true;
> }
>
> +void set_tif_resched_if_polling(int cpu)
> +{
> + set_nr_if_polling(cpu_rq(cpu)->idle);
> +}
> +
> #else
> static inline bool set_nr_and_not_polling(struct thread_info *ti, int tif)
> {
> @@ -999,6 +1004,11 @@ static inline bool set_nr_if_polling(struct task_struct *p)
> {
> return false;
> }
> +
> +void set_tif_resched_if_polling(int cpu)
> +{
> + set_tsk_need_resched(cpu_rq(cpu)->idle);
> +}
> #endif
>
> static bool __wake_q_add(struct wake_q_head *head, struct task_struct *task)
> diff --git a/kernel/sched/idle.c b/kernel/sched/idle.c
> index c39b089d4f09..428c2d1cbd1b 100644
> --- a/kernel/sched/idle.c
> +++ b/kernel/sched/idle.c
> @@ -324,7 +324,7 @@ static void do_idle(void)
> * idle as we know that the IPI is going to arrive right away.
> */
> if (cpu_idle_force_poll || tick_check_broadcast_expired()) {
> - tick_nohz_idle_restart_tick();
> + tick_nohz_idle_stop_tick();
> cpu_idle_poll();
I still think that the polling probably should happen in userspace rather than in
kernelspace. But if we have to go down that road, the tick stop here should only
happen if the CPU is nohz_full. Namely we should have
tick_nohz_full_idle_stop_tick() and provide a comment why we are doing that.
Because aside nohz_full, stopping the tick here is useless and can make things
worse for realtime workloads which may spend time reprogramming the tick while
a high prio task is waiting for the CPU.
Thanks.
--
Frederic Weisbecker
SUSE Labs
prev parent reply other threads:[~2025-12-10 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 11:48 [PATCH v3] sched/idle: disable tick in idle=poll idle entry Marcelo Tosatti
2025-11-03 12:30 ` Peter Zijlstra
2025-11-05 12:57 ` Marcelo Tosatti
2025-12-08 15:53 ` Marcelo Tosatti
2025-12-10 13:43 ` Frederic Weisbecker [this message]
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=aTl5Ah_x3UKWYU57@localhost.localdomain \
--to=frederic@kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).