Lines Matching refs:rtmutex
7 * 1) Lock rtmutex
15 * 3) Unlock rtmutex, to release blocked readers
22 * 5) unlock rtmutex, goto 1)
30 * RT tasks (think mmap_sem), are subject to the rtmutex priority/DL
35 * to block on the rtmutex, but the rtmutex would have to be proxy locked
71 struct rt_mutex_base *rtm = &rwb->rtmutex;
78 * Call into the slow lock path with the rtmutex->wait_lock
116 * On success the rtmutex is held, so there can't be a writer
118 * rtmutex again.
120 * rtmutex->wait_lock has to be unlocked in any case of course.
147 struct rt_mutex_base *rtm = &rwb->rtmutex;
153 * Wake the writer, i.e. the rtmutex owner. It might release the
154 * rtmutex concurrently in the fast path (due to a signal), but to
184 struct rt_mutex_base *rtm = &rwb->rtmutex;
197 struct rt_mutex_base *rtm = &rwb->rtmutex;
206 struct rt_mutex_base *rtm = &rwb->rtmutex;
217 lockdep_assert_held(&rwb->rtmutex.wait_lock);
234 struct rt_mutex_base *rtm = &rwb->rtmutex;
237 /* Take the rtmutex as a first step */
282 struct rt_mutex_base *rtm = &rwb->rtmutex;