mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kunwu Chan <kunwu.chan@gmail.com>
To: arnd@arndb.de, anna-maria@linutronix.de, frederic@kernel.org,
	mingo@kernel.org, tglx@kernel.org
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
	Kunwu Chan <kunwu.chan@gmail.com>
Subject: [PATCH v3 0/2] rwonce: Introduce {READ,WRITE}_ONCE_THIS_CPU()
Date: Wed,  7 Oct 2026 10:28:57 +0800	[thread overview]
Message-ID: <20261007022859.60101-1-kunwu.chan@gmail.com> (raw)

Hi,

This is a rebase of v2 onto v7.3-rc6 with review tags collected
since v2.

Changes since v2 [1]:
 - Rebased onto v7.3-rc6.
 - Collected Reviewed-by and Acked-by tags.

[1] https://lore.kernel.org/lkml/20261002151757.3605081-1-kunwu.chan@gmail.com/

Changes since v1 [2]:
 - Introduce {READ,WRITE}_ONCE_THIS_CPU() instead of reusing the
   plain variants. (Thomas Gleixner)

 - Expand the commit messages to state the KCSAN rationale. (Thomas
   Gleixner)

[2] https://lore.kernel.org/all/20260920085434.2918331-1-kunwu.chan@gmail.com/
 
Kunwu Chan (2):
  rwonce: Add READ_ONCE_THIS_CPU() and WRITE_ONCE_THIS_CPU()
  timers/nohz: Mark got_idle_tick accesses as same-CPU races

 include/asm-generic/rwonce.h | 11 +++++++++++
 kernel/time/tick-sched.c     |  6 +++---
 2 files changed, 14 insertions(+), 3 deletions(-)


base-commit: a90ee4305c4a5df72c11b31dacfdc76e00fcf78a
-- 
2.43.0


             reply	other threads:[~2026-10-07  2:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07  2:28 Kunwu Chan [this message]
2026-10-07  2:28 ` [PATCH v3 1/2] rwonce: Add READ_ONCE_THIS_CPU() and WRITE_ONCE_THIS_CPU() Kunwu Chan
2026-10-07 10:50   ` Arnd Bergmann
2026-10-07  2:28 ` [PATCH v3 2/2] timers/nohz: Mark got_idle_tick accesses as same-CPU races Kunwu Chan

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=20261007022859.60101-1-kunwu.chan@gmail.com \
    --to=kunwu.chan@gmail.com \
    --cc=anna-maria@linutronix.de \
    --cc=arnd@arndb.de \
    --cc=frederic@kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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®