| /Linux-v5.10/tools/perf/Documentation/ |
| D | perf-c2c.txt | 32 for cachelines with highest contention - highest number of HITM accesses.
178 - cacheline percentage of all Remote/Local HITM accesses
184 - sum of all cachelines accesses
187 - sum of all load accesses
190 - sum of all store accesses
193 L1Hit - store accesses that hit L1
194 L1Miss - store accesses that missed L1
200 - count of LLC load accesses, includes LLC hits and LLC HITMs
203 - count of remote load accesses, includes remote hits and remote HITMs
206 - count of local and remote DRAM accesses
[all …]
|
| /Linux-v5.10/Documentation/i2c/ |
| D | i2c-topology.rst | 152 This means that accesses to D2 are lockout out for the full duration
153 of the entire operation. But accesses to D3 are possibly interleaved
216 This means that accesses to both D2 and D3 are locked out for the full
261 When device D1 is accessed, accesses to D2 are locked out for the
263 are locked). But accesses to D3 and D4 are possibly interleaved at
264 any point. Accesses to D3 locks out D1 and D2, but accesses to D4
282 When device D1 is accessed, accesses to D2 and D3 are locked out
284 root adapter). But accesses to D4 are possibly interleaved at any
295 mux. In that case, any interleaved accesses to D4 might close M2
316 When D1 is accessed, accesses to D2 are locked out for the full
[all …]
|
| /Linux-v5.10/drivers/acpi/acpica/ |
| D | exprep.c | 65 u32 accesses; in acpi_ex_generate_access() local
115 accesses = field_end_offset - field_start_offset; in acpi_ex_generate_access()
124 accesses)); in acpi_ex_generate_access()
128 if (accesses <= 1) { in acpi_ex_generate_access()
140 if (accesses < minimum_accesses) { in acpi_ex_generate_access()
141 minimum_accesses = accesses; in acpi_ex_generate_access()
|
| /Linux-v5.10/Documentation/core-api/ |
| D | unaligned-memory-access.rst | 15 unaligned accesses, why you need to write code that doesn't cause them,
22 Unaligned memory accesses occur when you try to read N bytes of data starting
59 - Some architectures are able to perform unaligned memory accesses
61 - Some architectures raise processor exceptions when unaligned accesses
64 - Some architectures raise processor exceptions when unaligned accesses
72 memory accesses to happen, your code will not work correctly on certain
103 to pad structures so that accesses to fields are suitably aligned (assuming
136 lead to unaligned accesses when accessing fields that do not satisfy
183 Here is another example of some code that could cause unaligned accesses::
192 This code will cause unaligned accesses every time the data parameter points
[all …]
|
| /Linux-v5.10/Documentation/admin-guide/hw-vuln/ |
| D | special-register-buffer-data-sampling.rst | 7 infer values returned from special register accesses. Special register
8 accesses are accesses to off core registers. According to Intel's evaluation,
69 accesses from other logical processors will be delayed until the special
81 #. Executing RDRAND, RDSEED or EGETKEY will delay memory accesses from other
83 legacy locked cache-line-split accesses.
90 processors memory accesses. The opt-out mechanism does not affect Intel SGX
|
| /Linux-v5.10/Documentation/devicetree/bindings/ |
| D | common-properties.txt | 13 - big-endian: Boolean; force big endian register accesses
16 - little-endian: Boolean; force little endian register accesses
19 - native-endian: Boolean; always use register accesses matched to the
30 default to LE for their MMIO accesses.
|
| /Linux-v5.10/tools/memory-model/ |
| D | linux-kernel.cat | 160 (* Plain accesses and data races *)
163 (* Warn about plain writes and marked accesses in the same region *)
164 let mixed-accesses = ([Plain & W] ; (po-loc \ barrier) ; [Marked]) |
166 flag ~empty mixed-accesses as mixed-accesses
173 (* Boundaries for lifetimes of plain accesses *)
181 (* Visibility and executes-before for plain accesses *)
191 (* Coherence requirements for plain accesses *)
|
| /Linux-v5.10/Documentation/devicetree/bindings/mtd/ |
| D | gpio-control-nand.txt | 10 resource describes the data bus connected to the NAND flash and all accesses
23 location used to guard against bus reordering with regards to accesses to
26 read to ensure that the GPIO accesses have completed.
|
| /Linux-v5.10/Documentation/dev-tools/ |
| D | kcsan.rst | 94 instrumentation or e.g. DMA accesses. These reports will only be generated if
100 It may be desirable to disable data race detection for specific accesses,
105 any data races due to accesses in ``expr`` should be ignored and resulting
140 accesses are aligned writes up to word size.
190 In an execution, two memory accesses form a *data race* if they *conflict*,
236 KCSAN relies on observing that two accesses happen concurrently. Crucially, we
243 address set up, and then observe the watchpoint to fire, two accesses to the
253 compiler instrumenting plain accesses. For each instrumented plain access:
264 To detect data races between plain and marked accesses, KCSAN also annotates
265 marked accesses, but only to check if a watchpoint exists; i.e. KCSAN never
[all …]
|
| D | ubsan.rst | 78 Detection of unaligned accesses controlled through the separate option -
80 unaligned accesses (CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y). One could
|
| /Linux-v5.10/tools/memory-model/litmus-tests/ |
| D | MP+polocks.litmus | 9 * given lock), a CPU is not only guaranteed to see the accesses that other
11 * to see all prior accesses by those other CPUs.
|
| D | MP+porevlocks.litmus | 9 * given lock), a CPU is not only guaranteed to see the accesses that other
11 * see all prior accesses by those other CPUs.
|
| D | README | 40 litmus test is visible to an external process whose accesses are
141 spin_lock() sufficient to make ordering apparent to accesses
150 to make ordering apparent to accesses by a process that does
173 Each class defines the pattern of accesses and of the variables accessed.
206 accesses with descriptions of the second access in the pair.
220 to a different variable ("d"), and both accesses are reads ("RR").
246 The descriptors that describe connections between consecutive accesses
|
| /Linux-v5.10/arch/mips/kvm/ |
| D | Kconfig | 68 bool "Maintain counters for COP0 accesses"
71 Maintain statistics for Guest COP0 accesses.
72 A histogram of COP0 accesses is printed when the VM is
|
| /Linux-v5.10/Documentation/driver-api/ |
| D | device-io.rst | 30 part of the CPU's address space is interpreted not as accesses to
31 memory, but as accesses to a device. Some architectures define devices
54 historical accident, these are named byte, word, long and quad accesses.
55 Both read and write accesses are supported; there is no prefetch support
127 addresses is generally not as fast as accesses to the memory mapped
137 allow 8-bit, 16-bit and 32-bit accesses; also known as byte, word and
143 that accesses to their ports are slowed down. This functionality is
|
| /Linux-v5.10/Documentation/hwmon/ |
| D | w83627hf.rst | 5 * Winbond W83627HF (ISA accesses ONLY)
41 This driver implements support for ISA accesses *only* for
45 This driver supports ISA accesses, which should be more reliable
46 than i2c accesses. Also, for Tyan boards which contain both a
51 If you really want i2c accesses for these Super I/O chips,
|
| /Linux-v5.10/lib/ |
| D | Kconfig.ubsan | 45 array accesses, where the array size is known at compile time.
59 Enabling this option detects errors due to accesses through a
93 This option enables the check of unaligned memory accesses.
95 accesses may produce a lot of false positives.
|
| D | Kconfig.kasan | 29 designed to find out-of-bounds accesses and use-after-free bugs.
58 but detection of out-of-bounds accesses for global variables is
113 memory accesses. This is faster than outline (in some workloads
175 out of bounds and use after free accesses. It is useful for testing
187 accesses.
|
| /Linux-v5.10/Documentation/process/ |
| D | volatile-considered-harmful.rst | 39 meaning that data accesses will not be optimized across them. So the
43 accesses to that data.
53 registers. Within the kernel, register accesses, too, should be protected
55 accesses within a critical section. But, within the kernel, I/O memory
56 accesses are always done through accessor functions; accessing I/O memory
|
| /Linux-v5.10/tools/memory-model/Documentation/ |
| D | cheatsheet.txt | 34 SELF: Orders self, as opposed to accesses before and/or after
35 SV: Orders later accesses to the same variable
|
| D | explanation.txt | 86 factors such as DMA and mixed-size accesses.) But on multiprocessor
87 systems, with multiple CPUs making concurrent accesses to shared
140 This pattern of memory accesses, where one CPU stores values to two
151 accesses by the CPUs.
276 In short, if a memory model requires certain accesses to be ordered,
278 if those accesses would form a cycle, then the memory model predicts
305 Atomic read-modify-write accesses, such as atomic_inc() or xchg(),
312 logical computations, control-flow instructions, or accesses to
342 po-loc is a sub-relation of po. It links two memory accesses when the
357 that add memory accesses, eliminate accesses, combine them, split them
[all …]
|
| /Linux-v5.10/Documentation/devicetree/bindings/thermal/ |
| D | mediatek-thermal.txt | 5 instead it directly controls the AUXADC via AHB bus accesses. For this reason
7 apmixedsys register space via AHB bus accesses, so a phandle to the APMIXEDSYS
|
| /Linux-v5.10/Documentation/ |
| D | atomic_t.txt | 194 smp_mb__before_atomic() orders all earlier accesses against the RMW op
195 itself and all accesses following it, and smp_mb__after_atomic() orders all
196 later accesses against the RMW op and all accesses preceding it. However,
197 accesses between the smp_mb__{before,after}_atomic() and the RMW op are not
|
| D | memory-barriers.txt | 76 - Acquires vs memory accesses.
156 The set of accesses as seen by the memory system in the middle can be arranged
229 (*) On any given CPU, dependent memory accesses will be issued in order, with
289 (*) It _must_ be assumed that overlapping memory accesses may be merged or
495 ACQUIRE on a given variable, all memory accesses preceding any prior
497 words, within a given variable's critical section, all accesses of all
526 (*) There is no guarantee that any of the memory accesses specified before a
529 access queue that accesses of the appropriate type may not cross.
534 of the first CPU's accesses occur, but see the next point:
537 from a second CPU's accesses, even _if_ the second CPU uses a memory
[all …]
|
| /Linux-v5.10/Documentation/devicetree/bindings/iommu/ |
| D | msm,iommu-v0.txt | 27 required for iommu's register accesses.
29 required by iommu for bus accesses.
|
