[PATCH v10 3/4] qrwlock, x86: Add char and short as atomic data type in x86
From: Waiman Long
Date: Wed Jan 22 2014 - 16:34:47 EST
The generic __native_word() macro defined in include/linux/compiler.h
only allows "int" and "long" data types to be treated as native and
atomic. The x86 architecture, however, allow the use of char and short
data types as atomic as well.
This patch extends the data type allowed in the __native_word() macro to
allow the use of char and short for the x86 architecture.
Signed-off-by: Waiman Long <Waiman.Long@xxxxxx>
arch/x86/include/asm/barrier.h | 18 ++++++++++++++++++
1 files changed, 18 insertions(+), 0 deletions(-)
diff --git a/arch/x86/include/asm/barrier.h b/arch/x86/include/asm/barrier.h
index 04a4890..0149a66 100644
@@ -24,6 +24,24 @@
#define wmb() asm volatile("sfence" ::: "memory")
+ * Define x86 specific atomic types that can be used in read_acquire
+ * and store_release barriers.
+#define __arch_native_word(t) (sizeof(t) == sizeof(char) || \
+ sizeof(t) == sizeof(short) || \
+ sizeof(t) == sizeof(int) || \
+ sizeof(t) == sizeof(long))
+ * Due to cyclic header file dependency problem, the only way to modify
+ * the behavior of __native_word() macro within
+ * compiletime_assert_atomic_type() is to redefine it.
+#define __native_word(t) __arch_native_word(t)
* read_barrier_depends - Flush all pending reads that subsequents reads
* depend on.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/