Searched refs:CMPXCHG (Results 1 – 6 of 6) sorted by relevance
| /Linux-v4.19/arch/x86/kvm/ |
| D | paging_tmpl.h | 40 #define CMPXCHG cmpxchg macro
42 #define CMPXCHG cmpxchg64 macro
58 #define CMPXCHG cmpxchg macro
71 #define CMPXCHG cmpxchg64 macro
149 ret = CMPXCHG(&table[index], orig_pte, new_pte); in FNAME()
1051 #undef CMPXCHG
|
| /Linux-v4.19/Documentation/locking/ |
| D | rt-mutex-design.txt | 327 the architecture does not support CMPXCHG, then this macro is simply set
328 to fail every time. But if CMPXCHG is supported, then this will
413 done when we have CMPXCHG enabled (otherwise the fast taking automatically
415 taken with the CMPXCHG and nothing else needs to be done.
430 does not implement CMPXCHG would always grab the lock (if there's no
506 CMPXCHG. Since the taking of a mutex on contention always sets the
512 If the owner field has the "Has Waiters" bit set (or CMPXCHG is not available),
519 do not have CMPXCHG, this is the location that the owner of the mutex will
521 do have CMPXCHG, that check is done in the fast path, but it is still needed
523 or timeout between the time the owner failed the fast path CMPXCHG check and
|
| /Linux-v4.19/Documentation/ |
| D | atomic_t.txt | 97 will invalidate a LL/SC or fail a CMPXCHG.
|
| /Linux-v4.19/tools/objtool/arch/x86/lib/ |
| D | x86-opcode-map.txt | 527 b0: CMPXCHG Eb,Gb
528 b1: CMPXCHG Ev,Gv
|
| /Linux-v4.19/tools/perf/util/intel-pt-decoder/ |
| D | x86-opcode-map.txt | 527 b0: CMPXCHG Eb,Gb
528 b1: CMPXCHG Ev,Gv
|
| /Linux-v4.19/arch/x86/lib/ |
| D | x86-opcode-map.txt | 527 b0: CMPXCHG Eb,Gb
528 b1: CMPXCHG Ev,Gv
|
