| /linux-6.12.1/drivers/scsi/isci/ |
| D | isci.h | 140 * because the io request specified more data than is returned by the
178 * This member indicates the calling function failed, because the state
184 * This member indicates the calling function failed, because there is
190 * This member indicates the calling function failed, because the
196 * This member indicates the calling function failed, because the
202 * This member indicates the calling function failed, because the
208 * This member indicates the calling function failed, because the
214 * This member indicates the calling function failed, because the
221 * This member indicates the calling function failed, because the
227 * This member indicates the calling function failed, because the
[all …]
|
| /linux-6.12.1/tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/ |
| D | other.json | 9 …"PublicDescription": "This event counts every cycle that no operation was committed because the ol…
12 …"BriefDescription": "This event counts every cycle that no operation was committed because the old…
15 …"PublicDescription": "This event counts every cycle that no instruction was committed because the …
18 …"BriefDescription": "This event counts every cycle that no instruction was committed because the o…
21 …"PublicDescription": "This event counts every cycle that no instruction was committed because the …
24 …"BriefDescription": "This event counts every cycle that no instruction was committed because the o…
27 …"PublicDescription": "This event counts every cycle that no instruction was committed because the …
30 …"BriefDescription": "This event counts every cycle that no instruction was committed because the o…
33 …"PublicDescription": "This event counts every cycle that no instruction was committed because the …
36 …"BriefDescription": "This event counts every cycle that no instruction was committed because the o…
[all …]
|
| /linux-6.12.1/tools/perf/pmu-events/arch/s390/cf_z15/ |
| D | crypto6.json | 21 …m-number-generation functions that are issued by the CPU and are blocked because the DEA/AES/SHA c…
28 …ocked for the pseudorandom-number-generation functions issued by the CPU because the DEA/AES/SHA c…
49 …l number of the SHA functions that are issued by the CPU and are blocked because the SHA coprocess…
56 …tal number of CPU cycles blocked for the SHA functions issued by the CPU because the SHA coprocess…
77 …l number of the DEA functions that are issued by the CPU and are blocked because the DEA/AES copro…
84 …tal number of CPU cycles blocked for the DEA functions issued by the CPU because the DEA/AES copro…
105 …l number of the AES functions that are issued by the CPU and are blocked because the DEA/AES copro…
112 …tal number of CPU cycles blocked for the AES functions issued by the CPU because the DEA/AES copro…
133 … cryptography (ECC) functions that are issued by the CPU and are blocked because the ECC coprocess…
140 …ed for the elliptic-curve cryptography (ECC) functions issued by the CPU because the ECC coprocess…
|
| /linux-6.12.1/tools/perf/pmu-events/arch/s390/cf_z16/ |
| D | crypto6.json | 21 …m-number-generation functions that are issued by the CPU and are blocked because the DEA/AES/SHA c…
28 …ocked for the pseudorandom-number-generation functions issued by the CPU because the DEA/AES/SHA c…
49 …l number of the SHA functions that are issued by the CPU and are blocked because the SHA coprocess…
56 …tal number of CPU cycles blocked for the SHA functions issued by the CPU because the SHA coprocess…
77 …l number of the DEA functions that are issued by the CPU and are blocked because the DEA/AES copro…
84 …tal number of CPU cycles blocked for the DEA functions issued by the CPU because the DEA/AES copro…
105 …l number of the AES functions that are issued by the CPU and are blocked because the DEA/AES copro…
112 …tal number of CPU cycles blocked for the AES functions issued by the CPU because the DEA/AES copro…
133 … cryptography (ECC) functions that are issued by the CPU and are blocked because the ECC coprocess…
140 …ed for the elliptic-curve cryptography (ECC) functions issued by the CPU because the ECC coprocess…
|
| /linux-6.12.1/tools/perf/pmu-events/arch/powerpc/power9/ |
| D | metrics.json | 44 …"BriefDescription": "Finish stall because the NTF instruction was routed to the crypto execution p…
50 …"BriefDescription": "Finish stall because the NTF instruction was a load that missed the L1 and wa…
56 …"BriefDescription": "Finish stall because the NTF instruction was a multi-cycle instruction issued…
68 …"BriefDescription": "Finish stall because the NTF instruction was issued to the Decimal Floating P…
134 …"BriefDescription": "Finish stall because the NTF instruction was a scalar instruction issued to t…
140 …"BriefDescription": "Finish stall because the NTF instruction was a scalar multi-cycle instruction…
146 …"BriefDescription": "Finish stall because the NTF instruction is an EIEIO waiting for response fro…
152 …"BriefDescription": "Finish stall because the next to finish instruction suffered an ERAT miss and…
163 …"BriefDescription": "Finish stall because the NTF instruction was a load or store that suffered a …
169 …"BriefDescription": "Cycles in which the NTC instruction is not allowed to complete because it was…
[all …]
|
| D | frontend.json | 20 …"BriefDescription": "The NTC instruction is being held at dispatch because there are no slots in t…
25 …"BriefDescription": "Finish stall because the NTF instruction was a load or store that was held in…
70 …"BriefDescription": "Finish stall because the NTF instruction was a store waiting for a slot in th…
80 …"BriefDescription": "Completion stall of one cycle because the LSU requested to flush the next iop…
85 …"BriefDescription": "Finish stall because the NTF instruction was a stcx waiting for response from…
100 …"BriefDescription": "Completion stall because the ISU is updating the register and notifying the E…
140 …"BriefDescription": "Finish stall because the NTF instruction was a mfspr instruction targeting an…
165 …"BriefDescription": "Finish stall because the NTF instruction was a store with all its dependencie…
255 …"BriefDescription": "Finish stall because the NTF instruction was a tend instruction awaiting resp…
290 …"BriefDescription": "Finish stall because the next to finish instruction was a store waiting on da…
[all …]
|
| D | cache.json | 10 …"BriefDescription": "Cycles in which the NTC instruction is not allowed to complete because any of…
35 …"Finish stall because the NTF instruction was a load that missed in the L1 and the LMQ was unable …
45 …"BriefDescription": "Finish stall because the NTF instruction was a load instruction with all its …
90 …"BriefDescription": "Finish stall because the NTF instruction was a load that hit on an older stor…
105 … "BriefDescription": "Finish stall because the NTF instruction was a larx waiting to be satisfied"
|
| /linux-6.12.1/tools/perf/pmu-events/arch/s390/cf_z13/ |
| D | crypto.json | 21 …m-number-generation functions that are issued by the CPU and are blocked because the DEA/AES/SHA c…
28 …ocked for the pseudorandom-number-generation functions issued by the CPU because the DEA/AES/SHA c…
49 …l number of the SHA functions that are issued by the CPU and are blocked because the SHA coprocess…
56 …tal number of CPU cycles blocked for the SHA functions issued by the CPU because the SHA coprocess…
77 …l number of the DEA functions that are issued by the CPU and are blocked because the DEA/AES copro…
84 …tal number of CPU cycles blocked for the DEA functions issued by the CPU because the DEA/AES copro…
105 …l number of the AES functions that are issued by the CPU and are blocked because the DEA/AES copro…
112 …tal number of CPU cycles blocked for the AES functions issued by the CPU because the DEA/AES copro…
|
| /linux-6.12.1/tools/perf/pmu-events/arch/s390/cf_z10/ |
| D | crypto.json | 21 …m-number-generation functions that are issued by the CPU and are blocked because the DEA/AES/SHA c…
28 …ocked for the pseudorandom-number-generation functions issued by the CPU because the DEA/AES/SHA c…
49 …l number of the SHA functions that are issued by the CPU and are blocked because the SHA coprocess…
56 …tal number of CPU cycles blocked for the SHA functions issued by the CPU because the SHA coprocess…
77 …l number of the DEA functions that are issued by the CPU and are blocked because the DEA/AES copro…
84 …tal number of CPU cycles blocked for the DEA functions issued by the CPU because the DEA/AES copro…
105 …l number of the AES functions that are issued by the CPU and are blocked because the DEA/AES copro…
112 …tal number of CPU cycles blocked for the AES functions issued by the CPU because the DEA/AES copro…
|
| /linux-6.12.1/tools/perf/pmu-events/arch/s390/cf_z14/ |
| D | crypto.json | 21 …m-number-generation functions that are issued by the CPU and are blocked because the DEA/AES/SHA c…
28 …ocked for the pseudorandom-number-generation functions issued by the CPU because the DEA/AES/SHA c…
49 …l number of the SHA functions that are issued by the CPU and are blocked because the SHA coprocess…
56 …tal number of CPU cycles blocked for the SHA functions issued by the CPU because the SHA coprocess…
77 …l number of the DEA functions that are issued by the CPU and are blocked because the DEA/AES copro…
84 …tal number of CPU cycles blocked for the DEA functions issued by the CPU because the DEA/AES copro…
105 …l number of the AES functions that are issued by the CPU and are blocked because the DEA/AES copro…
112 …tal number of CPU cycles blocked for the AES functions issued by the CPU because the DEA/AES copro…
|
| /linux-6.12.1/tools/perf/pmu-events/arch/s390/cf_z196/ |
| D | crypto.json | 21 …m-number-generation functions that are issued by the CPU and are blocked because the DEA/AES/SHA c…
28 …ocked for the pseudorandom-number-generation functions issued by the CPU because the DEA/AES/SHA c…
49 …l number of the SHA functions that are issued by the CPU and are blocked because the SHA coprocess…
56 …tal number of CPU cycles blocked for the SHA functions issued by the CPU because the SHA coprocess…
77 …l number of the DEA functions that are issued by the CPU and are blocked because the DEA/AES copro…
84 …tal number of CPU cycles blocked for the DEA functions issued by the CPU because the DEA/AES copro…
105 …l number of the AES functions that are issued by the CPU and are blocked because the DEA/AES copro…
112 …tal number of CPU cycles blocked for the AES functions issued by the CPU because the DEA/AES copro…
|
| /linux-6.12.1/tools/perf/pmu-events/arch/s390/cf_zec12/ |
| D | crypto.json | 21 …m-number-generation functions that are issued by the CPU and are blocked because the DEA/AES/SHA c…
28 …ocked for the pseudorandom-number-generation functions issued by the CPU because the DEA/AES/SHA c…
49 …l number of the SHA functions that are issued by the CPU and are blocked because the SHA coprocess…
56 …tal number of CPU cycles blocked for the SHA functions issued by the CPU because the SHA coprocess…
77 …l number of the DEA functions that are issued by the CPU and are blocked because the DEA/AES copro…
84 …tal number of CPU cycles blocked for the DEA functions issued by the CPU because the DEA/AES copro…
105 …l number of the AES functions that are issued by the CPU and are blocked because the DEA/AES copro…
112 …tal number of CPU cycles blocked for the AES functions issued by the CPU because the DEA/AES copro…
|
| /linux-6.12.1/tools/perf/pmu-events/arch/x86/amdzen5/ |
| D | pipeline.json | 10 …"BriefDescription": "Percentage of dispatch slots that remained unused because the frontend did no…
24 …"BriefDescription": "Percentage of dispatch slots that remained unused because of backend stalls.",
31 …"BriefDescription": "Percentage of dispatch slots that remained unused because the other thread wa…
45 …"BriefDescription": "Percentage of dispatch slots that remained unused because of a latency bottle…
52 …"BriefDescription": "Percentage of dispatch slots that remained unused because of a bandwidth bott…
73 …"BriefDescription": "Percentage of dispatch slots that remained unused because of stalls due to th…
80 …"BriefDescription": "Percentage of dispatch slots that remained unused because of stalls not relat…
|
| /linux-6.12.1/tools/perf/pmu-events/arch/x86/amdzen4/ |
| D | pipeline.json | 9 …"BriefDescription": "Fraction of dispatch slots that remained unused because the frontend did not …
23 … "BriefDescription": "Fraction of dispatch slots that remained unused because of backend stalls.",
30 …"BriefDescription": "Fraction of dispatch slots that remained unused because the other thread was …
44 …"BriefDescription": "Fraction of dispatch slots that remained unused because of a latency bottlene…
51 …"BriefDescription": "Fraction of dispatch slots that remained unused because of a bandwidth bottle…
72 …"BriefDescription": "Fraction of dispatch slots that remained unused because of stalls due to the …
79 …"BriefDescription": "Fraction of dispatch slots that remained unused because of stalls not related…
|
| /linux-6.12.1/Documentation/networking/devlink/ |
| D | devlink-trap.rst | 100 * ``control``: Trapped packets were trapped by the device because these are
136 - Traps incoming packets that the device decided to drop because of a
171 - Traps packets that the device decided to drop because they could not be
175 - Traps packets that the device decided to drop because they need to
179 - Traps packets that the device decided to drop because they need to be
184 - Traps packets that the device decided to drop because they need to be
189 - Traps packets that the device decided to drop because they need to be
193 - Traps packets that the device decided to drop because they need to be
197 - Traps packets that the device decided to drop because they need to be
202 - Traps packets that the device decided to drop because they need to be
[all …]
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-bus-event_source-devices-hv_gpci | 110 * "-EIO" : Can't retrieve system information because of invalid buffer length/invalid address
111 or because of some hardware error. Refer to getPerfCountInfo documentation for
142 * "-EIO" : Can't retrieve system information because of invalid buffer length/invalid address
143 or because of some hardware error. Refer to getPerfCountInfo documentation for
174 * "-EIO" : Can't retrieve system information because of invalid buffer length/invalid address
175 or because of some hardware error. Refer to getPerfCountInfo documentation for
206 * "-EIO" : Can't retrieve system information because of invalid buffer length/invalid address
207 or because of some hardware error. Refer to getPerfCountInfo documentation for
238 * "-EIO" : Can't retrieve system information because of invalid buffer length/invalid address
239 or because of some hardware error. Refer to getPerfCountInfo documentation for
|
| /linux-6.12.1/tools/perf/pmu-events/arch/powerpc/power10/ |
| D | pipeline.json | 45 …"BriefDescription": "Cycles when dispatch was stalled for this thread because the MMU was handling…
75 …cles in which the next-to-complete (NTC) instruction is held at dispatch because of power manageme…
80 …cles in which the next-to-complete (NTC) instruction is held at dispatch because the STF mapper/SR…
110 …"BriefDescription": "Cycles dispatch is held because of a synchronizing instruction that requires …
220 …"BriefDescription": "Cycles when dispatch was stalled for this thread because Fetch was being held…
225 …cles in which the next-to-complete (NTC) instruction is held at dispatch because the XVFC mapper/S…
260 …"BriefDescription": "Cycles dispatch is held because the STF mapper/SRB was full. Includes GPR (co…
265 …"BriefDescription": "Cycles when dispatch was stalled because of a flush that happened to an instr…
315 …which the oldest instruction in the pipeline was not allowed to complete because it was interrupte…
345 …cles in which the next-to-complete (NTC) instruction is held at dispatch because the mapper/SRB wa…
[all …]
|
| /linux-6.12.1/tools/tracing/rtla/src/ |
| D | osnoise.h | 30 /* -1 as init value because 0 is disabled */
34 /* -1 as init value because 0 is disabled */
38 /* -1 as init value because 0 is disabled */
42 /* -1 as init value because 0 is off */
46 /* -1 as init value because 0 is off */
|
| /linux-6.12.1/tools/perf/pmu-events/arch/arm64/arm/cortex-a53/ |
| D | pipeline.json | 5 …"BriefDescription": "Data Write operation that stalls the pipeline because the store buffer is ful…
10 …"BriefDescription": "Cycles that the DPU IQ is empty and that is not because of a recent micro-TLB…
45 "BriefDescription": "Cycles there is a stall in the Wr stage because of a load miss"
50 "BriefDescription": "Cycles there is a stall in the Wr stage because of a store"
|
| /linux-6.12.1/Documentation/locking/ |
| D | locktypes.rst | 125 PREEMPT_RT does not change the semaphore implementation because counting
150 Because an rw_semaphore writer cannot grant its priority to multiple
152 thus starving even high-priority writers. In contrast, because readers
274 to RUNNING, but that does not work here because the task must remain
313 - Because an rwlock_t writer cannot grant its priority to multiple
315 thus starving even high-priority writers. In contrast, because readers
338 On a PREEMPT_RT kernel this code sequence breaks because local_lock_irq()
372 because local_lock_irqsave() does not disable interrupts due to the
412 On PREEMPT_RT kernel this code sequence breaks because RT-mutex requires a
429 not allow to acquire p->lock because get_cpu_ptr() implicitly disables
[all …]
|
| D | spinlocks.rst | 40 before, because you have to make sure the spinlocks correctly protect the
102 but partly **because** they are safe they are also fairly slow. They are slower
103 than they'd need to be, because they do have to disable interrupts
131 interrupt happens on the same CPU that already holds the lock, because the
132 lock will obviously never be released (because the interrupt is waiting
138 on other CPU's, because an interrupt on another CPU doesn't interrupt the
|
| /linux-6.12.1/drivers/staging/media/atomisp/pci/ |
| D | ia_css_err.h | 29 …IA_CSS_FW_WARNING_ISYS_QUEUE_FULL, /* < CSS system delayed because of insufficient space in the IS…
31 …IA_CSS_FW_WARNING_PSYS_QUEUE_FULL, /* < CSS system delayed because of insufficient space in the PS…
33 …IA_CSS_FW_WARNING_CIRCBUF_ALL_LOCKED, /* < CSS system delayed because of insufficient available bu…
35 …IA_CSS_FW_WARNING_EXP_ID_LOCKED, /* < Exposure ID skipped because the frame associated to it was s…
|
| /linux-6.12.1/rust/kernel/sync/ |
| D | locked_by.rs | 101 /// because in any case at most one thread (or CPU) can access the protected data at a time.
105 "The lock type cannot be a ZST because it may be impossible to distinguish instances" in new()
118 /// `U` cannot be a zero-sized type (ZST) because there are ways to get an `&U` that matches
131 "`U` cannot be a ZST because `owner` wouldn't be unique" in access()
147 /// `U` cannot be a zero-sized type (ZST) because there are ways to get an `&mut U` that
150 /// Showing a mutable reference to the owner is sufficient because we know no other references
160 "`U` cannot be a ZST because `owner` wouldn't be unique" in access_mut()
|
| /linux-6.12.1/fs/ubifs/ |
| D | budget.c | 48 * (@i_mutex) by the caller of the budgeting function, because write-back does
103 * This function is called when an operation cannot be budgeted because there
281 * be large, because UBIFS does not do any index consolidation as long as
310 * @c->lst.empty_lebs are available because they are empty. in do_budget_space()
311 * @c->freeable_cnt are available because they contain only free and in do_budget_space()
312 * dirty space, @c->idx_gc_cnt are available because they are index in do_budget_space()
318 * Note, @c->idx_gc_cnt is included to both @c->lst.empty_lebs (because in do_budget_space()
319 * these LEBs are empty) and to @c->lst.taken_empty_lebs (because they in do_budget_space()
323 * because of the way we serialize LEB allocations and budgeting. See a in do_budget_space()
596 /* The "no space" flags will be cleared because dd_growth is > 0 */ in ubifs_release_dirty_inode_budget()
[all …]
|
| /linux-6.12.1/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | msi-pic.txt | 17 region must be added because different MSI group has different MSIIR1 offset.
30 MPIC v4.3 does not support this property because the 32 interrupts of an
89 because of hardware limitations of the Peripheral Access Management Unit
96 Because PCI devices must be able to DMA to memory, the primary window must
102 means they cannot be located at just any address. Because of these
|