| /linux/drivers/crypto/ccp/ |
| H A D | ccp-crypto-main.c | 95 struct ccp_crypto_cmd *held = NULL, *tmp; in ccp_crypto_cmd_complete() local
109 held = tmp; in ccp_crypto_cmd_complete()
137 return held; in ccp_crypto_cmd_complete()
143 struct ccp_crypto_cmd *held, *next, *backlog; in ccp_crypto_complete() local
162 held = ccp_crypto_cmd_complete(crypto_cmd, &backlog); in ccp_crypto_complete()
179 while (held) { in ccp_crypto_complete()
183 held->cmd->flags |= CCP_CMD_MAY_BACKLOG; in ccp_crypto_complete()
184 ret = ccp_enqueue_cmd(held->cmd); in ccp_crypto_complete()
189 ctx = crypto_tfm_ctx_dma(held->req->tfm); in ccp_crypto_complete()
191 ret = ctx->complete(held->req, ret); in ccp_crypto_complete()
[all …]
|
| /linux/Documentation/arch/s390/ |
| H A D | vfio-ap-locking.rst | 31 (matrix_dev->mdev_list). This lock must be held while reading from, writing to
47 lock must be held by the vfio_ap device driver while one or more AP adapters,
69 KVM guest. This lock must be held:
91 held in order to access the KVM pointer since it is set and cleared under the
95 resources, so only the matrix_dev->mdevs_lock needs to be held.
114 held in write mode when pqap_hook value is set, and in read mode when the
|
| /linux/Documentation/pcmcia/ |
| H A D | locking.rst | 26 be called with "skt_mutex" held::
43 be called with "ops_mutex" held::
52 called with "ops_mutex" held.
|
| /linux/Documentation/filesystems/nfs/ |
| H A D | pnfs.rst | 22 LAYOUTCOMMIT), and for each lseg held within.
33 layout driver type. The device ids are held in a RCU cache (struct
35 mount. The entries (struct nfs4_deviceid) themselves are held across
51 level cache. Its reference is held over the lifetime of the deviceid
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | era.rst | 56 <current era> <held metadata root | '-'>
64 held metadata root The location, in blocks, of the metadata root
65 that has been 'held' for userspace read
66 access. '-' indicates there is no held root
|
| /linux/Documentation/locking/ |
| H A D | robust-futex-ABI.rst | 9 futexes, for kernel assist of cleanup of held locks on task exit.
18 held robust_futexes begins, and
19 2) internal kernel code at exit, to handle any listed locks held
85 For each futex lock currently held by a thread, if it wants this
114 up locks held at the time of (a perhaps unexpectedly) exit.
121 still held by the departing thread, as described below.
125 lock structures for locks currently held by that thread should be on
128 A given futex lock structure in a user shared memory region may be held
133 When adding or removing a lock from its list of held locks, in order for
|
| H A D | lockstat.rst | 69 - shortest (non-0) time we ever held the lock
71 - longest time we ever held the lock
73 - total time this lock was held
75 - average time this lock was held
|
| H A D | rt-mutex.rst | 58 taskpointer 0 lock is held (fast release possible)
59 taskpointer 1 lock is held and has waiters [2]_
66 with ->wait_lock is held. To prevent any fast path cmpxchg to the lock,
|
| H A D | lockdep-design.rst | 46 - 'ever held in STATE context'
47 - 'ever held as readlock in STATE context'
48 - 'ever held with STATE enabled'
49 - 'ever held as readlock with STATE enabled'
170 any rule violation between the new lock and any of the held locks.
238 must be held: lockdep_assert_held*(&lock) and lockdep_*pin_lock(&lock).
241 particular lock is held at a certain time (and generate a WARN() otherwise).
329 held locks is maintained, and a lightweight 64-bit hash value is
523 , which means lockdep has seen L1 held before L2 held in the same context at runtime.
524 And in deadlock detection, we care whether we could get blocked on L2 with L1 held,
[all …]
|
| H A D | robust-futexes.rst | 46 then the kernel has no information to clean up after the held lock!
152 million (!) held locks, using the new method [on a 2GHz CPU]:
162 (1 million held locks are unheard of - we expect at most a handful of
163 locks to be held at a time. Nevertheless it's nice to know that this
191 If a futex is found to be held at exit time, the kernel sets the
|
| H A D | mutex-design.rst | 85 - A task may not exit with a mutex held.
86 - Memory areas where held locks reside must not be freed.
98 list of all locks held in the system, printout of them.
|
| /linux/Documentation/gpu/ |
| H A D | drm-vm-bind-locking.rst | 51 of dma_fences and a lock that needs to be held when adding
93 sleeping if the write side is held.
94 The write side is held by the core mm while calling mmu interval
131 held in relevant situations and also provides a means of making itself
173 // dma_resv to be held (it protects the gpu_vm_bo's list of
175 // dma_resv, it is already held at this point.
255 gpu_vms the object is bound to are typically not held. Only
256 the object's private dma_resv can be guaranteed to be held. If there
263 both the gpu_vm's dma_resv and the object's dma_resv is held, and the
323 Accessing the gpu_vm's lists without the dma_resv lock held
[all …]
|
| /linux/Documentation/leds/ |
| H A D | ledtrig-transient.rst | 12 features that require an on or off state to be held just once and then stay in
75 - state allows user to specify a transient state to be held for the specified
96 - transient state to be held. It has two values 0 or 1. 0 maps
98 held for the duration of the one shot timer and then the
128 held for the specified duration.
130 held for the specified duration.
|
| /linux/drivers/gpu/drm/i915/ |
| H A D | i915_vma_resource.c | 165 bool held = refcount_inc_not_zero(&vma_res->hold_count); in i915_vma_resource_hold() local
167 if (held) in i915_vma_resource_hold()
170 return held; in i915_vma_resource_hold()
|
| /linux/Documentation/RCU/ |
| H A D | lockdep-splat.rst | 31 3 locks held by scsi_scan_6/1552:
85 or with the ->queue_lock held. In particular, this would have suppressed
86 the above lockdep-RCU splat because ->queue_lock is held (see #2 in the
|
| H A D | UP.rst | 74 2. In some cases, the lock will be held across some kernel API,
78 with no locks held than to have to modify such APIs to allow
103 from a known environment in which no locks are held.
|
| /linux/fs/jffs2/ |
| H A D | README.Locking | 22 When writing new nodes, the alloc_sem must be held until the new nodes
65 any f->sem held.
68 3. Never lock a page cache page with f->sem held.
130 erase_completion_lock cannot be held, so an alternative, more
|
| /linux/tools/memory-model/litmus-tests/ |
| H A D | MP+polockonce+poacquiresilsil.litmus | 7 * to sense the lock-held state, ordered by acquire? Note that when the
|
| H A D | MP+polockmbonce+poacquiresilsil.litmus | 7 * to outside observers using spin_is_locked() to sense the lock-held
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-hid-prodikeys | 16 note held by the pc-midi driver.
|
| /linux/Documentation/bpf/ |
| H A D | map_lru_hash_update.dot | 8 label = "Key\n(locks held during operation)";
15 no_lock [shape=rectangle,label="no locks held"]
|
| /linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | cgroups.rst | 437 has processes attached, or is held alive by other subsystem-specific
551 (cgroup_mutex held by caller)
566 (cgroup_mutex held by caller)
576 (cgroup_mutex held by caller)
586 (cgroup_mutex held by caller)
595 (cgroup_mutex held by caller)
616 (cgroup_mutex held by caller)
630 (cgroup_mutex held by caller)
639 (cgroup_mutex held by caller)
658 (cgroup_mutex held by caller)
|
| /linux/LICENSES/deprecated/ |
| H A D | Zlib | 15 no event will the authors be held liable for any damages arising from the use
|
| /linux/Documentation/filesystems/ |
| H A D | directory-locking.rst | 161 lower than that of an already held lock.
165 held by the next thread in the cycle.
177 T1 is blocked on D1 which is held by T2
179 T2 is blocked on D2 which is held by T3
183 Tn is blocked on Dn which is held by T1.
|
| /linux/arch/arm/common/ |
| H A D | vlock.S | 57 ldrb r2, [r0, #VLOCK_OWNER_OFFSET] @ check whether lock is held
|