Home
last modified time | relevance | path

Searched refs:CMPXCHG (Results 1 – 4 of 4) sorted by relevance

/linux-3.4.99/arch/x86/kvm/
Dpaging_tmpl.h37 #define CMPXCHG cmpxchg macro
39 #define CMPXCHG cmpxchg64 macro
52 #define CMPXCHG cmpxchg macro
96 ret = CMPXCHG(&table[index], orig_pte, new_pte); in FNAME()
837 #undef CMPXCHG
/linux-3.4.99/Documentation/
Drt-mutex-design.txt349 the architecture does not support CMPXCHG, then this macro is simply set
350 to fail every time. But if CMPXCHG is supported, then this will
562 done when we have CMPXCHG enabled (otherwise the fast taking automatically
564 taken with the CMPXCHG and nothing else needs to be done.
579 does not implement CMPXCHG would always grab the lock (if there's no
588 play nice for those architectures that do have CMPXCHG. By setting this flag
719 CMPXCHG. Since the taking of a mutex on contention always sets the
725 If the owner field has the "Has Waiters" bit set (or CMPXCHG is not available),
732 do not have CMPXCHG, this is the location that the owner of the mutex will
734 do have CMPXCHG, that check is done in the fast path, but it is still needed
[all …]
/linux-3.4.99/arch/x86/kernel/acpi/
Dboot.c82 #warning ACPI uses CMPXCHG, i486 and later hardware
/linux-3.4.99/arch/x86/lib/
Dx86-opcode-map.txt510 b0: CMPXCHG Eb,Gb
511 b1: CMPXCHG Ev,Gv