From: Frederic Weisbecker <frederic@kernel.org>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/idle: disable tick in idle=poll idle entry
Date: Thu, 8 Jun 2023 15:25:04 +0200 [thread overview]
Message-ID: <ZIHWsAC+n6mrDyFT@lothringen> (raw)
In-Reply-To: <ZIEqlkIASx2F2DRF@tpad>
On Wed, Jun 07, 2023 at 10:10:46PM -0300, Marcelo Tosatti wrote:
>
> 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.
>
> tick_nohz_idle_exit (called if the NEED_RESCHED bit is set)
> is responsible for re-enabling the tick when necessary.
>
> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
>
> ---
>
> diff --git a/kernel/sched/idle.c b/kernel/sched/idle.c
> index 342f58a329f5..fdc240988ea9 100644
> --- a/kernel/sched/idle.c
> +++ b/kernel/sched/idle.c
> @@ -276,7 +276,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();
cpu_idle_poll() re-enables interrupts and only checks need_resched(). If an
interrupt happens and queues a new timer without waking up a task, the timer
gets ignored.
> } else {
> cpuidle_idle_call();
>
prev parent reply other threads:[~2023-06-08 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 1:10 [PATCH] sched/idle: disable tick in idle=poll idle entry Marcelo Tosatti
2023-06-08 8:34 ` Peter Zijlstra
2023-06-09 13:54 ` Marcelo Tosatti
2023-06-08 13:25 ` 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=ZIHWsAC+n6mrDyFT@lothringen \
--to=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--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 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.