Thread (10 messages) 10 messages, 2 authors, 2021-01-21

Re: [PATCH v2 4/5] csky: Fixup asm/cmpxchg.h with correct ordering barrier

From: Peter Zijlstra <peterz@infradead.org>
Date: 2021-01-07 12:42:02
Also in: lkml

On Sun, Dec 20, 2020 at 03:39:22PM +0000, guoren@kernel.org wrote:

+#define cmpxchg(ptr, o, n) 					\
+({								\
+	__typeof__(*(ptr)) __ret;				\
+	__smp_release_fence();					\
+	__ret = cmpxchg_relaxed(ptr, o, n);			\
+	__smp_acquire_fence();					\
+	__ret;							\
+})
So you failed to Cc me on patch #2 that introduces these barriers. I've
dug it out, but I'm still terribly confused on all that.

On first reading the above looks wrong.

Could you also clarify the difference (if any) between your bar.brwarw
and sync instruction?

Specifically, about transitiviry, or whatever we seem to be calling that
today.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help