cores (full) in projects: linux - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:cores (Results 1 – 25 of 713) sorted by relevance

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

/linux/tools/perf/pmu-events/arch/x86/graniterapids/
H A D	uncore-cache.json	1109 "BriefDescription": "All locally initiated requests from IA Cores", 1115 "PublicDescription": "TOR Inserts : All requests from iA Cores", 1125 "PublicDescription": "TOR Inserts : CLFlushes issued by iA Cores", 1135 "PublicDescription": "TOR Inserts : CRDs issued by iA Cores", 1155 "PublicDescription": "TOR Inserts : DRds issued by iA Cores", 1160 "BriefDescription": "DRd PTEs issued by iA Cores due to a page walk", 1165 "PublicDescription": "TOR Inserts : DRdPte issued by iA Cores due to a page walk", 1175 "PublicDescription": "TOR Inserts : DRd_Prefs issued by iA Cores", 1180 "BriefDescription": "All locally initiated requests from IA Cores which hit the cache", 1186 "PublicDescription": "TOR Inserts : All requests from iA Cores that Hit the LLC", [all …]
/linux/tools/perf/pmu-events/arch/x86/grandridge/
H A D	uncore-cache.json	575 "BriefDescription": "All locally initiated requests from IA Cores", 581 "PublicDescription": "TOR Inserts : All requests from iA Cores", 591 "PublicDescription": "TOR Inserts : CLFlushes issued by iA Cores", 601 "PublicDescription": "TOR Inserts : CLFlushOpts issued by iA Cores", 611 "PublicDescription": "TOR Inserts : CRDs issued by iA Cores", 631 "PublicDescription": "TOR Inserts : DRd_Opts issued by iA Cores", 641 "PublicDescription": "TOR Inserts : DRd_Opt_Prefs issued by iA Cores", 646 "BriefDescription": "All locally initiated requests from IA Cores which hit the cache", 652 "PublicDescription": "TOR Inserts : All requests from iA Cores that Hit the LLC", 662 "PublicDescription": "TOR Inserts : CRds issued by iA Cores that Hit the LLC", [all …]
/linux/tools/perf/pmu-events/arch/x86/sierraforest/
H A D	uncore-cache.json	1109 "BriefDescription": "All locally initiated requests from IA Cores", 1115 "PublicDescription": "TOR Inserts : All requests from iA Cores", 1125 "PublicDescription": "TOR Inserts : CLFlushes issued by iA Cores", 1135 "PublicDescription": "TOR Inserts : CLFlushOpts issued by iA Cores", 1145 "PublicDescription": "TOR Inserts : CRDs issued by iA Cores", 1165 "PublicDescription": "TOR Inserts : DRd_Opts issued by iA Cores", 1175 "PublicDescription": "TOR Inserts : DRd_Opt_Prefs issued by iA Cores", 1180 "BriefDescription": "All locally initiated requests from IA Cores which hit the cache", 1186 "PublicDescription": "TOR Inserts : All requests from iA Cores that Hit the LLC", 1196 "PublicDescription": "TOR Inserts : CRds issued by iA Cores that Hit the LLC", [all …]
/linux/tools/perf/pmu-events/arch/x86/broadwellx/
H A D	uncore-power.json	178 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 187 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 196 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 205 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 214 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 223 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 232 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 241 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 250 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 259 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", [all …]
/linux/tools/perf/pmu-events/arch/x86/broadwellde/
H A D	uncore-power.json	178 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 187 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 196 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 205 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 214 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 223 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 232 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 241 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 250 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 259 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", [all …]
/linux/tools/perf/pmu-events/arch/x86/jaketown/
H A D	uncore-power.json	88 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 97 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 106 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 115 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 124 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 133 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 142 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 151 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 232 …igh enough to maintain good IO BW. This is necessary for when all the IA cores on a socket are id… 262 "BriefDescription": "Number of cores in C0", [all …]
/linux/tools/perf/pmu-events/arch/x86/haswellx/
H A D	uncore-power.json	178 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 187 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 196 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 205 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 214 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 223 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 232 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 241 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 250 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 259 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", [all …]
/linux/tools/perf/pmu-events/arch/x86/sandybridge/
H A D	cache.json	407 …clusive, hits to the L3 may require snooping the private L2 caches of any cores on the same socket… 417 …clusive, hits to the L3 may require snooping the private L2 caches of any cores on the same socket… 654 …efetch code reads that hit in the LLC and the snoop to one of the sibling cores hits the line in M… 664 …t needed as either the core-valid bit is not set or the shared line is present in multiple cores.", 674 … & prefetch code reads that hit in the LLC and the snoops sent to sibling cores return clean respo… 704 …efetch data reads that hit in the LLC and the snoop to one of the sibling cores hits the line in M… 714 …emand & prefetch data reads that hit in the LLC and the snoops to sibling cores hit in either E/S … 724 …t needed as either the core-valid bit is not set or the shared line is present in multiple cores.", 734 … & prefetch data reads that hit in the LLC and the snoops sent to sibling cores return clean respo… 754 …efetch code reads that hit in the LLC and the snoop to one of the sibling cores hits the line in M… [all …]
/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/
H A D	uncore-power.json	114 …igh enough to maintain good IO BW. This is necessary for when all the IA cores on a socket are id… 177 "BriefDescription": "Number of cores in C0", 182 …cores in C0 : This is an occupancy event that tracks the number of cores that are in the chosen C-… 186 "BriefDescription": "Number of cores in C3", 192 …cores in C3 : This is an occupancy event that tracks the number of cores that are in the chosen C-… 196 "BriefDescription": "Number of cores in C6", 201 …cores in C6 : This is an occupancy event that tracks the number of cores that are in the chosen C-… 231 … Transition Cycles : Number of cycles spent performing core C state transitions across all cores.",
H A D	uncore-cache.json	59 "PublicDescription": "Core Cross Snoops Issued : Any Cycle with Multiple Snoops : Counts the number of transactions that trigger a configurable number of cross snoops. Cores are snooped if the transaction looks up the cache and determines that it is necessary based on the operation type and what CoreValid bits are set. For example, if 2 CV bits are set on a data read, the cores must have the data in S state so it is not necessary to snoop them. However, if only 1 CV bit is set the core my have modified the data. If the transaction was an RFO, it would need to invalidate the lines. This event can be filtered based on who triggered the initial snoop(s).", 70 "PublicDescription": "Core Cross Snoops Issued : Any Single Snoop : Counts the number of transactions that trigger a configurable number of cross snoops. Cores are snooped if the transaction looks up the cache and determines that it is necessary based on the operation type and what CoreValid bits are set. For example, if 2 CV bits are set on a data read, the cores must have the data in S state so it is not necessary to snoop them. However, if only 1 CV bit is set the core my have modified the data. If the transaction was an RFO, it would need to invalidate the lines. This event can be filtered based on who triggered the initial snoop(s).", 81 "PublicDescription": "Core Cross Snoops Issued : Multiple Core Requests : Counts the number of transactions that trigger a configurable number of cross snoops. Cores are snooped if the transaction looks up the cache and determines that it is necessary based on the operation type and what CoreValid bits are set. For example, if 2 CV bits are set on a data read, the cores must have the data in S state so it is not necessary to snoop them. However, if only 1 CV bit is set the core my have modified the data. If the transaction was an RFO, it would need to invalidate the lines. This event can be filtered based on who triggered the initial snoop(s).", 92 "PublicDescription": "Core Cross Snoops Issued : Single Core Requests : Counts the number of transactions that trigger a configurable number of cross snoops. Cores are snooped if the transaction looks up the cache and determines that it is necessary based on the operation type and what CoreValid bits are set. For example, if 2 CV bits are set on a data read, the cores must have the data in S state so it is not necessary to snoop them. However, if only 1 CV bit is set the core my have modified the data. If the transaction was an RFO, it would need to invalidate the lines. This event can be filtered based on who triggered the initial snoop(s).", 103 "PublicDescription": "Core Cross Snoops Issued : Multiple Eviction : Counts the number of transactions that trigger a configurable number of cross snoops. Cores are snooped if the transaction looks up the cache and determines that it is necessary based on the operation type and what CoreValid bits are set. For example, if 2 CV bits are set on a data read, the cores mus [all...]
/linux/tools/perf/pmu-events/arch/x86/emeraldrapids/
H A D	uncore-power.json	114 …igh enough to maintain good IO BW. This is necessary for when all the IA cores on a socket are id… 177 "BriefDescription": "Number of cores in C0", 182 …cores in C0 : This is an occupancy event that tracks the number of cores that are in the chosen C-… 186 "BriefDescription": "Number of cores in C3", 192 …cores in C3 : This is an occupancy event that tracks the number of cores that are in the chosen C-… 196 "BriefDescription": "Number of cores in C6", 201 …cores in C6 : This is an occupancy event that tracks the number of cores that are in the chosen C-… 231 … Transition Cycles : Number of cycles spent performing core C state transitions across all cores.",
/linux/drivers/accel/rocket/
H A D	rocket_drv.c	23 * schedules jobs to any RKNN cores in the system. 89 rocket_priv->domain = rocket_iommu_domain_create(rdev->cores[0].dev); in rocket_open() 177 rdev->cores[core].rdev = rdev; in rocket_probe() 178 rdev->cores[core].dev = &pdev->dev; in rocket_probe() 179 rdev->cores[core].index = core; in rocket_probe() 183 ret = rocket_core_init(&rdev->cores[core]); in rocket_probe() 206 rocket_core_fini(&rdev->cores[core]); in rocket_remove() 227 if (dev == rdev->cores[core].dev) in find_core_for_dev() 243 err = clk_bulk_prepare_enable(ARRAY_SIZE(rdev->cores[core].clks), rdev->cores[core].clks); in rocket_device_runtime_resume() 260 if (!rocket_job_is_idle(&rdev->cores[core])) in rocket_device_runtime_suspend() [all …]
/linux/tools/perf/pmu-events/arch/x86/snowridgex/
H A D	uncore-power.json	112 …igh enough to maintain good IO BW. This is necessary for when all the IA cores on a socket are id… 185 "BriefDescription": "Number of cores in C-State : C0 and C1", 191 …cores in C-State : C0 and C1 : This is an occupancy event that tracks the number of cores that are… 196 "BriefDescription": "Number of cores in C-State : C3", 202 …cores in C-State : C3 : This is an occupancy event that tracks the number of cores that are in the… 207 "BriefDescription": "Number of cores in C-State : C6 and C7", 213 …cores in C-State : C6 and C7 : This is an occupancy event that tracks the number of cores that are… 244 … Transition Cycles : Number of cycles spent performing core C state transitions across all cores.",
/linux/tools/perf/pmu-events/arch/x86/ivytown/
H A D	uncore-power.json	286 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 295 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 304 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 313 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 322 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 331 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 340 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 349 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 358 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 367 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", [all …]
/linux/tools/perf/pmu-events/arch/x86/icelakex/
H A D	uncore-power.json	113 …igh enough to maintain good IO BW. This is necessary for when all the IA cores on a socket are id… 186 "BriefDescription": "Number of cores in C-State : C0 and C1", 192 …cores in C-State : C0 and C1 : This is an occupancy event that tracks the number of cores that are… 197 "BriefDescription": "Number of cores in C-State : C3", 203 …cores in C-State : C3 : This is an occupancy event that tracks the number of cores that are in the… 208 "BriefDescription": "Number of cores in C-State : C6 and C7", 214 …cores in C-State : C6 and C7 : This is an occupancy event that tracks the number of cores that are… 245 … Transition Cycles : Number of cycles spent performing core C state transitions across all cores.",
H A D	uncore-cache.json	1113 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … 1124 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … 1135 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … 1146 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … 1157 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … 1168 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … 1179 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … 1190 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … 1201 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … 1212 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … [all …]
/linux/arch/mips/include/asm/octeon/
H A D	cvmx-coremask.h	`11 * Module to support operations on bitmap of cores. Coremask can be used to 12 * select a specific core, a group of cores, or all available cores, for 22 * Node 0: Cores 0 - 47 23 * Node 1: Cores 128 - 175 24 * Node 2: Cores 256 - 303 25 * Node 3: Cores 384 - 431`
/linux/arch/x86/kernel/acpi/
H A D	cppc.c	168 * amd_detect_prefcore: Detect if CPUs in the system support preferred cores 171 * Determine whether CPUs in the system support preferred cores. On systems 172 * that support preferred cores, different highest perf values will be found 173 * on different cores. On other systems, the highest perf value will be the 174 * same on all cores. 233 * a CPU. On systems that support preferred cores, this will be a hardcoded 236 * If booting the system with amd-pstate enabled but preferred cores disabled then 238 * even if the preferred cores scheduling hints are not enabled. 253 /* without preferred cores, return the highest perf register value / in amd_get_boost_ratio_numerator() 281 / use the max scale for performance cores */ in amd_get_boost_ratio_numerator() [all …]
/linux/Documentation/networking/device_drivers/can/freescale/
H A D	flexcan.rst	`13 For most flexcan IP cores the driver supports 2 RX modes: 18 The older flexcan cores (integrated into the i.MX25, i.MX28, i.MX35 28 cores come up in a mode where RTR reception is possible. 39 On some IP cores the controller cannot receive RTR frames in the 45 Waive ability to receive RTR frames. (not supported on all IP cores) 48 some IP cores RTR frames cannot be received anymore.`
/linux/tools/perf/pmu-events/arch/x86/cascadelakex/
H A D	uncore-power.json	96 …igh enough to maintain good IO BW. This is necessary for when all the IA cores on a socket are id… 178 "BriefDescription": "Number of cores in C-State; C0 and C1", 184 … that tracks the number of cores that are in the chosen C-State. It can be used by itself to get … 189 "BriefDescription": "Number of cores in C-State; C3", 195 … that tracks the number of cores that are in the chosen C-State. It can be used by itself to get … 200 "BriefDescription": "Number of cores in C-State; C6 and C7", 206 … that tracks the number of cores that are in the chosen C-State. It can be used by itself to get … 237 …PublicDescription": "Number of cycles spent performing core C state transitions across all cores.",
/linux/tools/perf/pmu-events/arch/x86/skylakex/
H A D	uncore-power.json	96 …igh enough to maintain good IO BW. This is necessary for when all the IA cores on a socket are id… 178 "BriefDescription": "Number of cores in C-State; C0 and C1", 184 … that tracks the number of cores that are in the chosen C-State. It can be used by itself to get … 189 "BriefDescription": "Number of cores in C-State; C3", 195 … that tracks the number of cores that are in the chosen C-State. It can be used by itself to get … 200 "BriefDescription": "Number of cores in C-State; C6 and C7", 206 … that tracks the number of cores that are in the chosen C-State. It can be used by itself to get … 237 …PublicDescription": "Number of cycles spent performing core C state transitions across all cores.",
/linux/drivers/phy/broadcom/
H A D	phy-bcm-sr-pcie.c	85 /* PIPEMUX = 3, RC 2x8, cores 0, 7 / 87 / PIPEMUX = 4, RC 4x4, cores 0, 1, 6, 7 / 89 / PIPEMUX = 5, RC 8x2, all 8 cores / 91 / PIPEMUX = 6, RC 3x4 + 2x2, cores 0, 2, 3, 6, 7 / 93 / PIPEMUX = 7, RC 1x4 + 6x2, cores 0, 2, 3, 4, 5, 6, 7 / 95 / PIPEMUX = 8, EP 1x8 + RC 4x2, cores 4, 5, 6, 7 / 97 / PIPEMUX = 9, EP 1x8 + RC 2x4, cores 6, 7 / 99 / PIPEMUX = 10, EP 2x4 + RC 2x4, cores 1, 6 / 101 / PIPEMUX = 11, EP 2x4 + RC 4x2, cores 2, 3, 4, 5 / 103 / PIPEMUX = 12, EP 1x4 + RC 6x2, cores 2, 3, 4, 5, 6, 7 */ [all …]
/linux/arch/riscv/
H A D	Kconfig.errata	`9 here if your platform uses Andes CPU cores. 20 non-standard handling on non-coherent operations on Andes cores. 30 here if your platform uses MIPS CPU cores. 53 here if your platform uses SiFive CPU cores. 105 here if your platform uses T-HEAD CPU cores. 138 The T-Head C9xx cores implement a PMU overflow extension very 151 The T-Head C9xx cores have a vulnerability in the xtheadvector`
/linux/arch/arm/boot/dts/arm/
H A D	vexpress-v2p-ca15-tc1.dts	`199 regulator-cores { 203 regulator-name = "Cores"; 207 label = "Cores"; 210 amp-cores { 211 /* Total current for the two cores */ 214 label = "Cores"; 224 power-cores { 228 label = "Cores"; 235 label = "Cores";`
/linux/Documentation/devicetree/bindings/media/xilinx/
H A D	video.txt	`1 DT bindings for Xilinx video IP cores 4 Xilinx video IP cores process video streams by acting as video sinks and/or 10 cores are represented as defined in ../video-interfaces.txt. 18 The following properties are common to all Xilinx video IP cores. 21 AXI bus between video IP cores, using its VF code as defined in "AXI4-Stream`

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