Searched refs:futex_lock_pi (Results 1 – 7 of 7) sorted by relevance
| /linux-5.10/tools/testing/selftests/futex/functional/ |
| D | futex_requeue_pi.c | 136 futex_lock_pi(&f2, NULL, 0, FUTEX_PRIVATE_FLAG); in waiterfn()
161 futex_lock_pi(&f2, NULL, 0, FUTEX_PRIVATE_FLAG); in broadcast_wakerfn()
212 futex_lock_pi(&f2, NULL, 0, FUTEX_PRIVATE_FLAG); in signal_wakerfn()
262 args->ret = futex_lock_pi(&f2, NULL, 0, FUTEX_PRIVATE_FLAG); in third_party_blocker()
|
| D | futex_requeue_pi_signal_restart.c | 167 futex_lock_pi(&f2, 0, 0, FUTEX_PRIVATE_FLAG); in main()
|
| /linux-5.10/tools/perf/bench/ |
| D | futex.h | 63 futex_lock_pi(u_int32_t *uaddr, struct timespec *timeout, int opflags) in futex_lock_pi() function
|
| D | futex-lock-pi.c | 94 ret = futex_lock_pi(w->futex, NULL, futex_flag); in workerfn()
|
| /linux-5.10/tools/testing/selftests/futex/include/ |
| D | futextest.h | 121 futex_lock_pi(futex_t *uaddr, struct timespec *timeout, int detect, in futex_lock_pi() function
|
| /linux-5.10/Documentation/locking/ |
| D | futex-requeue-pi.rst | 108 futex_lock_pi(), with some extra logic to check for the additional
|
| /linux-5.10/kernel/ |
| D | futex.c | 2772 static int futex_lock_pi(u32 __user *uaddr, unsigned int flags, in futex_lock_pi() function
3778 return futex_lock_pi(uaddr, flags, timeout, 0); in do_futex()
3782 return futex_lock_pi(uaddr, flags, NULL, 1); in do_futex()
|