From: Liang Hao <haohlliang@gmail.com>
To: tglx@kernel.org
Cc: anna-maria@linutronix.de, frederic@kernel.org,
haohlliang@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] timers: Clear pending_map on CPU hotplug
Date: Wed, 30 Sep 2026 14:26:42 +0800 [thread overview]
Message-ID: <20260930062642.36164-1-haohlliang@gmail.com> (raw)
In-Reply-To: <87bj9fizww.ffs@fw13>
On Tue, 29 Sep 2026 at 22:08, Thomas Gleixner wrote:
> 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.
You're right - clearing it twice is redundant. The stale bits come from
migration in timers_dead_cpu(); clearing pending_map there after migration
is sufficient. I'll remove the timers_prepare_cpu() part in v2.
Thanks,
Liang Hao
next prev parent reply other threads:[~2026-09-30 6:26 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
2026-09-30 6:26 ` Liang Hao [this message]
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=20260930062642.36164-1-haohlliang@gmail.com \
--to=haohlliang@gmail.com \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@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®