| /Linux-v5.4/drivers/crypto/ccp/ |
| D | ccp-crypto-main.c | 99 struct ccp_crypto_cmd *held = NULL, *tmp; in ccp_crypto_cmd_complete() local
113 held = tmp; in ccp_crypto_cmd_complete()
141 return held; in ccp_crypto_cmd_complete()
147 struct ccp_crypto_cmd *held, *next, *backlog; in ccp_crypto_complete() local
166 held = ccp_crypto_cmd_complete(crypto_cmd, &backlog); in ccp_crypto_complete()
183 while (held) { in ccp_crypto_complete()
187 held->cmd->flags |= CCP_CMD_MAY_BACKLOG; in ccp_crypto_complete()
188 ret = ccp_enqueue_cmd(held->cmd); in ccp_crypto_complete()
193 ctx = crypto_tfm_ctx(held->req->tfm); in ccp_crypto_complete()
195 ret = ctx->complete(held->req, ret); in ccp_crypto_complete()
[all …]
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-bus-coresight-devices-tmc | 21 Description: (R) Shows the value held by the TMC status register. The value
28 Description: (R) Shows the value held by the TMC RAM Read Pointer register
37 Description: (R) Shows the value held by the TMC RAM Write Pointer register
53 Description: (R) Shows the value held by the TMC Control register. The value
60 Description: (R) Shows the value held by the TMC Formatter and Flush Status
68 Description: (R) Shows the value held by the TMC Formatter and Flush Control
76 Description: (R) Shows the value held by the TMC Mode register, which
|
| D | sysfs-bus-coresight-devices-etb10 | 30 Description: (R) Shows the value held by the ETB status register. The value
37 Description: (R) Shows the value held by the ETB RAM Read Pointer register
46 Description: (R) Shows the value held by the ETB RAM Write Pointer register
62 Description: (R) Shows the value held by the ETB Control register. The value
69 Description: (R) Shows the value held by the ETB Formatter and Flush Status
77 Description: (R) Shows the value held by the ETB Formatter and Flush Control
|
| D | sysfs-driver-hid-prodikeys | 16 note held by the pc-midi driver.
|
| /Linux-v5.4/Documentation/dev-tools/ |
| D | sparse.rst | 59 locking. These annotations tell sparse when a lock is held, with
62 __must_hold - The specified lock is held on function entry and exit.
64 __acquires - The specified lock is held on function exit, but not entry.
66 __releases - The specified lock is held on function entry, but not exit.
68 If the function enters and exits without the lock held, acquiring and
|
| /Linux-v5.4/Documentation/pcmcia/ |
| D | locking.rst | 26 be called with "skt_mutex" held::
43 be called with "ops_mutex" held::
52 called with "ops_mutex" held.
|
| /Linux-v5.4/Documentation/admin-guide/device-mapper/ |
| 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-v5.4/Documentation/filesystems/nfs/ |
| D | pnfs.txt | 20 LAYOUTCOMMIT), and for each lseg held within.
30 layout driver type. The device ids are held in a RCU cache (struct
32 mount. The entries (struct nfs4_deviceid) themselves are held across
47 level cache. Its reference is held over the lifetime of the deviceid
|
| /Linux-v5.4/Documentation/ |
| D | robust-futex-ABI.txt | 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
|
| D | robust-futexes.txt | 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
|
| /Linux-v5.4/Documentation/leds/ |
| D | ledtrig-transient.rst | 12 features that require an on or off state to be held just once and then stay in
81 - state allows user to specify a transient state to be held for the specified
102 - transient state to be held. It has two values 0 or 1. 0 maps
104 held for the duration of the one shot timer and then the
134 held for the specified duration.
136 held for the specified duration.
|
| /Linux-v5.4/Documentation/locking/ |
| 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
|
| 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,
|
| D | lockdep-design.rst | 45 - 'ever held in STATE context'
46 - 'ever held as readlock in STATE context'
47 - 'ever held with STATE enabled'
48 - 'ever held as readlock with STATE enabled'
167 any rule violation between the new lock and any of the held locks.
235 must be held: lockdep_assert_held*(&lock) and lockdep_*pin_lock(&lock).
238 particular lock is held at a certain time (and generate a WARN() otherwise).
326 held locks is maintained, and a lightweight 64-bit hash value is
|
| 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-v5.4/Documentation/devicetree/bindings/remoteproc/ |
| D | qcom,adsp.txt | 51 held on behalf of the booting Hexagon core
61 Definition: reference to the regulator to be held on behalf of the
67 Definition: reference to the px regulator to be held on behalf of the
|
| D | qcom,q6v5.txt | 103 Definition: reference to the regulators to be held on behalf of the
114 Definition: reference to the regulators to be held on behalf of the
122 Definition: reference to the regulators to be held on behalf of the
|
| D | qcom,wcnss-pil.txt | 42 Definition: reference to the regulators to be held on behalf of the
90 Definition: reference to the regulators to be held on behalf of the
|
| /Linux-v5.4/Documentation/RCU/ |
| D | lockdep-splat.txt | 26 3 locks held by scsi_scan_6/1552:
80 or with the ->queue_lock held. In particular, this would have suppressed
81 the above lockdep-RCU splat because ->queue_lock is held (see #2 in the
|
| D | UP.rst | 73 2. In some cases, the lock will be held across some kernel API,
77 with no locks held than to have to modify such APIs to allow
94 from a known environment in which no locks are held.
|
| /Linux-v5.4/tools/memory-model/litmus-tests/ |
| D | MP+polockonce+poacquiresilsil.litmus | 7 * to sense the lock-held state, ordered by acquire? Note that when the
|
| D | MP+polockmbonce+poacquiresilsil.litmus | 7 * to outside observers using spin_is_locked() to sense the lock-held
|
| /Linux-v5.4/Documentation/devicetree/bindings/fpga/ |
| D | lattice-ice40-fpga-mgr.txt | 9 that unless the GPIO is held low during startup, the
|
| /Linux-v5.4/fs/jffs2/ |
| 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-v5.4/Documentation/virt/kvm/devices/ |
| D | vfio.txt | 12 VFIO-group is held by KVM.
|
