| /linux/tools/memory-model/Documentation/ |
| H A D | locking.txt | 10 CPU holding a given lock sees any changes previously seen or made by any
23 Any CPU holding a given lock sees any changes previously seen
26 Note that this statement is a bit stronger than "Any CPU holding a
28 previously holding this same lock". For example, consider the following
58 The converse to the basic rule also holds: Any CPU holding a given
148 In short, if you access a lock-protected variable without holding the
157 seen as ordered by CPUs not holding that lock. Consider this example:
189 Ordering can be extended to CPUs not holding the lock by careful use
259 CPU0() sets it to "1" while holding the lock, and CPU1() emulates the
269 "x" while holding the lock. And herd7 confirms this.
|
| H A D | recipes.txt | 51 holding the update-side lock, reads from that variable
72 stronger than "Any CPU holding a given lock sees all changes made by any
73 CPU during the time that CPU was holding this same lock". For example,
130 locking will be seen as ordered by CPUs not holding that lock.
163 Ordering can be extended to CPUs not holding the lock by careful use
|
| /linux/tools/memory-model/litmus-tests/ |
| H A D | Z6.0+pooncelock+pooncelock+pombonce.litmus | 7 * processes each while holding a given lock will not necessarily be
8 * seen as ordered by a third process not holding that lock.
|
| H A D | MP+polocks.litmus | 8 * In other words, when holding a given lock (or indeed after releasing a
10 * CPUs made while previously holding that lock, it is also guaranteed
|
| H A D | MP+porevlocks.litmus | 8 * In other words, when holding a given lock (or indeed after releasing a
10 * CPUs made while previously holding that lock, it is also guaranteed to
|
| H A D | Z6.0+pooncelock+poonceLock+pombonce.litmus | 9 * by CPUs not holding that lock.
|
| /linux/fs/jffs2/ |
| H A D | README.Locking | 25 nodes to an inode may obsolete old ones, and by holding the alloc_sem
35 if the wbuf is currently holding any data is permitted, though.
87 may remove _obsolete_ nodes from the list while holding only the
88 erase_completion_lock. So you can walk the list only while holding the
90 long as the pointer you're holding is to a _valid_ node, not an
162 when updating such a object is necessary under holding read semaphore.
164 xdatum at first. But it retries this process with holding write-semaphore
|
| /linux/fs/btrfs/ |
| H A D | volumes.h | 426 int holding; member
867 ASSERT(fs_devices->holding >= 0); in btrfs_fs_devices_inc_holding()
868 fs_devices->holding++; in btrfs_fs_devices_inc_holding()
874 ASSERT(fs_devices->holding > 0); in btrfs_fs_devices_dec_holding()
875 fs_devices->holding--; in btrfs_fs_devices_dec_holding()
|
| /linux/Documentation/locking/ |
| H A D | robust-futex-ABI.rst | 11 The interesting data as to what futexes a thread is holding is kept on a
65 of the thread holding the lock in the bottom 30 bits. See further
88 specified 'offset'. Should a thread die while holding any such locks,
130 thread currently holding such a lock, if any, is marked with the threads
169 lock owner died holding the lock.
|
| H A D | ww-mutex-design.rst | 39 If the transaction holding the lock is younger, the locking transaction waits.
40 If the transaction holding the lock is older, the locking transaction backs off
43 If the transaction holding the lock is younger, the locking transaction
44 wounds the transaction holding the lock, requesting it to die.
45 If the transaction holding the lock is older, it waits for the other
237 and edges can only be changed when holding the locks of all involved nodes. w/w
|
| H A D | robust-futexes.rst | 30 "Robustness" is about dealing with crashes while holding a lock: if a
31 process exits prematurely while holding a pthread_mutex_t lock that is
32 also shared with some other process (e.g. yum segfaults while holding a
90 robust locks that userspace is holding (maintained by glibc) - which
|
| H A D | locktypes.rst | 151 readers, a preempted low-priority reader will continue holding its lock,
273 - Tasks holding a spinlock_t do not migrate. Non-PREEMPT_RT kernels
335 readers, a preempted low-priority reader will continue holding its lock,
506 while holding normal non-raw spinlocks because they do not disable
547 per-CPU spinlock_t means that they cannot be acquired while holding a raw
|
| /linux/sound/aoa/fabrics/ |
| H A D | Kconfig | 8 Audio driver, the module holding it all together
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | era.rst | 24 metadata dev fast device holding the persistent metadata
25 origin dev device holding data blocks that may change
|
| /linux/Documentation/core-api/ |
| H A D | kref.rst | 72 holding a valid pointer, it is safe to do this without
76 without already holding a valid pointer, it must serialize access
129 already holding a pointer.
173 holding a valid pointer. You must add a mutex (or some other lock).
|
| /linux/Documentation/devicetree/bindings/input/ |
| H A D | input-reset.txt | 5 sysrq driver. Upon holding the keys for a specified amount of time (if
|
| /linux/Documentation/devicetree/bindings/dma/ |
| H A D | moxa,moxart-dma.txt | 11 - #dma-cells : Should be 1, a single cell holding a line request number
|
| /linux/Documentation/kernel-hacking/ |
| H A D | locking.rst | 111 spinlock, but you may block holding a mutex. If you can't lock a mutex,
304 - Avoid holding spinlock for more than 5 lines of code and across any
357 lock when some other thread is holding the lock. You should acquire the
405 /* Must be holding cache_lock */
418 /* Must be holding cache_lock */
427 /* Must be holding cache_lock */
645 /* Must be holding cache_lock */
691 now sleep holding the object (eg. to copy_to_user() to
760 /* Must be holding cache_lock */
1020 going to be waiting while someone else is holding a lock. Second is the
[all …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | streaming-par.rst | 30 contains a union holding separate parameters for input and output
|
| /linux/Documentation/networking/ |
| H A D | netdevices.rst | 268 called without holding netif_tx_lock. In this case the driver
348 ``ndos`` are called without holding the instance lock for most drivers.
369 All net shaper callbacks are invoked while holding the netdev instance
377 All queue management callbacks are invoked while holding the netdev instance
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-hid-ntrig | 19 number of empty frames. By holding off on deactivation for a few
|
| /linux/Documentation/filesystems/ |
| H A D | directory-locking.rst | 89 dcache trees. Lookup is already holding the parent locked. If alias is
102 all we change is the view in dcache. Moreover, holding a directory locked
103 exclusive prevents such changes involving its children and holding the
245 rename holding the lock on parent of source and trying to lock its
|
| /linux/Documentation/security/ |
| H A D | sak.rst | 51 incorrectly holding /dev/console open. Be sure to complain to your
|
| /linux/Documentation/driver-api/ |
| H A D | io-mapping.rst | 74 If you need to sleep while holding a mapping, you can use the regular
|
| /linux/Documentation/power/ |
| H A D | swsusp-and-swap-files.rst | 18 filesystem holding the swap file to be mounted, and if this filesystem is
|