From: Jules Maselbas <jmaselbas@kalray.eu>
To: Will Deacon <will@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Boqun Feng <boqun.feng@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
Arnd Bergmann <arnd@arndb.de>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
Jules Maselbas <jmaselbas@kalray.eu>
Subject: [PATCH] locking/atomic: atomic: Use arch_atomic_{read,set} in generic atomic ops
Date: Thu, 26 Jan 2023 18:33:54 +0100 [thread overview]
Message-ID: <20230126173354.13250-1-jmaselbas@kalray.eu> (raw)
Reading and setting the atomic counter should be done through
arch_atomic_{read,set} macros, which respectively uses {READ,WRITE}_ONCE
macros.
This is to avoid the compiler from potentially replay the read access.
Suggested-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Jules Maselbas <jmaselbas@kalray.eu>
---
include/asm-generic/atomic.h | 31 +++++++++++++++++--------------
1 file changed, 17 insertions(+), 14 deletions(-)
diff --git a/include/asm-generic/atomic.h b/include/asm-generic/atomic.h
index 04b8be9f1a77..711e408af581 100644
--- a/include/asm-generic/atomic.h
+++ b/include/asm-generic/atomic.h
@@ -12,6 +12,9 @@
#include <asm/cmpxchg.h>
#include <asm/barrier.h>
+#define arch_atomic_read(v) READ_ONCE((v)->counter)
+#define arch_atomic_set(v, i) WRITE_ONCE(((v)->counter), (i))
+
#ifdef CONFIG_SMP
/* we can build all atomic primitives from cmpxchg */
@@ -21,7 +24,7 @@ static inline void generic_atomic_##op(int i, atomic_t *v) \
{ \
int c, old; \
\
- c = v->counter; \
+ c = arch_atomic_read(v); \
while ((old = arch_cmpxchg(&v->counter, c, c c_op i)) != c) \
c = old; \
}
@@ -31,7 +34,7 @@ static inline int generic_atomic_##op##_return(int i, atomic_t *v) \
{ \
int c, old; \
\
- c = v->counter; \
+ c = arch_atomic_read(v); \
while ((old = arch_cmpxchg(&v->counter, c, c c_op i)) != c) \
c = old; \
\
@@ -43,7 +46,7 @@ static inline int generic_atomic_fetch_##op(int i, atomic_t *v) \
{ \
int c, old; \
\
- c = v->counter; \
+ c = arch_atomic_read(v); \
while ((old = arch_cmpxchg(&v->counter, c, c c_op i)) != c) \
c = old; \
\
@@ -58,9 +61,11 @@ static inline int generic_atomic_fetch_##op(int i, atomic_t *v) \
static inline void generic_atomic_##op(int i, atomic_t *v) \
{ \
unsigned long flags; \
+ int c; \
\
raw_local_irq_save(flags); \
- v->counter = v->counter c_op i; \
+ c = arch_atomic_read(v); \
+ arch_atomic_set(v, c c_op i); \
raw_local_irq_restore(flags); \
}
@@ -68,27 +73,28 @@ static inline void generic_atomic_##op(int i, atomic_t *v) \
static inline int generic_atomic_##op##_return(int i, atomic_t *v) \
{ \
unsigned long flags; \
- int ret; \
+ int c; \
\
raw_local_irq_save(flags); \
- ret = (v->counter = v->counter c_op i); \
+ c = arch_atomic_read(v); \
+ arch_atomic_set(v, c c_op i); \
raw_local_irq_restore(flags); \
\
- return ret; \
+ return c c_op i; \
}
#define ATOMIC_FETCH_OP(op, c_op) \
static inline int generic_atomic_fetch_##op(int i, atomic_t *v) \
{ \
unsigned long flags; \
- int ret; \
+ int c; \
\
raw_local_irq_save(flags); \
- ret = v->counter; \
- v->counter = v->counter c_op i; \
+ c = arch_atomic_read(v); \
+ arch_atomic_set(v, c c_op i); \
raw_local_irq_restore(flags); \
\
- return ret; \
+ return c; \
}
#endif /* CONFIG_SMP */
@@ -127,9 +133,6 @@ ATOMIC_OP(xor, ^)
#define arch_atomic_or generic_atomic_or
#define arch_atomic_xor generic_atomic_xor
-#define arch_atomic_read(v) READ_ONCE((v)->counter)
-#define arch_atomic_set(v, i) WRITE_ONCE(((v)->counter), (i))
-
#define arch_atomic_xchg(ptr, v) (arch_xchg(&(ptr)->counter, (v)))
#define arch_atomic_cmpxchg(v, old, new) (arch_cmpxchg(&((v)->counter), (old), (new)))
--
2.17.1
next reply other threads:[~2023-01-26 17:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 17:33 Jules Maselbas [this message]
2023-01-27 11:18 ` [PATCH] locking/atomic: atomic: Use arch_atomic_{read,set} in generic atomic ops Peter Zijlstra
2023-01-27 13:49 ` Jules Maselbas
2023-01-27 14:34 ` Peter Zijlstra
2023-01-27 22:09 ` Boqun Feng
2023-01-30 12:23 ` Jonas Oberhauser
2023-01-30 18:38 ` Boqun Feng
2023-01-31 15:08 ` Jonas Oberhauser
2023-01-31 22:03 ` Boqun Feng
2023-02-01 10:51 ` Jonas Oberhauser
2023-01-30 18:15 ` Jules Maselbas
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=20230126173354.13250-1-jmaselbas@kalray.eu \
--to=jmaselbas@kalray.eu \
--cc=arnd@arndb.de \
--cc=boqun.feng@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peterz@infradead.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).