Searched refs:CMPXCHG (Results 1 – 5 of 5) sorted by relevance
| /Linux-v5.10/arch/x86/kvm/mmu/ |
| D | paging_tmpl.h | 37 #define CMPXCHG cmpxchg macro
39 #define CMPXCHG cmpxchg64 macro
55 #define CMPXCHG cmpxchg macro
68 #define CMPXCHG cmpxchg64 macro
158 ret = CMPXCHG(&table[index], orig_pte, new_pte); in FNAME()
181 ret = CMPXCHG(&table[index], orig_pte, new_pte); in FNAME()
1104 #undef CMPXCHG
|
| /Linux-v5.10/Documentation/locking/ |
| D | rt-mutex-design.rst | 337 the architecture does not support CMPXCHG, then this macro is simply set
338 to fail every time. But if CMPXCHG is supported, then this will
424 done when we have CMPXCHG enabled (otherwise the fast taking automatically
426 taken with the CMPXCHG and nothing else needs to be done.
441 does not implement CMPXCHG would always grab the lock (if there's no
518 CMPXCHG. Since the taking of a mutex on contention always sets the
524 If the owner field has the "Has Waiters" bit set (or CMPXCHG is not available),
531 do not have CMPXCHG, this is the location that the owner of the mutex will
533 do have CMPXCHG, that check is done in the fast path, but it is still needed
535 or timeout between the time the owner failed the fast path CMPXCHG check and
|
| /Linux-v5.10/Documentation/ |
| D | atomic_t.txt | 116 will invalidate a LL/SC or fail a CMPXCHG.
|
| /Linux-v5.10/arch/x86/lib/ |
| D | x86-opcode-map.txt | 527 b0: CMPXCHG Eb,Gb
528 b1: CMPXCHG Ev,Gv
|
| /Linux-v5.10/tools/arch/x86/lib/ |
| D | x86-opcode-map.txt | 527 b0: CMPXCHG Eb,Gb
528 b1: CMPXCHG Ev,Gv
|
