| /Linux-v5.4/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-v5.4/tools/perf/pmu-events/arch/s390/cf_z13/ |
| D | crypto.json | 21 … number of the PRNG functions that are issued by the CPU and are blocked because the DEA/AES copro…
28 …al number of CPU cycles blocked for the PRNG functions issued by the CPU because the DEA/AES copro…
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 …Total number of 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-v5.4/tools/perf/pmu-events/arch/s390/cf_z14/ |
| D | crypto.json | 21 … number of the PRNG functions that are issued by the CPU and are blocked because the DEA/AES copro…
28 …al number of CPU cycles blocked for the PRNG functions issued by the CPU because the DEA/AES copro…
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 …Total number of 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-v5.4/tools/perf/pmu-events/arch/s390/cf_z15/ |
| D | crypto.json | 21 … number of the PRNG functions that are issued by the CPU and are blocked because the DEA/AES copro…
28 …al number of CPU cycles blocked for the PRNG functions issued by the CPU because the DEA/AES copro…
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 …Total number of 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-v5.4/tools/perf/pmu-events/arch/s390/cf_z196/ |
| D | crypto.json | 21 … number of the PRNG functions that are issued by the CPU and are blocked because the DEA/AES copro…
28 …al number of CPU cycles blocked for the PRNG functions issued by the CPU because the DEA/AES copro…
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 …Total number of 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-v5.4/tools/perf/pmu-events/arch/s390/cf_zec12/ |
| D | crypto.json | 21 … number of the PRNG functions that are issued by the CPU and are blocked because the DEA/AES copro…
28 …al number of CPU cycles blocked for the PRNG functions issued by the CPU because the DEA/AES copro…
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 …Total number of 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-v5.4/tools/perf/pmu-events/arch/s390/cf_z10/ |
| D | crypto.json | 21 … number of the PRNG functions that are issued by the CPU and are blocked because the DEA/AES copro…
28 …al number of CPU cycles blocked for the PRNG functions issued by the CPU because the DEA/AES copro…
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 …Total number of 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-v5.4/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-v5.4/tools/perf/pmu-events/arch/arm64/arm/cortex-a76-n1/ |
| D | pipeline.json | 3 …"PublicDescription": "No operation issued because of the frontend. The counter counts on any cycle…
6 "BriefDescription": "No operation issued because of the frontend."
9 …"PublicDescription": "No operation issued because of the backend. The counter counts on any cycle …
12 "BriefDescription": "No operation issued because of the backend."
|
| /Linux-v5.4/arch/x86/boot/compressed/ |
| D | efi_stub_32.S | 7 * arch/x86/platform/efi/efi_stub_32.S because we're _already_ in physical
22 * at the end no matter how many we use, because we can not assure EFI runtime
37 * 1. Because we haven't been relocated by this point we need to
62 * 4. Balance the stack. And because EAX contain the return value,
64 * again because %ecx and %edx are not preserved across EFI function
|
| /Linux-v5.4/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-v5.4/Documentation/locking/ |
| 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-v5.4/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
|
| /Linux-v5.4/fs/f2fs/ |
| D | verity.c | 13 * boundary beyond i_size. This approach works because (a) verity files are
16 * changes to f2fs. Extended attributes cannot be used because (a) f2fs limits
20 * because it contains hashes of the plaintext data.
38 * Read some verity metadata from the inode. __vfs_read() can't be used because
70 * kernel_write() can't be used because the file descriptor is readonly.
111 * descriptor within the file data rather than containing it directly because
|
| /Linux-v5.4/fs/ubifs/ |
| D | budget.c | 48 * (@i_mutex) by the caller of the budgeting function, because write-back does
106 * This function is called when an operation cannot be budgeted because there
285 * be large, because UBIFS does not do any index consolidation as long as
314 * @c->lst.empty_lebs are available because they are empty. in do_budget_space()
315 * @c->freeable_cnt are available because they contain only free and in do_budget_space()
316 * dirty space, @c->idx_gc_cnt are available because they are index in do_budget_space()
322 * Note, @c->idx_gc_cnt is included to both @c->lst.empty_lebs (because in do_budget_space()
323 * these LEBs are empty) and to @c->lst.taken_empty_lebs (because they in do_budget_space()
327 * because of the way we serialize LEB allocations and budgeting. See a in do_budget_space()
600 /* The "no space" flags will be cleared because dd_growth is > 0 */ in ubifs_release_dirty_inode_budget()
[all …]
|
| /Linux-v5.4/Documentation/vm/ |
| D | active_mm.rst | 14 Cc'd to linux-kernel, because I don't write explanations all that often,
65 lazy users. That is often a short-lived state, because once that thread
67 released because "mm_users" becomes zero.
85 because it slightly changes the interfaces to accommodate the alpha (who
|
| /Linux-v5.4/arch/ia64/lib/ |
| D | copy_user.S | 10 * errors on stores. Note that because of the nature of the copy
99 mov dst1=dst // copy because of rotation
103 mov src1=src // copy because of rotation
230 // because we need 2 back-to-back val1[] to get tmp.
325 mov len1=len // copy because of rotation
343 // Stop bit not required after ld4 because if we fail on ld4
352 // Stop bit not required after ld8 because if we fail on ld8
436 // pipeline going. We can't really do this inline because
503 // This allows us to simplify the cleanup code, because basically you
516 // because it would mean you had 15bytes to copy in which case you
[all …]
|
| D | strlen.S | 31 // so we need to do a few extra checks at the beginning because the
38 // Because we don't want the kernel to be relying on particular
62 // - after the loop we must test for Nat values because neither the
150 mov ar.pfs=saved_pfs // because of ar.ec, restore no matter what
158 // because read ahead is not possible
192 mov ar.pfs=saved_pfs // because of ar.ec, restore no matter what
|
| /Linux-v5.4/drivers/message/fusion/lsi/ |
| D | mpi_log_fc.h | 54 …MPI_IOCLOGINFO_FC_TARGET_NO_PDISC = 0x21000001, /* not sent because we are waiting f…
55 …MPI_IOCLOGINFO_FC_TARGET_NO_LOGIN = 0x21000002, /* not sent because we are not logge…
64 …MPI_IOCLOGINFO_FC_TARGET_NO_CLASS_3 = 0x2100000b, /* not sent because remote node does…
65 …MPI_IOCLOGINFO_FC_TARGET_LOGIN_NOT_VALID = 0x2100000c, /* not sent because login to remote …
|
| /Linux-v5.4/kernel/locking/ |
| D | osq_lock.c | 10 * Using a single mcs node per CPU is safe because sleeping locks should not be
69 * We must xchg() the @node->next value, because if we were to in osq_wait_next()
129 * Normally @prev is untouchable after the above store; because at that in osq_lock()
195 * @prev is stable because its still waiting for a new @prev->next in osq_lock()
196 * pointer, @next is stable because our @node->next pointer is NULL and in osq_lock()
|
| /Linux-v5.4/Documentation/networking/ |
| D | checksum-offloads.rst | 38 Because csum_offset cannot be negative, this ensures that the previous value of
53 software. This is OK because when we build the IP header, we obviously have it
56 The requirements for GSO are more complicated, because when segmenting an
88 to the complement of the sum of the pseudo header, because everything else gets
89 'cancelled out' by the checksum field. This is because the sum was
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-class-mic | 69 OS can shutdown because of various reasons. When read, this
74 "crashed" - Shutdown because of a HW or SW crash.
75 "halted" - Shutdown because of a halt command.
76 "poweroff" - Shutdown because of a poweroff command.
77 "restart" - Shutdown because of a restart command.
|
| /Linux-v5.4/Documentation/i2c/ |
| D | gpio-fault-injection.rst | 26 because the bus master under test will not be able to clock. It should detect
39 succeed because SDA is still pinned low until you manually release it again
61 transmitted. Because the device will ACK its presence, this results in SDA
74 because it acknowledges data. However, there are two differences compared to
103 There doesn't need to be a device at this address because arbitration lost
|
