Searched refs:mutexes (Results 1 – 16 of 16) sorted by relevance
| /linux-4.1.27/kernel/locking/ |
| D | rtmutex-tester.c | 30 int mutexes[MAX_RT_TEST_MUTEXES]; member
37 static struct rt_mutex mutexes[MAX_RT_TEST_MUTEXES]; variable
65 td->mutexes[td->opdata] = 1; in handle_op()
71 if (td->mutexes[i] == 4) { in handle_op()
72 rt_mutex_unlock(&mutexes[i]); in handle_op()
73 td->mutexes[i] = 0; in handle_op()
95 td->mutexes[id] = 1; in handle_op()
97 rt_mutex_lock(&mutexes[id]); in handle_op()
99 td->mutexes[id] = 4; in handle_op()
108 td->mutexes[id] = 1; in handle_op()
[all …]
|
| /linux-4.1.27/Documentation/locking/ |
| D | rt-mutex.txt | 4 RT-mutexes with priority inheritance are used to support PI-futexes,
15 RT-mutexes extend the semantics of simple mutexes by the priority
26 mutexes which protect shared resources. Priority inheritance is not a
40 RT-mutexes are optimized for fastpath operations and have no internal
|
| D | mutex-design.txt | 6 What are mutexes?
9 In the Linux kernel, mutexes refer to a particular locking primitive
80 While formally kernel mutexes are sleepable locks, it is path (ii) that
98 - Held mutexes must not be reinitialized.
106 - Uses symbolic names of mutexes, whenever they are printed
152 When to use mutexes
155 Unless the strict semantics of mutexes are unsuitable and/or the critical
|
| D | ww-mutex-design.txt | 4 Please read mutex-design.txt first, as it applies to wait/wound mutexes too.
43 Compared to normal mutexes two additional concepts/objects show up in the lock
44 interface for w/w mutexes:
52 W/w class: In contrast to normal mutexes the lock class needs to be explicit for
53 w/w mutexes, since it is required to initialize the acquire context.
212 mutexes are a natural fit for such a case for two reasons:
310 increase in code size if wait/wound mutexes are not used.
315 would add overhead to all cases where normal mutexes are used, and
325 - Attempting to lock more mutexes after ww_acquire_done.
327 unlocking all mutexes.
[all …]
|
| D | rt-mutex-design.txt | 111 top pi waiter - The highest priority process waiting on one of the mutexes
121 The PI chain is a list of processes and mutexes that may cause priority
167 have multiple chains merge at mutexes. If we add another process G that is
187 on both mutexes and processes, I'll explain the plist. This is similar to
218 a list of all top waiters of the mutexes that are owned by the process.
220 blocked on mutexes owned by the process.
238 the nesting of mutexes. Let's look at the example where we have 3 mutexes,
302 Now since mutexes can be defined by user-land applications, we don't want a DOS
303 type of application that nests large amounts of mutexes to create a large
330 mutexes short.
[all …]
|
| D | lockdep-design.txt | 62 Unused mutexes cannot be part of the cause of an error.
|
| /linux-4.1.27/Documentation/ |
| D | pi-futex.txt | 63 locks (such as futex-based pthread mutexes) is priority inheritance:
78 mutexes involves no kernel work at all - they behave quite similarly to
81 futexes.) Userspace uses atomic ops to lock/unlock these mutexes without
114 possible anyway, due to existing ABI properties of pthread mutexes.]
|
| D | robust-futexes.txt | 38 There is a big conceptual problem with futex based mutexes though: it is
118 mechanism, which fully enables robust mutexes.
129 - no registration of individual locks is needed: robust mutexes dont
130 need any extra per-lock syscalls. Robust mutexes thus become a very
133 mutexes are just as fast.
154 [which it currently does for !pshared robust mutexes], and that took 256
|
| D | volatile-considered-harmful.txt | 19 safe (spinlocks, mutexes, memory barriers, etc.) are designed to prevent
|
| D | kprobes.txt | 556 Kprobes does not use mutexes or allocate memory except during
|
| D | memory-barriers.txt | 1772 (*) mutexes
|
| /linux-4.1.27/drivers/staging/media/davinci_vpfe/ |
| D | TODO | 17 - Check proper serialisation (through mutexes and spinlocks)
|
| /linux-4.1.27/fs/jffs2/ |
| D | README.Locking | 66 2. Never attempt to lock two file mutexes in one thread.
|
| /linux-4.1.27/Documentation/scheduler/ |
| D | completion.txt | 140 time, you probably don't want to call this with held mutexes.
|
| /linux-4.1.27/lib/ |
| D | Kconfig.debug | 905 menu "Lock Debugging (spinlocks, mutexes, etc...)"
915 bool "Built-in scriptable tester for rt-mutexes"
1003 NOTE: this feature can also be enabled for rwlocks, mutexes
1067 mutexes and rwsems.
|
| /linux-4.1.27/init/ |
| D | Kconfig | 1489 support for "fast userspace mutexes". The resulting kernel may not
|