Home
last modified time | relevance | path

Searched refs:wounded (Results 1 – 5 of 5) sorted by relevance

/linux/kernel/locking/
H A Dww_rt_mutex.c20 * Reset the wounded flag after a kill. No other process can in ww_mutex_trylock()
25 ww_ctx->wounded = 0; in ww_mutex_trylock()
52 * Reset the wounded flag after a kill. No other process can in __ww_rt_mutex_lock()
57 ww_ctx->wounded = 0; in __ww_rt_mutex_lock()
H A Dww_mutex.h332 hold_ctx->wounded = 1; in __ww_mutex_wound()
476 if (ctx->wounded) in __ww_mutex_check_kill()
H A Dmutex.c585 * Reset the wounded flag after a kill. No other process can in __mutex_lock_common()
590 ww_ctx->wounded = 0; in __mutex_lock_common()
791 * Reset the wounded flag after a kill. No other process can in ww_mutex_trylock()
796 ww_ctx->wounded = 0; in ww_mutex_trylock()
/linux/include/linux/
H A Dww_mutex.h59 unsigned short wounded; member
148 ctx->wounded = false; in ww_acquire_init()
/linux/Documentation/locking/
H A Dww-mutex-design.rst51 algorithm in that transactions are wounded by other transactions, and that
52 requires a reliable way to pick up the wounded condition and preempt the
351 The wounded status of the transaction is checked only when there is
353 situation, if the transaction is wounded, it backs off, clears the
354 wounded status and retries. A great benefit of implementing preemption in
355 this way is that the wounded transaction can identify a contending lock to