arm64: atomics: fix grossly inconsistent asm constraints for exclusives
Our uses of inline asm constraints for atomic operations are fairly wild and varied. We basically need to guarantee the following: 1. Any instructions with barrier implications (load-acquire/store-release) have a "memory" clobber 2. When performing exclusive accesses, the addresing mode is generated using the "Q" constraint 3. Atomic blocks which use the condition flags, have a "cc" clobber This patch addresses these concerns which, as well as fixing the semantics of the code, stops GCC complaining about impossible asm constraints. Signed-off-by:Will Deacon <will.deacon@arm.com> Signed-off-by:
Catalin Marinas <catalin.marinas@arm.com>
Showing
- arch/arm64/include/asm/atomic.h 66 additions, 66 deletionsarch/arm64/include/asm/atomic.h
- arch/arm64/include/asm/cmpxchg.h 37 additions, 37 deletionsarch/arm64/include/asm/cmpxchg.h
- arch/arm64/include/asm/futex.h 1 addition, 1 deletionarch/arm64/include/asm/futex.h
- arch/arm64/include/asm/spinlock.h 39 additions, 39 deletionsarch/arm64/include/asm/spinlock.h
Loading
Please register or sign in to comment