Searched full:same (Results 1 – 25 of 5460) sorted by relevance
12345678910>>...219
/Linux-v5.4/arch/nios2/include/asm/ |
D | asm-macros.h | 16 * You cannnot use the same register for reg1 & reg2. 36 * It is safe to use the same register for reg1 & reg2. 55 * It is safe to use the same register for reg1 & reg2. 75 * It is safe to use the same register for reg1 & reg2. 94 * It is safe to use the same register for reg1 & reg2. 106 * It is safe to use the same register for reg1 & reg2. 118 * It is NOT safe to use the same register for reg1 & reg2. 139 * It is NOT safe to use the same register for reg1 & reg2. 160 * It is NOT safe to use the same register for reg1 & reg2. 182 * It is NOT safe to use the same register for reg1 & reg2. [all …]
|
/Linux-v5.4/kernel/ |
D | cpu_pm.c | 42 * This function may sleep, and has the same return conditions as 57 * This function may sleep, and has the same return conditions as 70 * cause some blocks in the same power domain as the cpu to reset. 73 * responsible for ensuring that cpu_pm_enter is not called twice on the same 79 * Return conditions are same as __raw_notifier_call_chain. 102 * have caused some blocks in the same power domain as the cpu to reset. 108 * Return conditions are same as __raw_notifier_call_chain. 120 * state that may cause some blocks in the same power domain to reset. 130 * Return conditions are same as __raw_notifier_call_chain. 153 * low power state that may have caused some blocks in the same power domain [all …]
|
/Linux-v5.4/Documentation/driver-api/usb/ |
D | persist.rst | 22 has no way to know what has actually happened. Perhaps the same 35 system woke up, who cares? It'll still work the same when you type on 39 devices. The effect is exactly the same as if the device really had 47 interrupts a power session will have the same effect. For example, 83 same thing that happens whenever a USB device is reset.) If the 85 same descriptors as before, including the Vendor and Product IDs, then 86 the kernel continues to use the same device structure. In effect, the 90 The same thing happens if the host controller is in the expected state 125 have the same persistent volume associated with the device. As such 142 to make sure the USB device hasn't been changed; that is, the same [all …]
|
/Linux-v5.4/Documentation/devicetree/bindings/display/ |
D | st,stih4xx.txt | 18 - clock-names: names of the clocks listed in clocks property in the same 36 - clock-names: names of the clocks listed in clocks property in the same 40 - reset-names: names of the resets listed in resets property in the same 50 the same order. 53 - reset-names: names of the resets listed in resets property in the same 62 the same order. 65 the same order 68 - clock-names: names of the clocks listed in clocks property in the same 78 the same order. 82 - clock-names: names of the clocks listed in clocks property in the same [all …]
|
/Linux-v5.4/Documentation/admin-guide/ |
D | cputopology.rst | 41 internal kernel map of CPUs within the same core. 46 human-readable list of CPUs within the same core. 51 internal kernel map of the CPUs sharing the same physical_package_id. 56 human-readable list of CPUs sharing the same physical_package_id. 61 internal kernel map of CPUs within the same die. 65 human-readable list of CPUs within the same die. 69 internal kernel map of cpuX's hardware threads within the same 74 human-readable list of cpuX's hardware threads within the same 79 internal kernel map of cpuX's hardware threads within the same 84 human-readable list of cpuX's hardware threads within the same
|
/Linux-v5.4/tools/perf/pmu-events/arch/powerpc/power8/ |
D | other.json | 5 …on": "Number of cycles in single lpar mode. All threads in the core are assigned to the same lpar", 389 …The processor's data cache was reloaded from another chip's memory on the same Node or Group (Dist… 390 …The processor's data cache was reloaded from another chip's memory on the same Node or Group (Dist… 401 …a cache was reloaded with Modified (M) data from another core's L2 on the same chip due to either … 402 …a cache was reloaded with Modified (M) data from another core's L2 on the same chip due to either … 407 …ata cache was reloaded with Shared (S) data from another core's L2 on the same chip due to either … 408 …ata cache was reloaded with Shared (S) data from another core's L2 on the same chip due to either … 449 …che was reloaded with Modified (M) data from another core's ECO L3 on the same chip due to either … 450 …che was reloaded with Modified (M) data from another core's ECO L3 on the same chip due to either … 455 …cache was reloaded with Shared (S) data from another core's ECO L3 on the same chip due to either … [all …]
|
D | frontend.json | 107 …cessor's Instruction cache was reloaded from another chip's memory on the same Node or Group (Dist… 108 …cessor's Instruction cache was reloaded from another chip's memory on the same Node or Group (Dist… 209 … reloaded either shared or modified data from another core's L2/L3 on the same chip due to an inst… 210 … reloaded either shared or modified data from another core's L2/L3 on the same chip due to either … 215 …e was reloaded with Modified (M) data from another chip's L2 or L3 on the same Node or Group (Remo… 216 …e was reloaded with Modified (M) data from another chip's L2 or L3 on the same Node or Group (Remo… 221 …che was reloaded with Shared (S) data from another chip's L2 or L3 on the same Node or Group (Remo… 222 …che was reloaded with Shared (S) data from another chip's L2 or L3 on the same Node or Group (Remo… 227 … processor's Instruction cache was reloaded from another chip's L4 on the same Node or Group ( Rem… 228 … processor's Instruction cache was reloaded from another chip's L4 on the same Node or Group ( Rem… [all …]
|
D | marked.json | 71 …The processor's data cache was reloaded from another chip's memory on the same Node or Group (Dist… 77 …"BriefDescription": "Duration in cycles to reload from another chip's memory on the same Node or G… 263 … reloaded either shared or modified data from another core's L2/L3 on the same chip due to a marke… 269 …to reload either shared or modified data from another core's L2/L3 on the same chip due to a marke… 275 …e was reloaded with Modified (M) data from another chip's L2 or L3 on the same Node or Group (Remo… 281 …cles to reload with Modified (M) data from another chip's L2 or L3 on the same Node or Group (Remo… 287 …che was reloaded with Shared (S) data from another chip's L2 or L3 on the same Node or Group (Remo… 293 …cycles to reload with Shared (S) data from another chip's L2 or L3 on the same Node or Group (Remo… 299 …"BriefDescription": "The processor's data cache was reloaded from another chip's L4 on the same No… 305 …"BriefDescription": "Duration in cycles to reload from another chip's L4 on the same Node or Group… [all …]
|
/Linux-v5.4/Documentation/vm/ |
D | zswap.rst | 113 Some of the pages in zswap are same-value filled pages (i.e. contents of the 114 page have same value or repetitive pattern). These pages include zero-filled 116 checked if it is a same-value filled page before compressing it. If true, the 117 compressed length of the page is set to zero and the pattern or same-filled 120 Same-value filled pages identification feature is enabled by default and can be 128 When zswap same-filled page identification is disabled at runtime, it will stop 129 checking for the same-value filled pages during store operation. However, the 130 existing pages which are marked as same-value filled pages remain stored 134 of pages stored, same-value filled pages and various counters for the reasons
|
D | numa.rst | 35 attached to the same cell will experience faster access times and higher 43 [cache misses] to be to "local" memory--memory on the same cell, if any--or 61 a given node will see the same local memory access times and bandwidth. 83 fall back to the same zone type on a different node, or to a different zone 84 type on the same node. This is an important consideration because some zones, 87 from the same node before using remote nodes which are ordered by NUMA distance. 125 closest available memory. This is a consequence of the same mechanism that 149 specified CPU. Again, this is the same node from which default, local page
|
/Linux-v5.4/arch/mips/include/asm/sibyte/ |
D | bcm1480_scd.h | 25 * Pull in the BCM1250's SCD since lots of stuff is the same. 152 * Same as BCM1250 159 * Same as BCM1250 172 * The watchdogs are almost the same as the 1250, except 205 * The timer registers are the same as the BCM1250 213 * Same as BCM1250 220 * Same as BCM1250 228 * SPC_CFG_SRC[0-3] is the same as the 1250. 281 * Same as BCM1250. 287 * Same as BCM1250. [all …]
|
/Linux-v5.4/tools/perf/pmu-events/arch/powerpc/power9/ |
D | translation.json | 15 …ata cache was reloaded with Shared (S) data from another core's L2 on the same chip due to a deman… 25 …age Table Entry was loaded into the TLB from another chip's memory on the same Node or Group (Dist… 35 …ded into the TLB with Shared (S) data from another chip's L2 or L3 on the same Node or Group (Remo… 75 …o the TLB either shared or modified data from another core's L2/L3 on the same chip due to a instr… 80 …ion cache was reloaded with Shared (S) data from another core's L2 on the same chip due to an inst… 95 …a cache was reloaded with Modified (M) data from another core's L2 on the same chip due to a deman… 100 …"A Page Table Entry was loaded into the TLB from another chip's L4 on the same Node or Group ( Rem… 135 …cles to reload with Modified (M) data from another chip's L2 or L3 on the same Node or Group (Remo… 200 …n cycles to reload with Shared (S) data from another core's ECO L3 on the same chip due to a marke… 210 …d into the TLB with Modified (M) data from another chip's L2 or L3 on the same Node or Group (Remo… [all …]
|
D | cache.json | 10 …nstruction is not allowed to complete because any of the 4 threads in the same core suffered a flu… 25 …"BriefDescription": "Duration in cycles to reload from another chip's L4 on the same Node or Group… 40 … reloaded either shared or modified data from another core's L2/L3 on the same chip due to an inst… 50 … processor's Instruction cache was reloaded from another chip's L4 on the same Node or Group ( Rem… 55 …che was reloaded with Shared (S) data from another chip's L2 or L3 on the same Node or Group (Remo… 80 …age Table Entry was loaded into the TLB from another chip's memory on the same Node or Group ( Rem… 100 …e was reloaded with Modified (M) data from another chip's L2 or L3 on the same Node or Group (Remo…
|
D | pipeline.json | 30 … reloaded either shared or modified data from another core's L2/L3 on the same chip due to a marke… 80 … loaded into the TLB with Modified (M) data from another core's L2 on the same chip due to a marke… 95 … loaded into the TLB with Modified (M) data from another core's L2 on the same chip due to a data … 100 … it lost arbitration onto the issue pipe to another instruction (from the same thread or a differe… 190 …e was reloaded with Modified (M) data from another chip's L2 or L3 on the same Node or Group (Remo… 235 …e was reloaded with Modified (M) data from another chip's L2 or L3 on the same Node or Group (Remo… 250 …ded into the TLB with Shared (S) data from another chip's L2 or L3 on the same Node or Group (Remo… 260 …d into the TLB with Modified (M) data from another chip's L2 or L3 on the same Node or Group (Remo… 265 …age Table Entry was loaded into the TLB from another chip's memory on the same Node or Group (Dist… 285 …The processor's data cache was reloaded from another chip's memory on the same Node or Group (Dist… [all …]
|
D | frontend.json | 5 … loaded into the TLB with Modified (M) data from another core's L3 on the same chip due to a instr… 30 …l 4 slices. This is event is not per thread. All the threads will see the same count for this core… 50 …che was reloaded with Modified (M) data from another core's ECO L3 on the same chip due to a deman… 115 …as loaded into the TLB with Shared (S) data from another core's L3 on the same chip due to a instr… 155 …cycles to reload with Shared (S) data from another chip's L2 or L3 on the same Node or Group (Remo… 170 …to reload either shared or modified data from another core's L2/L3 on the same chip due to a marke… 195 …age Table Entry was loaded into the TLB from another chip's memory on the same Node or Group ( Rem… 315 …oaded into the TLB with Shared (S) data from another core's ECO L3 on the same chip due to a instr… 330 …"BriefDescription": "The processor's data cache was reloaded from another chip's L4 on the same No… 335 …cache was reloaded with Shared (S) data from another core's ECO L3 on the same chip due to a marke… [all …]
|
D | marked.json | 20 …as loaded into the TLB with Shared (S) data from another core's L3 on the same chip due to a data … 25 …The processor's data cache was reloaded from another chip's memory on the same Node or Group ( Rem… 70 …oaded into the TLB with Shared (S) data from another core's ECO L3 on the same chip due to a marke… 95 …ded into the TLB with Modified (M) data from another core's ECO L3 on the same chip due to a marke… 100 …oaded into the TLB with Shared (S) data from another core's ECO L3 on the same chip due to a data … 120 …cessor's Instruction cache was reloaded from another chip's memory on the same Node or Group (Dist… 180 …ata cache was reloaded with Shared (S) data from another core's L3 on the same chip due to a deman… 185 …a cache was reloaded with Modified (M) data from another core's L3 on the same chip due to a deman… 190 …"BriefDescription": "The processor's data cache was reloaded from another chip's L4 on the same No… 195 …n cache was reloaded with Modified (M) data from another core's L3 on the same chip due to an inst… [all …]
|
/Linux-v5.4/tools/perf/Documentation/ |
D | perf-buildid-cache.txt | 38 same directory and are also copied. All 3 files are created with read 40 kcore in the cache (with the same build-id) that has the same modules at 41 the same addresses. Use the -v option to see if a copy of kcore is 45 Remove a cached binary which has same build-id of specified file 62 exactly same build-id, that is replaced by new one. It can be used
|
/Linux-v5.4/Documentation/devicetree/bindings/net/ |
D | socionext-netsec.txt | 11 - phy-mode: See ethernet.txt file in the same directory 12 - phy-handle: See ethernet.txt in the same directory. 26 Optional properties: (See ethernet.txt file in the same directory) 29 - max-speed: See ethernet.txt in the same directory. 30 - max-frame-size: See ethernet.txt in the same directory.
|
/Linux-v5.4/include/linux/ |
D | rwsem.h | 26 * other to increase the chance that they will share the same cacheline. 32 * reduce the chance that they will share the same cacheline causing 114 * This is the same regardless of which rwsem implementation that is being used. 164 * (which occurs if the same task tries to acquire the same 166 * same lock class might be taken, if the order of the locks 167 * is always the same. This ordering rule can be expressed
|
/Linux-v5.4/Documentation/x86/ |
D | tsx_async_abort.rst | 17 the same uarch data structures as in MDS, with same scope of exposure i.e. 18 same-thread and cross-thread. This issue affects all current processors that 69 …0 0 0 HW default Yes Same as MDS Same as MDS 84 … 0 0 0 HW default Yes Same as MDS Same as MDS 87 … 0 1 1 Enabled Yes None Same as MDS 99 …0 0 0 HW default Yes Same as MDS Same as MDS
|
/Linux-v5.4/samples/bpf/ |
D | tcp_clamp_kern.c | 9 * the same datacenter. For his example, we assume they are within the same 10 * datacenter when the first 5.5 bytes of their IPv6 addresses are the same. 48 /* Check that both hosts are within same datacenter. For this example in bpf_clamp() 50 * the same. in bpf_clamp()
|
/Linux-v5.4/Documentation/core-api/ |
D | refcount-vs-atomic.rst | 35 program order (po) relation (on the same CPU). It guarantees that 42 stores (all po-earlier instructions) on the same CPU are completed 43 before any po-later instruction is executed on the same CPU. 44 It also guarantees that all po-earlier stores on the same CPU 50 stores (all po-earlier instructions) on the same CPU are completed 52 stores on the same CPU and all propagated stores from other CPUs 58 stores (all po-later instructions) on the same CPU are 60 po-later stores on the same CPU must propagate to all other CPUs
|
/Linux-v5.4/Documentation/networking/ |
D | scaling.rst | 135 the receive descriptor for the packet; this would usually be the same 171 the rps_cpus to the CPUs in the same memory domain of the interrupting 180 share the same memory domain as the interrupting CPU for that queue. 187 reordering. The trade-off to sending all packets from the same flow 188 to the same CPU is CPU load imbalance if flows vary in packet rate. 215 in sysctl net.core.flow_limit_cpu_bitmap. It exposes the same CPU 222 the same that selects a CPU in RPS, but as the number of buckets can 255 consuming the packet is running. RFS relies on the same RPS mechanisms 266 same CPU. Indeed, with many flows and few CPUs, it is very likely that 282 and userspace processing occur on the same CPU, and hence the CPU index [all …]
|
/Linux-v5.4/tools/perf/pmu-events/arch/s390/cf_z10/ |
D | extended.json | 21 …he installed cache line was sourced from the Level-3 cache that is on the same book as the Instruc… 28 …e installtion cache line was source from the Level-3 cache that is on the same book as the Data ca… 35 … installed cache line was sourced from a Level-3 cache that is not on the same book as the Instruc… 42 … installed cache line was sourced from a Level-3 cache that is not on the same book as the Data ca… 49 … the installed cache line was sourced from memory that is attached to the same book as the Data ca… 70 … cache line in the Level-1 I-Cache has been invalidated by a store on the same CPU as the Level-1 …
|
/Linux-v5.4/tools/usb/ |
D | hcd-tests.sh | 27 # - connect several devices concurrently (same HC) 126 echo "test 1: $COUNT transfers, same size" 139 echo "test 5: $COUNT scatterlists, same size entries" 166 echo "test 15: $COUNT transfers, same size" 187 echo "test 2: $COUNT transfers, same size" 200 echo "test 6: $COUNT scatterlists, same size entries" 219 echo "test 16: $COUNT transfers, same size"
|
12345678910>>...219