Home
last modified time | relevance | path

Searched full:acquire (Results 1 – 25 of 2272) sorted by relevance

12345678910>>...91

/kernel/linux/linux-5.10/include/linux/
Dww_mutex.h98 * ww_acquire_init - initialize a w/w acquire context
99 * @ctx: w/w acquire context to initialize
102 * Initializes an context to acquire multiple mutexes of the given w/w class.
114 * Nesting of acquire contexts for _different_ w/w classes is possible, subject
117 * An acquire context must be released with ww_acquire_fini by the same task
147 * ww_acquire_done - marks the end of the acquire phase
148 * @ctx: the acquire context
150 * Marks the end of the acquire phase, any further w/w mutex lock calls using
154 * code and clearly designated the acquire phase from actually using the locked
168 * ww_acquire_fini - releases a w/w acquire context
[all …]
Datomic.h16 * - Acquire: Provides ACQUIRE semantics, _acquire suffix.
20 * For compound atomics performing both a load and a store, ACQUIRE
25 * See Documentation/memory-barriers.txt for ACQUIRE/RELEASE definitions.
35 * The idea here is to build acquire/release variants by adding explicit
/kernel/linux/linux-6.6/include/linux/
Dww_mutex.h109 * ww_acquire_init - initialize a w/w acquire context
110 * @ctx: w/w acquire context to initialize
113 * Initializes an context to acquire multiple mutexes of the given w/w class.
125 * Nesting of acquire contexts for _different_ w/w classes is possible, subject
128 * An acquire context must be released with ww_acquire_fini by the same task
158 * ww_acquire_done - marks the end of the acquire phase
159 * @ctx: the acquire context
161 * Marks the end of the acquire phase, any further w/w mutex lock calls using
165 * code and clearly designated the acquire phase from actually using the locked
179 * ww_acquire_fini - releases a w/w acquire context
[all …]
Datomic.h16 * - Acquire: Provides ACQUIRE semantics, _acquire suffix.
20 * For compound atomics performing both a load and a store, ACQUIRE
25 * See Documentation/memory-barriers.txt for ACQUIRE/RELEASE definitions.
35 * The idea here is to build acquire/release variants by adding explicit
/kernel/linux/linux-5.10/tools/memory-model/
Dlinux-kernel.def12 // Release Acquire and friends
14 smp_load_acquire(X) __load{acquire}(*X)
33 xchg_acquire(X,V) __xchg{acquire}(X,V)
36 cmpxchg_acquire(X,V,W) __cmpxchg{acquire}(X,V,W)
70 atomic_add_return_acquire(V,X) __atomic_op_return{acquire}(X,+,V)
74 atomic_fetch_add_acquire(V,X) __atomic_fetch_op{acquire}(X,+,V)
79 atomic_inc_return_acquire(X) __atomic_op_return{acquire}(X,+,1)
83 atomic_fetch_inc_acquire(X) __atomic_fetch_op{acquire}(X,+,1)
88 atomic_sub_return_acquire(V,X) __atomic_op_return{acquire}(X,-,V)
92 atomic_fetch_sub_acquire(V,X) __atomic_fetch_op{acquire}(X,-,V)
[all …]
/kernel/linux/linux-6.6/tools/memory-model/
Dlinux-kernel.def12 // Release Acquire and friends
14 smp_load_acquire(X) __load{acquire}(*X)
34 xchg_acquire(X,V) __xchg{acquire}(X,V)
37 cmpxchg_acquire(X,V,W) __cmpxchg{acquire}(X,V,W)
73 atomic_add_return_acquire(V,X) __atomic_op_return{acquire}(X,+,V)
77 atomic_fetch_add_acquire(V,X) __atomic_fetch_op{acquire}(X,+,V)
82 atomic_inc_return_acquire(X) __atomic_op_return{acquire}(X,+,1)
86 atomic_fetch_inc_acquire(X) __atomic_fetch_op{acquire}(X,+,1)
91 atomic_sub_return_acquire(V,X) __atomic_op_return{acquire}(X,-,V)
95 atomic_fetch_sub_acquire(V,X) __atomic_fetch_op{acquire}(X,-,V)
[all …]
/kernel/linux/linux-5.10/kernel/locking/
Dsemaphore.c23 * The ->count variable represents how many more tasks can acquire this
43 * down - acquire the semaphore
46 * Acquires the semaphore. If no more tasks are allowed to acquire the
67 * down_interruptible - acquire the semaphore unless interrupted
70 * Attempts to acquire the semaphore. If no more tasks are allowed to
71 * acquire the semaphore, calling this function will put the task to sleep.
92 * down_killable - acquire the semaphore unless killed
95 * Attempts to acquire the semaphore. If no more tasks are allowed to
96 * acquire the semaphore, calling this function will put the task to sleep.
118 * down_trylock - try to acquire the semaphore, without waiting
[all …]
Dmcs_spinlock.h9 * to acquire the lock spinning on a local variable.
26 * Using smp_cond_load_acquire() provides the acquire semantics
58 * In order to acquire the lock, the caller should declare a local node and
76 * observation of @node. And to provide the ACQUIRE ordering associated in mcs_spin_lock()
84 * However, since this thread can immediately acquire the lock in mcs_spin_lock()
99 * was used to acquire the lock.
Dqrwlock.c18 * queued_read_lock_slowpath - acquire read lock of a queue rwlock
30 * so spin with ACQUIRE semantics until the lock is available in queued_read_lock_slowpath()
45 * The ACQUIRE semantics of the following spinning code ensure in queued_read_lock_slowpath()
59 * queued_write_lock_slowpath - acquire write lock of a queue rwlock
69 /* Try to acquire the lock directly if no reader is present */ in queued_write_lock_slowpath()
/kernel/linux/linux-6.6/kernel/locking/
Dsemaphore.c23 * The ->count variable represents how many more tasks can acquire this
45 * down - acquire the semaphore
48 * Acquires the semaphore. If no more tasks are allowed to acquire the
70 * down_interruptible - acquire the semaphore unless interrupted
73 * Attempts to acquire the semaphore. If no more tasks are allowed to
74 * acquire the semaphore, calling this function will put the task to sleep.
96 * down_killable - acquire the semaphore unless killed
99 * Attempts to acquire the semaphore. If no more tasks are allowed to
100 * acquire the semaphore, calling this function will put the task to sleep.
123 * down_trylock - try to acquire the semaphore, without waiting
[all …]
Dmcs_spinlock.h9 * to acquire the lock spinning on a local variable.
26 * Using smp_cond_load_acquire() provides the acquire semantics
58 * In order to acquire the lock, the caller should declare a local node and
76 * observation of @node. And to provide the ACQUIRE ordering associated in mcs_spin_lock()
84 * However, since this thread can immediately acquire the lock in mcs_spin_lock()
99 * was used to acquire the lock.
Dqrwlock.c18 * queued_read_lock_slowpath - acquire read lock of a queued rwlock
30 * so spin with ACQUIRE semantics until the lock is available in queued_read_lock_slowpath()
47 * The ACQUIRE semantics of the following spinning code ensure in queued_read_lock_slowpath()
63 * queued_write_lock_slowpath - acquire write lock of a queued rwlock
75 /* Try to acquire the lock directly if no reader is present */ in queued_write_lock_slowpath()
/kernel/linux/linux-5.10/tools/memory-model/litmus-tests/
DREADME46 and load-acquire replaced with READ_ONCE().
49 Can a release-acquire chain order a prior store against
58 Does a release-acquire pair suffice for the load-buffering
64 and load-acquire replaced with READ_ONCE().
71 in one process, and use an acquire load followed by a pair of
76 acquire load followed by a pair of spin_is_locked() calls
87 As below, but with a release-acquire chain.
126 As below, but without the smp_wmb() and acquire load.
129 Can a smp_wmb(), instead of a release, and an acquire order
149 Is the ordering provided by a release-acquire chain sufficient
[all …]
/kernel/linux/linux-6.6/tools/memory-model/litmus-tests/
DREADME46 and load-acquire replaced with READ_ONCE().
49 Can a release-acquire chain order a prior store against
58 Does a release-acquire pair suffice for the load-buffering
64 and load-acquire replaced with READ_ONCE().
75 in one process, and use an acquire load followed by a pair of
80 acquire load followed by a pair of spin_is_locked() calls
91 As below, but with a release-acquire chain.
134 As below, but without the smp_wmb() and acquire load.
137 Can a smp_wmb(), instead of a release, and an acquire order
157 Is the ordering provided by a release-acquire chain sufficient
[all …]
/kernel/linux/linux-6.6/Documentation/sound/cards/
Dimg-spdif-in.rst19 * name='SPDIF In Multi Frequency Acquire',index=0
20 * name='SPDIF In Multi Frequency Acquire',index=1
21 * name='SPDIF In Multi Frequency Acquire',index=2
22 * name='SPDIF In Multi Frequency Acquire',index=3
47 * name='SPDIF In Lock Acquire Threshold',index=0
/kernel/linux/linux-5.10/Documentation/sound/cards/
Dimg-spdif-in.rst19 * name='SPDIF In Multi Frequency Acquire',index=0
20 * name='SPDIF In Multi Frequency Acquire',index=1
21 * name='SPDIF In Multi Frequency Acquire',index=2
22 * name='SPDIF In Multi Frequency Acquire',index=3
47 * name='SPDIF In Lock Acquire Threshold',index=0
/kernel/linux/linux-5.10/include/drm/
Ddrm_modeset_lock.h33 * @ww_ctx: base acquire ctx
39 * Each thread competing for a set of locks must use one acquire
143 * DRM_MODESET_LOCK_ALL_BEGIN - Helper to acquire modeset locks
145 * @ctx: local modeset acquire context, will be dereferenced
158 * Drivers can acquire additional modeset locks. If any lock acquisition
178 * @ctx: local modeset acquire context, will be dereferenced
189 * successfully acquire the locks, ret will be whatever your code sets it to. If
190 * there is a deadlock or other failure with acquire or backoff, ret will be set
/kernel/linux/linux-6.6/include/drm/
Ddrm_modeset_lock.h35 * @ww_ctx: base acquire ctx
42 * Each thread competing for a set of locks must use one acquire
152 * DRM_MODESET_LOCK_ALL_BEGIN - Helper to acquire modeset locks
154 * @ctx: local modeset acquire context, will be dereferenced
167 * Drivers can acquire additional modeset locks. If any lock acquisition
187 * @ctx: local modeset acquire context, will be dereferenced
198 * successfully acquire the locks, ret will be whatever your code sets it to. If
199 * there is a deadlock or other failure with acquire or backoff, ret will be set
/kernel/linux/linux-6.6/Documentation/driver-api/soundwire/
Dlocking.rst42 a. Acquire Message lock.
59 <-------------------------------+ a. Acquire Message lock
72 1. Acquire lock for Bus instance associated with Master 1.
76 a. Acquire Message lock.
93 <-------------------------------+ 1. Acquire bus lock
98 <-------------------------------+ a. Acquire Message lock
/kernel/linux/linux-5.10/Documentation/driver-api/soundwire/
Dlocking.rst42 a. Acquire Message lock.
59 <-------------------------------+ a. Acquire Message lock
72 1. Acquire lock for Bus instance associated with Master 1.
76 a. Acquire Message lock.
93 <-------------------------------+ 1. Acquire bus lock
98 <-------------------------------+ a. Acquire Message lock
/kernel/linux/linux-5.10/drivers/gpu/drm/
Ddrm_modeset_lock.c34 * to use &ww_mutex and acquire-contexts to avoid deadlocks. But because
36 * of extra utility/tracking out of our acquire-ctx. This is provided
190 * drm_modeset_acquire_init - initialize acquire context
191 * @ctx: the acquire context
211 * drm_modeset_acquire_fini - cleanup acquire context
212 * @ctx: the acquire context
222 * @ctx: the acquire context
224 * Drop all locks currently held against this acquire context.
284 * @ctx: the acquire context
323 * @ctx: acquire ctx
[all …]
/kernel/linux/linux-6.6/tools/memory-model/Documentation/
Dglossary.txt27 Acquire: With respect to a lock, acquiring that lock, for example,
31 An example special acquire operation is smp_load_acquire(),
33 acquire loads.
35 When an acquire load returns the value stored by a release store
36 to that same variable, (in other words, the acquire load "reads
38 store "happen before" any operations following that load acquire.
163 See also "Acquire" and "Release".
173 See also "Acquire" and "Relaxed".
/kernel/linux/linux-6.6/include/linux/atomic/
Datomic-instrumented.h37 * atomic_read_acquire() - atomic load with acquire ordering
40 * Atomically loads the value of @v with acquire ordering.
128 * atomic_add_return_acquire() - atomic add with acquire ordering
132 * Atomically updates @v to (@v + @i) with acquire ordering.
202 * atomic_fetch_add_acquire() - atomic add with acquire ordering
206 * Atomically updates @v to (@v + @i) with acquire ordering.
294 * atomic_sub_return_acquire() - atomic subtract with acquire ordering
298 * Atomically updates @v to (@v - @i) with acquire ordering.
368 * atomic_fetch_sub_acquire() - atomic subtract with acquire ordering
372 * Atomically updates @v to (@v - @i) with acquire ordering.
[all …]
Datomic-long.h45 * raw_atomic_long_read_acquire() - atomic load with acquire ordering
48 * Atomically loads the value of @v with acquire ordering.
149 * raw_atomic_long_add_return_acquire() - atomic add with acquire ordering
153 * Atomically updates @v to (@v + @i) with acquire ordering.
233 * raw_atomic_long_fetch_add_acquire() - atomic add with acquire ordering
237 * Atomically updates @v to (@v + @i) with acquire ordering.
338 * raw_atomic_long_sub_return_acquire() - atomic subtract with acquire ordering
342 * Atomically updates @v to (@v - @i) with acquire ordering.
422 * raw_atomic_long_fetch_sub_acquire() - atomic subtract with acquire ordering
426 * Atomically updates @v to (@v - @i) with acquire ordering.
[all …]
/kernel/linux/linux-6.6/Documentation/locking/
Dww-mutex-design.rst63 Acquire context: To ensure eventual forward progress it is important that a task
64 trying to acquire locks doesn't grab a new reservation id, but keeps the one it
66 acquire context. Furthermore the acquire context keeps track of debugging state
67 to catch w/w mutex interface abuse. An acquire context is representing a
71 w/w mutexes, since it is required to initialize the acquire context. The lock
74 Furthermore there are three different class of w/w lock acquire functions:
99 * Functions to only acquire a single w/w mutex, which results in the exact same
103 Again this is not strictly required. But often you only want to acquire a
104 single lock in which case it's pointless to set up an acquire context (and so
119 Three different ways to acquire locks within the same w/w class. Common
[all …]

12345678910>>...91