| /linux-5.19.10/tools/testing/selftests/futex/functional/ ! |
| D | futex_wait.c | 20 void *futex; variable
42 if (futex_wait(futex, 0, &to, flags)) in waiterfn()
56 futex = &f_private; in main()
80 info("Calling private futex_wait on futex: %p\n", futex); in main()
86 info("Calling private futex_wake on futex: %p\n", futex); in main()
87 res = futex_wake(futex, 1, FUTEX_PRIVATE_FLAG); in main()
106 futex = shared_data; in main()
108 info("Calling shared (page anon) futex_wait on futex: %p\n", futex); in main()
114 info("Calling shared (page anon) futex_wake on futex: %p\n", futex); in main()
115 res = futex_wake(futex, 1, 0); in main()
[all …]
|
| /linux-5.19.10/tools/testing/selftests/futex/include/ ! |
| D | futextest.h | 70 #define futex(uaddr, op, val, timeout, uaddr2, val3, opflags) \ macro
80 return futex(uaddr, FUTEX_WAIT, val, timeout, NULL, 0, opflags); in futex_wait()
90 return futex(uaddr, FUTEX_WAKE, nr_wake, NULL, NULL, 0, opflags); in futex_wake()
101 return futex(uaddr, FUTEX_WAIT_BITSET, val, timeout, NULL, bitset, in futex_wait_bitset()
112 return futex(uaddr, FUTEX_WAKE_BITSET, nr_wake, NULL, NULL, bitset, in futex_wake_bitset()
124 return futex(uaddr, FUTEX_LOCK_PI, detect, timeout, NULL, 0, opflags); in futex_lock_pi()
133 return futex(uaddr, FUTEX_UNLOCK_PI, 0, NULL, NULL, 0, opflags); in futex_unlock_pi()
143 return futex(uaddr, FUTEX_WAKE_OP, nr_wake, nr_wake2, uaddr2, wake_op, in futex_wake_op()
159 return futex(uaddr, FUTEX_REQUEUE, nr_wake, nr_requeue, uaddr2, 0, in futex_requeue()
172 return futex(uaddr, FUTEX_CMP_REQUEUE, nr_wake, nr_requeue, uaddr2, in futex_cmp_requeue()
[all …]
|
| /linux-5.19.10/Documentation/locking/ ! |
| D | pi-futex.rst | 7 - in the user-space fastpath a PI-enabled futex involves no kernel work
64 locks (such as futex-based pthread mutexes) is priority inheritance:
80 normal futex-based locks: a 0 value means unlocked, and a value==TID
85 To handle the slowpath, we have added two new futex ops:
92 remaining work: if there is no futex-queue attached to the futex address
93 yet then the code looks up the task that owns the futex [it has put its
94 own TID into the futex value], and attaches a 'PI state' structure to
95 the futex-queue. The pi_state includes an rt-mutex, which is a PI-aware,
98 futex value. Then this task tries to lock the rt-mutex, on which it
100 futex value to its own TID and returns. Userspace has no other work to
[all …]
|
| D | index.rst | 21 pi-futex
22 futex-requeue-pi
26 robust-futex-ABI
|
| D | robust-futexes.rst | 15 A futex is in essence a user-space address, e.g. a 32-bit lock variable
20 creates a 'futex queue' internally, so that it can later on match up the
22 When the owner thread releases the futex, it notices (via the variable
25 taken and released the lock, the futex is again back to 'uncontended'
27 completely forgets that there ever was a futex at that address. This
42 There is a big conceptual problem with futex based mutexes though: it is
44 the kernel cannot help with the cleanup: if there is no 'futex queue'
51 is needed to release that futex based lock. This is one of the leading
76 are to be cleaned up, because a robust futex might have been registered
77 in another task, and the futex variable might have been simply mmap()-ed
[all …]
|
| D | robust-futex-ABI.rst | 2 The robust futex ABI
26 waiting on a particular futex, and waking up the next waiter on a
27 particular futex.
80 lock variable used by the futex mechanism, in conjunction with
82 waiting for a lock on a threads exit if that next thread used the futex
85 For each futex lock currently held by a thread, if it wants this
91 that lock using the futex mechanism.
118 existing futex mechanism to wait for, and wakeup, locks. The kernels
123 There may exist thousands of futex lock structures in a threads shared
128 A given futex lock structure in a user shared memory region may be held
[all …]
|
| D | futex-requeue-pi.rst | 5 Requeueing of tasks from a non-PI futex to a PI futex requires
56 user space already holding the PI futex. The glibc implementation
105 and pthread_cond_timedwait()) to block on the initial futex and wait
106 to be requeued to a PI-aware futex. The implementation is the
116 PI futex on behalf of the top waiter. If it can, this waiter is
118 nr_wake+nr_requeue tasks to the PI futex, calling
|
| /linux-5.19.10/tools/perf/bench/ ! |
| D | futex-lock-pi.c | 28 u_int32_t *futex; member
96 ret = futex_lock_pi(w->futex, NULL, futex_flag); in workerfn()
101 w->tid, w->futex, ret); in workerfn()
109 ret = futex_unlock_pi(w->futex, futex_flag); in workerfn()
112 w->tid, w->futex, ret); in workerfn()
138 worker[i].futex = calloc(1, sizeof(u_int32_t)); in create_threads()
139 if (!worker[i].futex) in create_threads()
142 worker[i].futex = &global_futex; in create_threads()
238 worker[i].tid, worker[i].futex, t); in bench_futex_lock_pi()
241 zfree(&worker[i].futex); in bench_futex_lock_pi()
|
| D | Build | 5 perf-y += futex-hash.o
6 perf-y += futex-wake.o
7 perf-y += futex-wake-parallel.o
8 perf-y += futex-requeue.o
9 perf-y += futex-lock-pi.o
|
| D | futex-hash.c | 44 u_int32_t *futex; member
91 ret = futex_wait(&w->futex[i], 1234, NULL, futex_flag); in workerfn()
183 worker[i].futex = calloc(params.nfutexes, sizeof(*worker[i].futex)); in bench_futex_hash()
184 if (!worker[i].futex) in bench_futex_hash()
233 worker[i].tid, &worker[i].futex[0], t); in bench_futex_hash()
236 worker[i].tid, &worker[i].futex[0], in bench_futex_hash()
237 &worker[i].futex[params.nfutexes-1], t); in bench_futex_hash()
240 zfree(&worker[i].futex); in bench_futex_hash()
|
| D | futex-wake-parallel.c | 48 static u_int32_t futex = 0; variable
85 waker->nwoken = futex_wake(&futex, nwakes, futex_flag); in waking_workerfn()
136 if (futex_wait(&futex, 0, NULL, futex_flag) != EINTR) in blocked_workerfn()
291 &futex, params.nwakes, nwakes); in bench_futex_wake_parallel()
|
| /linux-5.19.10/Documentation/userspace-api/ ! |
| D | futex2.rst | 9 futex, or fast user mutex, is a set of syscalls to allow userspace to create
14 futex2 is a followup version of the initial futex syscall, designed to overcome
37 and ``flags`` to specify the type (e.g. private) and size of futex.
59 - Some futex at the list was woken, returning the index of some waked futex.
61 An example of how to use the interface can be found at ``tools/testing/selftests/futex/functional/f…
71 Types of futex
74 A futex can be either private or shared. Private is used for processes that
75 shares the same memory space and the virtual address of the futex will be the
77 private futexes, it's necessary to specify ``FUTEX_PRIVATE_FLAG`` in the futex
79 have different virtual addresses for the same futex (using, for instance, a
[all …]
|
| /linux-5.19.10/kernel/futex/ ! |
| D | waitwake.c | 678 restart->futex.uaddr = uaddr; in futex_wait()
679 restart->futex.val = val; in futex_wait()
680 restart->futex.time = *abs_time; in futex_wait()
681 restart->futex.bitset = bitset; in futex_wait()
682 restart->futex.flags = flags | FLAGS_HAS_TIMEOUT; in futex_wait()
696 u32 __user *uaddr = restart->futex.uaddr; in futex_wait_restart()
699 if (restart->futex.flags & FLAGS_HAS_TIMEOUT) { in futex_wait_restart()
700 t = restart->futex.time; in futex_wait_restart()
705 return (long)futex_wait(uaddr, restart->futex.flags, in futex_wait_restart()
706 restart->futex.val, tp, restart->futex.bitset); in futex_wait_restart()
|
| /linux-5.19.10/Documentation/translations/zh_CN/locking/ ! |
| D | index.rst | 30 * pi-futex
31 * futex-requeue-pi
35 * robust-futex-ABI
|
| /linux-5.19.10/tools/testing/selftests/powerpc/benchmarks/ ! |
| D | futex_bench.c | 18 #define futex(A, B, C, D, E, F) syscall(__NR_futex, A, B, C, D, E, F) macro
29 futex(&addr, FUTEX_WAKE, 1, NULL, NULL, 0); in test_futex()
|
| /linux-5.19.10/tools/testing/selftests/futex/ ! |
| D | README | 3 Futex Test is intended to thoroughly test the Linux kernel futex system call
6 Functional tests shall test the documented behavior of the futex operation
54 based on the primary futex operation they test. Eventually this will become a
|
| /linux-5.19.10/tools/perf/scripts/python/bin/ ! |
| D | futex-contention-report | 4 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/futex-contention.py
|
| /linux-5.19.10/tools/testing/selftests/timens/ ! |
| D | .gitignore | 4 futex
|
| D | Makefile | 1 TEST_GEN_PROGS := timens timerfd timer clock_nanosleep procfs exec futex
|
| /linux-5.19.10/tools/perf/Documentation/ ! |
| D | perf-bench.txt | 61 'futex'::
206 SUITES FOR 'futex'
221 Suite for evaluating futex lock_pi calls.
|
| D | perf-lock.txt | 86 futex-default-S 1609 0 0
|
| /linux-5.19.10/include/linux/ ! |
| D | restart_block.h | 37 } futex; member
|
| /linux-5.19.10/include/asm-generic/ ! |
| D | Kbuild | 25 mandatory-y += futex.h
|
| /linux-5.19.10/tools/perf/arch/powerpc/entry/syscalls/ ! |
| D | syscall.tbl | 275 221 32 futex sys_futex_time32
276 221 64 futex sys_futex
277 221 spu futex sys_futex
|
| /linux-5.19.10/arch/powerpc/kernel/syscalls/ ! |
| D | syscall.tbl | 275 221 32 futex sys_futex_time32
276 221 64 futex sys_futex
277 221 spu futex sys_futex
|