From: Kunwu Chan <kunwu.chan@gmail.com>
To: anna-maria@linutronix.de, frederic@kernel.org, mingo@kernel.org,
tglx@kernel.org
Cc: linux-kernel@vger.kernel.org, paulmck@kernel.org,
Kunwu Chan <kunwu.chan@gmail.com>
Subject: [PATCH] timers/nohz: Annotate lockless accesses to got_idle_tick
Date: Sun, 20 Sep 2026 16:54:34 +0800 [thread overview]
Message-ID: <20260920085434.2918331-1-kunwu.chan@gmail.com> (raw)
tick_sched_do_timer(), called from the tick interrupt handler, sets
ts->got_idle_tick when a tick fires while the CPU is idle. The idle
path reads and clears it via tick_nohz_idle_got_tick() to detect
whether the tick handler has run.
The flag is accessed locklessly from hardirq and task context. A
concurrent set can be overwritten by the clear.
Use READ_ONCE() and WRITE_ONCE() to annotate the lockless accesses.
Signed-off-by: Kunwu Chan <kunwu.chan@gmail.com>
---
kernel/time/tick-sched.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
index 6c3fea386713..c0ab32e543b3 100644
--- a/kernel/time/tick-sched.c
+++ b/kernel/time/tick-sched.c
@@ -269,7 +269,7 @@ static void tick_sched_do_timer(struct tick_sched *ts, ktime_t now)
}
if (tick_sched_flag_test(ts, TS_FLAG_INIDLE))
- ts->got_idle_tick = 1;
+ WRITE_ONCE(ts->got_idle_tick, 1);
}
static void tick_sched_handle(struct tick_sched *ts, struct pt_regs *regs)
@@ -1248,8 +1248,8 @@ bool tick_nohz_idle_got_tick(void)
{
struct tick_sched *ts = this_cpu_ptr(&tick_cpu_sched);
- if (ts->got_idle_tick) {
- ts->got_idle_tick = 0;
+ if (READ_ONCE(ts->got_idle_tick)) {
+ WRITE_ONCE(ts->got_idle_tick, 0);
return true;
}
return false;
--
2.43.0
reply other threads:[~2026-09-20 8:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260920085434.2918331-1-kunwu.chan@gmail.com \
--to=kunwu.chan@gmail.com \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@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®