/openbmc/qemu/tests/unit/ |
H A D | test-smp-parse.c | 30 * -sockets/cores/threads 36 .has_cores = hc, .cores = c, \ 45 .cores = c, \ 52 * -sockets/dies/modules/cores/threads 61 .has_cores = he, .cores = e, \ 68 * -sockets/clusters/cores/threads 75 .has_cores = hd, .cores = d, \ 82 * -drawers/books/sockets/cores/threads 91 .has_cores = he, .cores = e, \ 99 * -drawers/books/sockets/dies/clusters/modules/cores/threads [all …]
|
/openbmc/qemu/hw/core/ |
H A D | machine-smp.c | 58 g_string_append_printf(s, " * cores (%u)", ms->smp.cores); in cpu_hierarchy_to_string() 68 * Any missing parameter in "cpus/maxcpus/sockets/cores/threads" will be 71 * In the calculation of omitted sockets/cores/threads: we prefer sockets 72 * over cores over threads before 6.2, while preferring cores over sockets 96 unsigned cores = config->has_cores ? config->cores : 0; in machine_parse_smp_config() local 112 (config->has_cores && config->cores == 0) || in machine_parse_smp_config() 167 cores = cores > 0 ? cores : 1; in machine_parse_smp_config() 173 /* prefer sockets over cores before 6.2 */ in machine_parse_smp_config() 175 cores = cores > 0 ? cores : 1; in machine_parse_smp_config() 179 modules * cores * threads); in machine_parse_smp_config() [all …]
|
/openbmc/u-boot/arch/arm/cpu/armv8/fsl-layerscape/ |
H A D | mp.c | 77 u32 cores, cpu_up_mask = 1; in fsl_layerscape_wake_seconday_cores() local 82 /* update for secondary cores */ in fsl_layerscape_wake_seconday_cores() 88 cores = cpu_mask(); in fsl_layerscape_wake_seconday_cores() 97 printf("Waking secondary cores to start from %lx\n", gd->relocaddr); in fsl_layerscape_wake_seconday_cores() 108 rst->brrl = cores; in fsl_layerscape_wake_seconday_cores() 112 * Release the cores out of reset one-at-a-time to avoid in fsl_layerscape_wake_seconday_cores() 140 gur_out32(&gur->brrl, cores); in fsl_layerscape_wake_seconday_cores() 143 /* Bootup online cores */ in fsl_layerscape_wake_seconday_cores() 144 scfg_out32(&scfg->corebcr, cores); in fsl_layerscape_wake_seconday_cores() 148 * cores then the pre-bootloader code will trap them in a "wfe" unless in fsl_layerscape_wake_seconday_cores() [all …]
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/broadwellx/ |
H A D | uncore-power.json | 158 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 166 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 174 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 182 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 190 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 198 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 206 …"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", 222 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 230 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", [all …]
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/broadwellde/ |
H A D | uncore-power.json | 158 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 166 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 174 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 182 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 190 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 198 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 206 …"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", 222 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 230 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", [all …]
|
/openbmc/linux/sound/soc/intel/skylake/ |
H A D | skl-sst-dsp.c | 31 * successful first boot. Hence core 0 will be running and other cores 39 skl->cores.state[SKL_DSP_CORE0_ID] = SKL_DSP_RUNNING; in skl_dsp_init_core_state() 40 skl->cores.usage_count[SKL_DSP_CORE0_ID] = 1; in skl_dsp_init_core_state() 42 for (i = SKL_DSP_CORE0_ID + 1; i < skl->cores.count; i++) { in skl_dsp_init_core_state() 43 skl->cores.state[i] = SKL_DSP_RESET; in skl_dsp_init_core_state() 44 skl->cores.usage_count[i] = 0; in skl_dsp_init_core_state() 48 /* Get the mask for all enabled cores */ 55 core_mask = SKL_DSP_CORES_MASK(skl->cores.count); in skl_dsp_get_enabled_cores() 59 /* Cores having CPA bit set */ in skl_dsp_get_enabled_cores() 63 /* And cores having CRST bit cleared */ in skl_dsp_get_enabled_cores() [all …]
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
H A D | OperatingConfig.v1_0_4.json | 36 "description": "The clock speed for a set of cores.", 37 "longDescription": "This type shall specify the clock speed for a set of cores.", 54 "description": "The clock speed to configure the set of cores in MHz.", 55 …gDescription": "This property shall contain the clock speed to configure the set of cores in MHz.", 65 "description": "The number of cores to configure with a specified speed.", 66 …"longDescription": "This property shall contain the number of cores to configure with the speed sp… 75 … "description": "The identifier of the cores to configure with the specified speed.", 82 …"longDescription": "This property shall contain an array identifying the cores to configure with t… 158 … "description": "The clock speed for sets of cores when the configuration is operational.", 169 …hall contain an array of objects that specify the clock speed for sets of cores when the configura… [all …]
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
H A D | OperatingConfig.v1_0_4.json | 36 "description": "The clock speed for a set of cores.", 37 "longDescription": "This type shall specify the clock speed for a set of cores.", 54 "description": "The clock speed to configure the set of cores in MHz.", 55 …gDescription": "This property shall contain the clock speed to configure the set of cores in MHz.", 65 "description": "The number of cores to configure with a specified speed.", 66 …"longDescription": "This property shall contain the number of cores to configure with the speed sp… 75 … "description": "The identifier of the cores to configure with the specified speed.", 82 …"longDescription": "This property shall contain an array identifying the cores to configure with t… 158 … "description": "The clock speed for sets of cores when the configuration is operational.", 169 …hall contain an array of objects that specify the clock speed for sets of cores when the configura… [all …]
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | lockup-watchdogs.rst | 67 By default, the watchdog runs on all online cores. However, on a 69 on the housekeeping cores, not the cores specified in the "nohz_full" 71 the "nohz_full" cores, we would have to run timer ticks to activate 73 from protecting the user code on those cores from the kernel. 74 Of course, disabling it by default on the nohz_full cores means that 75 when those cores do enter the kernel, by default we will not be 77 to continue to run on the housekeeping (non-tickless) cores means 78 that we will continue to detect lockups properly on those cores. 80 In either case, the set of cores excluded from running the watchdog 82 nohz_full cores, this may be useful for debugging a case where the [all …]
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/jaketown/ |
H A D | uncore-power.json | 78 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 86 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 94 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 102 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 110 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 118 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 126 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 134 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 206 …igh enough to maintain good IO BW. This is necessary for when all the IA cores on a socket are id… 233 "BriefDescription": "Number of cores in C0", [all …]
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/haswellx/ |
H A D | uncore-power.json | 158 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 166 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 174 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 182 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 190 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 198 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 206 …"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", 222 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 230 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", [all …]
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/sandybridge/ |
H A D | cache.json | 357 …clusive, hits to the L3 may require snooping the private L2 caches of any cores on the same socket… 366 …clusive, hits to the L3 may require snooping the private L2 caches of any cores on the same socket… 577 …efetch code reads that hit in the LLC and the snoop to one of the sibling cores hits the line in M… 586 …t needed as either the core-valid bit is not set or the shared line is present in multiple cores.", 595 … & prefetch code reads that hit in the LLC and the snoops sent to sibling cores return clean respo… 622 …efetch data reads that hit in the LLC and the snoop to one of the sibling cores hits the line in M… 631 …emand & prefetch data reads that hit in the LLC and the snoops to sibling cores hit in either E/S … 640 …t needed as either the core-valid bit is not set or the shared line is present in multiple cores.", 649 … & prefetch data reads that hit in the LLC and the snoops sent to sibling cores return clean respo… 667 …efetch code reads that hit in the LLC and the snoop to one of the sibling cores hits the line in M… [all …]
|
/openbmc/qemu/tests/qtest/ |
H A D | cpu-plug-test.c | 21 unsigned cores; member 38 "-smp 1,sockets=%u,cores=%u,threads=%u,maxcpus=%u", in test_plug_with_device_add() 40 td->sockets, td->cores, td->threads, td->maxcpus); in test_plug_with_device_add() 95 data->cores = 3; in add_pc_test_case() 97 data->maxcpus = data->sockets * data->cores * data->threads; in add_pc_test_case() 100 mname, data->sockets, data->cores, in add_pc_test_case() 121 data->cores = 3; in add_pseries_test_case() 123 data->maxcpus = data->sockets * data->cores * data->threads; in add_pseries_test_case() 126 mname, data->sockets, data->cores, in add_pseries_test_case() 147 data->cores = 3; in add_s390x_test_case() [all …]
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
H A D | uncore-power.json | 91 …igh enough to maintain good IO BW. This is necessary for when all the IA cores on a socket are id… 142 "BriefDescription": "Number of cores in C0", 146 …cores in C0 : This is an occupancy event that tracks the number of cores that are in the chosen C-… 150 "BriefDescription": "Number of cores in C3", 154 …cores in C3 : This is an occupancy event that tracks the number of cores that are in the chosen C-… 158 "BriefDescription": "Number of cores in C6", 162 …cores in C6 : This is an occupancy event that tracks the number of cores that are in the chosen C-… 186 … Transition Cycles : Number of cycles spent performing core C state transitions across all cores.",
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/icelakex/ |
H A D | uncore-power.json | 90 …igh enough to maintain good IO BW. This is necessary for when all the IA cores on a socket are id… 149 "BriefDescription": "Number of cores in C-State : C0 and C1", 153 …cores in C-State : C0 and C1 : This is an occupancy event that tracks the number of cores that are… 157 "BriefDescription": "Number of cores in C-State : C3", 161 …cores in C-State : C3 : This is an occupancy event that tracks the number of cores that are in the… 165 "BriefDescription": "Number of cores in C-State : C6 and C7", 169 …cores in C-State : C6 and C7 : This is an occupancy event that tracks the number of cores that are… 193 … Transition Cycles : Number of cycles spent performing core C state transitions across all cores.",
|
H A D | uncore-cache.json | 911 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … 920 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … 929 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … 938 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … 947 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … 956 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … 965 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … 974 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … 983 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … 992 …Cores are snooped if the transaction looks up the cache and determines that it is necessary based … [all …]
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/snowridgex/ |
H A D | uncore-power.json | 89 …igh enough to maintain good IO BW. This is necessary for when all the IA cores on a socket are id… 148 "BriefDescription": "Number of cores in C-State : C0 and C1", 152 …cores in C-State : C0 and C1 : This is an occupancy event that tracks the number of cores that are… 156 "BriefDescription": "Number of cores in C-State : C3", 160 …cores in C-State : C3 : This is an occupancy event that tracks the number of cores that are in the… 164 "BriefDescription": "Number of cores in C-State : C6 and C7", 168 …cores in C-State : C6 and C7 : This is an occupancy event that tracks the number of cores that are… 192 … Transition Cycles : Number of cycles spent performing core C state transitions across all cores.",
|
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
H A D | OperatingConfig_v1.xml | 72 …<Annotation Term="OData.Description" String="The number of cores in the processor that can be conf… 73 …"OData.LongDescription" String="This property shall contain the number of cores in the processor t… 104 …<Annotation Term="OData.Description" String="The clock speed for sets of cores when the configurat… 105 …hall contain an array of objects that specify the clock speed for sets of cores when the configura… 108 …. A turbo profile is the maximum turbo clock speed as a function of the number of active cores."/> 109 …erty shall contain an array of objects that specify the turbo profile for a set of active cores."/> 119 <Annotation Term="OData.Description" String="The turbo profile for a set of active cores."/> 120 …ta.LongDescription" String="This type shall specify the turbo profile for a set of active cores."/> 123 …<Annotation Term="OData.Description" String="The number of active cores to be configured with the … 124 …"OData.LongDescription" String="This property shall contain the number of cores to be configured w… [all …]
|
/openbmc/bmcweb/redfish-core/schema/dmtf/installed/ |
H A D | OperatingConfig_v1.xml | 72 …<Annotation Term="OData.Description" String="The number of cores in the processor that can be conf… 73 …"OData.LongDescription" String="This property shall contain the number of cores in the processor t… 104 …<Annotation Term="OData.Description" String="The clock speed for sets of cores when the configurat… 105 …hall contain an array of objects that specify the clock speed for sets of cores when the configura… 108 …. A turbo profile is the maximum turbo clock speed as a function of the number of active cores."/> 109 …erty shall contain an array of objects that specify the turbo profile for a set of active cores."/> 119 <Annotation Term="OData.Description" String="The turbo profile for a set of active cores."/> 120 …ta.LongDescription" String="This type shall specify the turbo profile for a set of active cores."/> 123 …<Annotation Term="OData.Description" String="The number of active cores to be configured with the … 124 …"OData.LongDescription" String="This property shall contain the number of cores to be configured w… [all …]
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/ivytown/ |
H A D | uncore-power.json | 254 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 262 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 270 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 278 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 286 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 294 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 302 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 310 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 318 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", 326 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion", [all …]
|
/openbmc/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
|
/openbmc/linux/drivers/remoteproc/ |
H A D | ti_k3_r5_remoteproc.c | 105 * @cores: list of R5 cores within the cluster 112 struct list_head cores; member 299 /* assert local reset on all applicable cores */ in k3_r5_lockstep_reset() 300 list_for_each_entry(core, &cluster->cores, elem) { in k3_r5_lockstep_reset() 310 /* disable PSC modules on all applicable cores */ in k3_r5_lockstep_reset() 311 list_for_each_entry(core, &cluster->cores, elem) { in k3_r5_lockstep_reset() 324 list_for_each_entry_continue_reverse(core, &cluster->cores, elem) { in k3_r5_lockstep_reset() 329 core = list_last_entry(&cluster->cores, struct k3_r5_core, elem); in k3_r5_lockstep_reset() 331 list_for_each_entry_from_reverse(core, &cluster->cores, elem) { in k3_r5_lockstep_reset() 344 /* enable PSC modules on all applicable cores */ in k3_r5_lockstep_release() [all …]
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/skylakex/ |
H A D | uncore-power.json | 76 …igh enough to maintain good IO BW. This is necessary for when all the IA cores on a socket are id… 142 "BriefDescription": "Number of cores in C-State; C0 and C1", 146 … that tracks the number of cores that are in the chosen C-State. It can be used by itself to get … 150 "BriefDescription": "Number of cores in C-State; C3", 154 … that tracks the number of cores that are in the chosen C-State. It can be used by itself to get … 158 "BriefDescription": "Number of cores in C-State; C6 and C7", 162 … that tracks the number of cores that are in the chosen C-State. It can be used by itself to get … 186 …PublicDescription": "Number of cycles spent performing core C state transitions across all cores.",
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/cascadelakex/ |
H A D | uncore-power.json | 76 …igh enough to maintain good IO BW. This is necessary for when all the IA cores on a socket are id… 142 "BriefDescription": "Number of cores in C-State; C0 and C1", 146 … that tracks the number of cores that are in the chosen C-State. It can be used by itself to get … 150 "BriefDescription": "Number of cores in C-State; C3", 154 … that tracks the number of cores that are in the chosen C-State. It can be used by itself to get … 158 "BriefDescription": "Number of cores in C-State; C6 and C7", 162 … that tracks the number of cores that are in the chosen C-State. It can be used by itself to get … 186 …PublicDescription": "Number of cycles spent performing core C state transitions across all cores.",
|
/openbmc/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.
|