mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@kernel.org>
To: Liang Hao <haohlliang@gmail.com>,
	Anna-Maria Behnsen <anna-maria@linutronix.de>,
	Frederic Weisbecker <frederic@kernel.org>
Cc: linux-kernel@vger.kernel.org, Liang Hao <haohlliang@gmail.com>
Subject: Re: [PATCH] timers: Clear pending_map on CPU hotplug
Date: Tue, 29 Sep 2026 22:08:15 +0200	[thread overview]
Message-ID: <87bj9fizww.ffs@fw13> (raw)
In-Reply-To: <20260823115046.50930-1-haohlliang@gmail.com>

On Sun, Aug 23 2026 at 19:50, Liang Hao wrote:
> CPU hotplug migration leaves pending_map bits set on the outgoing CPU
> while its wheel vectors are empty. After re-online, a later next_expiry
> recalc can treat those empty buckets as pending and temporarily pull
> next_expiry forward until collect drains the bits.
>
> Clear pending_map under the base lock after migration in
> timers_dead_cpu(), and in timers_prepare_cpu() for a full base reinit.
>
> Signed-off-by: Liang Hao <haohlliang@gmail.com>
> ---
>  kernel/time/timer.c | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/kernel/time/timer.c b/kernel/time/timer.c
> index ae9abf14688e..e550489c73b8 100644
> --- a/kernel/time/timer.c
> +++ b/kernel/time/timer.c
> @@ -44,6 +44,7 @@
>  #include <linux/compat.h>
>  #include <linux/random.h>
>  #include <linux/sysctl.h>
> +#include <linux/bitmap.h>
>  
>  #include <linux/uaccess.h>
>  #include <asm/unistd.h>
> @@ -2509,6 +2510,7 @@ int timers_prepare_cpu(unsigned int cpu)
>  		base->next_expiry_recalc = false;
>  		base->timers_pending = false;
>  		base->is_idle = false;
> +		bitmap_zero(base->pending_map, WHEEL_SIZE);
>  	}
>  	return 0;
>  }
> @@ -2541,6 +2543,7 @@ int timers_dead_cpu(unsigned int cpu)
>  		for (i = 0; i < WHEEL_SIZE; i++)
>  			migrate_timer_list(new_base, old_base->vectors + i);
>  
> +		bitmap_zero(old_base->pending_map, WHEEL_SIZE);

Why do you need to zero the map twice - once when the CPU goes out and
then again when it comes back. That does not make sense.

Thanks

        tglx


  parent reply	other threads:[~2026-09-29 20:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23 11:50 Liang Hao
2026-08-24 15:21 ` Liang Hao
2026-09-29 20:08 ` Thomas Gleixner [this message]
2026-09-30  6:26   ` Liang Hao
2026-09-30  6:36 ` [PATCH v2] " Liang Hao

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=87bj9fizww.ffs@fw13 \
    --to=tglx@kernel.org \
    --cc=anna-maria@linutronix.de \
    --cc=frederic@kernel.org \
    --cc=haohlliang@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®