Lines Matching refs:CMPXCHG

349 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
736 or timeout between the time the owner failed the fast path CMPXCHG check and