Same (full) in projects: linux-6.12.1 - OpenGrok search results

Searched full:same (Results 1 – 25 of 7146) sorted by relevance

/linux-6.12.1/tools/perf/pmu-events/arch/powerpc/power10/
D	datasource.json	35 …uction fetch hit in the L1. Each fetch group contains 8 instructions. The same line can hit 4 time… 230 … was not in the M (exclusive) state from another core's L2 on the same chip in the same regent due… 235 … was not in the M (exclusive) state from another core's L2 on the same chip in the same regent due… 240 …h a line in the M (exclusive) state from another core's L2 on the same chip in the same regent due… 245 …h a line in the M (exclusive) state from another core's L2 on the same chip in the same regent due… 250 …or's instruction cache was reloaded from another core's L2 on the same chip in the same regent due… 255 …cessor's L1 data cache was reloaded from another core's L2 on the same chip in the same regent due… 260 …or's instruction cache was reloaded from another core's L2 on the same chip in the same regent due… 265 …cessor's L1 data cache was reloaded from another core's L2 on the same chip in the same regent due… 270 … was not in the M (exclusive) state from another core's L3 on the same chip in the same regent due… [all …]
/linux-6.12.1/Documentation/ABI/stable/
D	sysfs-devices-system-cpu	9 all per-CPU defaults at the same time. 64 Description: internal kernel map of CPUs within the same core. 69 Description: human-readable list of CPUs within the same core. 75 Description: internal kernel map of the CPUs sharing the same physical_package_id. 80 Description: human-readable list of CPUs sharing the same physical_package_id. 86 Description: internal kernel map of CPUs within the same die. 94 Description: human-readable list of CPUs within the same die. 99 Description: internal kernel map of CPUs within the same cluster. 103 Description: human-readable list of CPUs within the same cluster. 108 Description: internal kernel map of cpuX's hardware threads within the same [all …]
/linux-6.12.1/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-6.12.1/tools/perf/pmu-events/arch/x86/amdzen5/
D	load-store.json	96 …"BriefDescription": "Demand data cache fills from L3 cache or different L2 cache in the same CCX.", 102 …": "Demand data cache fills from cache of another CCX when the address was in the same NUMA node.", 108 "BriefDescription": "Demand data cache fills from either DRAM or MMIO in the same NUMA node.", 120 …emand data cache fills from either DRAM or MMIO in a different NUMA node (same or different socket… 144 "BriefDescription": "Any data cache fills from L3 cache or different L2 cache in the same CCX.", 150 …on": "Any data cache fills from local L2 cache or L3 cache or different L2 cache in the same CCX.", 156 …ion": "Any data cache fills from cache of another CCX when the address was in the same NUMA node.", 162 "BriefDescription": "Any data cache fills from either DRAM or MMIO in the same NUMA node.", 174 …ny data cache fills from cache of another CCX when the address was in the same or a different NUMA… 180 … "Any data cache fills from either DRAM or MMIO in a different NUMA node (same or different socket… [all …]
/linux-6.12.1/scripts/coccinelle/misc/
D	array_size_dup.cocci	5 /// 1. An opencoded expression is used before array_size() to compute the same size 6 /// 2. An opencoded expression is used after array_size() to compute the same size 43 msg = "WARNING: array_size is used later (line %s) to compute the same size" % (p2[0].line) 51 msg = "WARNING: array_size is used later (line %s) to compute the same size" % (p2[0].line) 72 msg = "WARNING: array_size is already used (line %s) to compute the same size" % (p1[0].line) 80 msg = "WARNING: array_size is already used (line %s) to compute the same size" % (p1[0].line) 108 msg = "WARNING: array3_size is used later (line %s) to compute the same size" % (p2[0].line) 116 msg = "WARNING: array3_size is used later (line %s) to compute the same size" % (p2[0].line) 138 msg = "WARNING: array3_size is already used (line %s) to compute the same size" % (p1[0].line) 146 msg = "WARNING: array3_size is already used (line %s) to compute the same size" % (p1[0].line) [all …]
/linux-6.12.1/kernel/
D	cpu_pm.c	59 * This function has the same return conditions as raw_notifier_chain_register. 79 * This function has the same return conditions as raw_notifier_chain_unregister. 97 * cause some blocks in the same power domain as the cpu to reset. 100 * responsible for ensuring that cpu_pm_enter is not called twice on the same 106 * Return conditions are same as __raw_notifier_call_chain. 118 * have caused some blocks in the same power domain as the cpu to reset. 124 * Return conditions are same as __raw_notifier_call_chain. 136 * state that may cause some blocks in the same power domain to reset. 146 * Return conditions are same as __raw_notifier_call_chain. 158 * low power state that may have caused some blocks in the same power domain [all …]
/linux-6.12.1/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-6.12.1/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-6.12.1/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 …]
/linux-6.12.1/tools/perf/pmu-events/arch/x86/amdzen3/
D	memory.json	6 … Software can avoid this problem by using same-size and same-alignment loads and stores when acces… 46 …patch. Dispatch of a single op that performs a load from and store to the same memory address. Cou… 144 …"BriefDescription": "Demand Data Cache Fills by Data Source. From DRAM or IO connected in same nod… 150 …fDescription": "Demand Data Cache Fills by Data Source. From cache of different CCX in same node.", 156 …"BriefDescription": "Demand Data Cache Fills by Data Source. From L3 or different L2 in same CCX.", 180 …"BriefDescription": "Any Data Cache Fills by Data Source. From DRAM or IO connected in same node.", 186 …"BriefDescription": "Any Data Cache Fills by Data Source. From cache of different CCX in same node… 192 "BriefDescription": "Any Data Cache Fills by Data Source. From L3 or different L2 in same CCX.", 354 …ion": "Software Prefetch Data Cache Fills by Data Source. From DRAM or IO connected in same node.", 360 …n": "Software Prefetch Data Cache Fills by Data Source. From cache of different CCX in same node.", [all …]
/linux-6.12.1/tools/perf/pmu-events/arch/x86/amdzen4/
D	cache.json	29 …"BriefDescription": "Demand data cache fills from L3 cache or different L2 cache in the same CCX.", 35 …": "Demand data cache fills from cache of another CCX when the address was in the same NUMA node.", 41 "BriefDescription": "Demand data cache fills from either DRAM or MMIO in the same NUMA node.", 53 …emand data cache fills from either DRAM or MMIO in a different NUMA node (same or different socket… 77 "BriefDescription": "Any data cache fills from L3 cache or different L2 cache in the same CCX.", 83 …on": "Any data cache fills from local L2 cache or L3 cache or different L2 cache in the same CCX.", 89 …ion": "Any data cache fills from cache of another CCX when the address was in the same NUMA node.", 95 "BriefDescription": "Any data cache fills from either DRAM or MMIO in the same NUMA node.", 107 …ny data cache fills from cache of another CCX when the address was in the same or a different NUMA… 113 … "Any data cache fills from either DRAM or MMIO in a different NUMA node (same or different socket… [all …]
/linux-6.12.1/fs/
D	remap_range.c	85 /* Don't allow overlapped cloning within the same file. / in generic_remap_checks() 167 are from the same file. 180 /* Unlock two folios, being careful not to unlock the same folio twice. / 189 Compare extents of two files to see if they are the same. 196 bool same = true; in vfs_dedupe_file_range_compare() local 231 same = false; in vfs_dedupe_file_range_compare() 244 same = false; in vfs_dedupe_file_range_compare() 253 if (!same) in vfs_dedupe_file_range_compare() 261 is_same = same; in vfs_dedupe_file_range_compare() 335 Check that the extents are the same. in __generic_remap_file_range_prep() [all …]
/linux-6.12.1/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 …]
/linux-6.12.1/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 79 it follows the same syntax as the DEBUGINFOD_URLS variable, like:`
/linux-6.12.1/tools/testing/selftests/arm64/pauth/
D	pac.c	`73 int same = 0; in n_same_single_set() local 86 same += 1; in n_same_single_set() 89 return same; in n_same_single_set() 254 int same = 10; in TEST() local 283 if (tmp < same) in TEST() 284 same = tmp; in TEST() 287 ASSERT_EQ(0, same) TH_LOG("%d keys clashed every time", same); in TEST() 299 int same = 10; in TEST() local 320 if (ret < same) in TEST() 321 same = ret; in TEST() [all …]`
/linux-6.12.1/rust/kernel/
D	page.rs	91 /// If multiple threads map the same page at the same time, then they may reference with 93 /// still the same for these purposes (e.g., it's still a data race if they both write to the 94 /// same underlying byte at the same time). 132 /// If multiple threads map the same page at the same time, then they may reference with 134 /// still the same for these purposes (e.g., it's still a data race if they both write to the 135 /// same underlying byte at the same time). 163 /// * Callers must ensure that this call does not race with a write to the same page that 185 /// * Callers must ensure that this call does not race with a read or write to the same page 205 /// Callers must ensure that this call does not race with a read or write to the same page that 228 /// Callers must ensure that this call does not race with a read or write to the same page that
/linux-6.12.1/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-6.12.1/tools/testing/selftests/powerpc/pmu/event_code_tests/
D	group_constraint_repeat_test.c	`16 * when using events with same PMC. 18 * ask for same PMC. If so it should fail. 29 * Two events in a group using same PMC in group_constraint_repeat() 30 * should fail to get scheduled. Usei same PMC2 in group_constraint_repeat() 39 /* Expected to fail since sibling event is requesting same PMC as leader */ in group_constraint_repeat()`
/linux-6.12.1/drivers/pci/
D	Kconfig	105 require SR-IOV support, while at the same time the PF (Physical 169 to access more than one IO address space at the same time. To make 194 P2P DMA transactions must be between devices behind the same root 233 at compile-time. The choices are the same as those offered for 245 Use the BIOS defaults; don't touch MPS at all. This is the same 261 is the same as booting with 'pci=pcie_bus_safe'. 270 parent. This is the same as booting with 'pci=pcie_bus_perf'. 281 This is the same as booting with 'pci=pcie_bus_peer2peer'. 290 Some "legacy" VGA devices implemented on PCI typically have the same 292 are accessed at same time they need some kind of coordination. Please
/linux-6.12.1/Documentation/filesystems/nfs/
D	client-identifier.rst	57 server to distinguish successive boot epochs of the same client. 95 If distinct clients present the same "co_ownerid" string and use 96 the same principal (for example, AUTH_SYS and UID 0), a server is 97 unable to tell that the clients are not the same. Each distinct 102 If distinct clients present the same "co_ownerid" string and use 104 to operate normally but reject subsequent clients with the same 128 the client's UTS node name (the same node name, incidentally, that 140 client instances with the same host name. 191 use the same lease for operations covered by all "sec=" settings. 206 migration by presenting the same "client_owner4" to all servers it
/linux-6.12.1/Documentation/arch/x86/
D	sva.rst	11 same virtual addresses avoiding the need for software to translate virtual 18 (PRI) allow devices to function much the same way as the CPU handling 98 with the same PASID. The platform IOMMU uses the PASID in the transaction to 104 thread can interact with a device. Threads that belong to the same 105 process share the same page tables, thus the same MSR value. 114 device but finds no PASID for this process. Subsequent binds of the same, or 115 other devices will share the same PASID. 129 longer has the same address space that it had when the device was opened. 131 On clone(2) the new task shares the same address space, so will be 161 * Multiple processes can separately mmap() the same portal, in [all …]
/linux-6.12.1/Documentation/filesystems/
D	directory-locking.rst	81 from the same NFS4 server and doing lookups in one of them has reached 86 For a lot of reasons we want to have the same directory present in dcache 121 on other filesystems must follow the same locking rules. Moreover, "a 142 * put ->i_rwsem of all directories on a filesystem at the same rank, 143 lower than ->i_rwsem of any non-directory on the same filesystem. 145 on the same filesystem. 152 2. ->i_rwsem of directories on that NFS filesystem, same rank for all 156 5. ->i_rwsem of directories on the local filesystem, same rank for all 168 contended locks in the minimal deadlock will be of the same rank, 169 i.e. they all will be ->i_rwsem of directories on the same filesystem. [all …]
/linux-6.12.1/tools/perf/pmu-events/arch/x86/elkhartlake/
D	frontend.json	`56 …same cache line or byte chunk count as one. Specifically, the event counts when accesses from seq… 65 …same cache line and byte chunk count as one. Specifically, the event counts when accesses from se… 74 …same cache line and byte chunk count as one. Specifically, the event counts when accesses from se…`

12 3 4 5 6 7 8 9 10 >>...286

Project(s)

Full Search
Definition
Symbol
File Path
History
Type