Home
last modified time | relevance | path

Searched full:cpu0 (Results 1 – 25 of 722) sorted by relevance

12345678910>>...29

/Linux-v5.10/tools/power/x86/turbostat/
Dturbostat.8183 Notice that cpu4's HT sibling is cpu0, which is under 1% busy, but can get into CPU%c1 only,
222 cpu0: MSR_IA32_ENERGY_PERF_BIAS: 0x00000006 (balanced)
223 cpu0: MSR_CORE_PERF_LIMIT_REASONS, 0x31200000 (Active: ) (Logged: Transitions, MultiCoreTurbo, Amps…
224 cpu0: MSR_GFX_PERF_LIMIT_REASONS, 0x00000000 (Active: ) (Logged: )
225 cpu0: MSR_RING_PERF_LIMIT_REASONS, 0x0d000000 (Active: ) (Logged: Amps, PkgPwrL1, PkgPwrL2, )
226 cpu0: MSR_RAPL_POWER_UNIT: 0x000a0e03 (0.125000 Watts, 0.000061 Joules, 0.000977 sec.)
227 cpu0: MSR_PKG_POWER_INFO: 0x000002a0 (84 W TDP, RAPL 0 - 0 W, 0.000000 sec.)
228 cpu0: MSR_PKG_POWER_LIMIT: 0x428348001a82a0 (UNlocked)
229 cpu0: PKG Limit #1: ENabled (84.000000 Watts, 8.000000 sec, clamp DISabled)
230 cpu0: PKG Limit #2: ENabled (105.000000 Watts, 0.002441* sec, clamp DISabled)
[all …]
/Linux-v5.10/arch/arm/boot/dts/
Dexynos5422-odroidhc1.dts31 cpu0_thermal: cpu0-thermal {
59 cooling-device = <&cpu0 0 2>,
75 cooling-device = <&cpu0 3 8>,
108 cooling-device = <&cpu0 0 2>,
119 cooling-device = <&cpu0 3 8>,
152 cooling-device = <&cpu0 0 2>,
163 cooling-device = <&cpu0 3 8>,
196 cooling-device = <&cpu0 0 2>,
207 cooling-device = <&cpu0 3 8>,
Daspeed-bmc-opp-zaius.dts313 /* CPU0 PRM 0.7V */
314 /* CPU0 PRM 1.2V CH03 */
315 /* CPU0 PRM 0.8V */
316 /* CPU0 PRM 1.2V CH47 */
372 /* Master selector PCA9541A @70h (other master: CPU0)
393 /* CPU0 VR ISL68137 0.7V, 0.96V PMBUS @64h */
394 /* CPU0 VR ISL68137 1.2V CH03 PMBUS @40h */
395 /* CPU0 VR ISL68137 0.8V PMBUS @60h */
396 /* CPU0 VR 1.0V IR38064 I2C @11h, PMBUS @43h */
397 /* CPU0 VR ISL68137 1.2V CH47 PMBUS @41h */
[all …]
Dexynos5422-odroidxu3-lite.dts48 cooling-device = <&cpu0 3 7>,
59 cooling-device = <&cpu0 3 7>,
70 cooling-device = <&cpu0 3 7>,
81 cooling-device = <&cpu0 3 7>,
Dexynos5420-arndale-octa.dts63 &cpu0 {
102 cooling-device = <&cpu0 0 2>,
118 cooling-device = <&cpu0 3 6>,
134 cooling-device = <&cpu0 6 11>,
173 cooling-device = <&cpu0 0 2>,
185 cooling-device = <&cpu0 3 6>,
197 cooling-device = <&cpu0 6 11>,
236 cooling-device = <&cpu0 0 2>,
248 cooling-device = <&cpu0 3 6>,
260 cooling-device = <&cpu0 6 11>,
[all …]
Dexynos5422-odroidxu3-common.dtsi52 cpu0_thermal: cpu0-thermal {
114 cooling-device = <&cpu0 0 2>,
130 cooling-device = <&cpu0 3 8>,
192 cooling-device = <&cpu0 0 2>,
203 cooling-device = <&cpu0 3 8>,
265 cooling-device = <&cpu0 0 2>,
276 cooling-device = <&cpu0 3 8>,
338 cooling-device = <&cpu0 0 2>,
349 cooling-device = <&cpu0 3 8>,
Drk3288-veyron-mickey.dts90 cooling-device = <&cpu0 THERMAL_NO_LIMIT 4>,
118 cooling-device = <&cpu0 5 6>, <&cpu1 5 6>, <&cpu2 5 6>,
123 cooling-device = <&cpu0 7 7>, <&cpu1 7 7>, <&cpu2 7 7>,
128 cooling-device = <&cpu0 7 8>, <&cpu1 7 8>, <&cpu2 7 8>,
133 cooling-device = <&cpu0 8 THERMAL_NO_LIMIT>,
194 cooling-device = <&cpu0 4 4>,
/Linux-v5.10/tools/memory-model/Documentation/
Drecipes.txt73 void CPU0(void)
89 The basic rule guarantees that if CPU0() acquires mylock before CPU1(),
99 void CPU0(void)
115 This converse to the basic rule guarantees that if CPU0() acquires
130 void CPU0(void)
163 void CPU0(void)
220 void CPU0(void)
255 void CPU0(void)
296 void CPU0(void)
364 void CPU0(void)
[all …]
/Linux-v5.10/Documentation/scheduler/
Dsched-capacity.rst60 - work_per_hz(CPU0) = W
66 - capacity(CPU0) = C
69 To draw the parallel with Arm big.LITTLE, CPU0 would be a big while CPU1 would
75 CPU0 work ^
85 CPU0 has the highest capacity in the system (C), and completes a fixed amount of
87 CPU0, and thus only completes W/2 in T.
95 - max_freq(CPU0) = F
100 - capacity(CPU0) = C
106 CPU0 work ^
189 - capacity(CPU0) = C
[all …]
Dsched-energy.rst152 composed of two CPUs each. CPU0 and CPU1 are little CPUs; CPU2 and CPU3
179 CPU0 CPU1 CPU2 CPU3
188 compared to leaving P on CPU0. EAS assumes that OPPs follow utilization
197 768 ============= * CPU0: 200 / 341 * 150 = 88
207 CPU0 CPU1 CPU2 CPU3
215 768 ============= * CPU0: 200 / 341 * 150 = 88
225 CPU0 CPU1 CPU2 CPU3
233 768 ============= * CPU0: 400 / 512 * 300 = 234
243 CPU0 CPU1 CPU2 CPU3
/Linux-v5.10/tools/virtio/virtio-trace/
DREADME63 -chardev pipe,id=charchannel1,path=/tmp/virtio-trace/trace-path-cpu0\
65 id=channel1,name=trace-path-cpu0\
77 <source path='/tmp/virtio-trace/trace-path-cpu0'/>
78 <target type='virtio' name='trace-path-cpu0'/>
83 example, if a guest use three CPUs, chardev names should be trace-path-cpu0,
107 # cat /tmp/virtio-trace/trace-path-cpu0.out
/Linux-v5.10/Documentation/devicetree/bindings/clock/
Dmvebu-core-clock.txt42 1 = cpuclk (CPU0 clock)
43 2 = l2clk (L2 Cache clock derived from CPU0 clock)
44 3 = ddrclk (DDR controller clock derived from CPU0 clock)
48 1 = cpuclk (CPU0 clock)
49 2 = ddrclk (DDR controller clock derived from CPU0 clock)
/Linux-v5.10/arch/x86/power/
Dcpu.c330 pr_warn("CPU0 is offline.\n"); in bsp_check()
350 * When system resumes from hibernation, online CPU0 because in bsp_pm_callback()
363 * call _debug_hotplug_cpu() to restore to CPU0's state prior to in bsp_pm_callback()
366 * This works for normal boot case in our CPU0 hotplug debug in bsp_pm_callback()
367 * mode, i.e. CPU0 is offline and user mode hibernation in bsp_pm_callback()
370 * If CPU0 is online and user application accesses snapshot in bsp_pm_callback()
371 * device after boot time, this will offline CPU0 and user may in bsp_pm_callback()
372 * see different CPU0 state before and after accessing in bsp_pm_callback()
374 * user debugging CPU0 hotplug. Even if users hit this case, in bsp_pm_callback()
375 * they can easily online CPU0 back. in bsp_pm_callback()
[all …]
/Linux-v5.10/Documentation/core-api/irq/
Dirq-affinity.rst21 Here is an example of restricting IRQ44 (eth1) to CPU0-3 then restricting
38 CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7
57 CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7
61 i.e counters for the CPU0-3 did not change.
/Linux-v5.10/arch/arm64/boot/dts/amlogic/
Dmeson-g12b.dtsi19 cpu = <&cpu0>;
46 cpu0: cpu@0 { label
120 cooling-device = <&cpu0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
129 cooling-device = <&cpu0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
Dmeson-g12a.dtsi15 cpu0: cpu@0 { label
121 cooling-device = <&cpu0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
129 cooling-device = <&cpu0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
/Linux-v5.10/tools/power/cpupower/bench/
Dcpufreq-bench_script.sh30 echo $up_threshold >/sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold
31 echo $sampling_rate >/sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate
32 up_threshold_set=$(cat /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold)
33 sampling_rate_set=$(cat /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate)
/Linux-v5.10/Documentation/devicetree/bindings/thermal/
Dthermal-cooling-devices.yaml59 // Example 1: Cpufreq cooling device on CPU0
64 CPU0: cpu@0 {
93 cpu0-thermal {
111 cooling-device = <&CPU0 5 5>;
/Linux-v5.10/arch/arm/mach-omap2/
Dcpuidle44xx.c128 * CPU0 has to wait and stay ON until CPU1 is OFF state. in omap_enter_idle_coupled()
239 /* C1 - CPU0 ON + CPU1 ON + MPU ON */
247 /* C2 - CPU0 OFF + CPU1 OFF + MPU CSWR */
256 /* C3 - CPU0 OFF + CPU1 OFF + MPU OSWR */
274 /* C1 - CPU0 ON + CPU1 ON + MPU ON */
282 /* C2 - CPU0 RET + CPU1 RET + MPU CSWR */
Domap-mpuss-lowpower.c10 * CPU0 and CPU1 LPRM modules.
11 * CPU0, CPU1 and MPUSS each have there own power domain and
14 * The CPU0 and CPU1 can't support Closed switch Retention (CSWR)
23 * CPU0 CPU1 MPUSS
32 * Note: CPU0 is the master core and it is the last CPU to go down
114 * Program the wakeup routine address for the CPU0 and CPU1
378 pr_err("Lookup failed for CPU0 pwrdm\n"); in omap4_mpuss_init()
386 /* Initialise CPU0 power domain state to ON */ in omap4_mpuss_init()
Domap-smp.c150 * OMAP44XX EMU/HS devices - CPU0 SMP bit access is enabled in PPA in omap4_secondary_init()
151 * init and for CPU1, a secure PPA API provided. CPU0 must be ON in omap4_secondary_init()
201 * wake-up. To wakeup CPU1, CPU0 forces the CPU1 clockdomain to in omap4_boot_secondary()
206 * 4.3.4.2 Power States of CPU0 and CPU1 in omap4_boot_secondary()
217 * GIC restoration will cause a problem to CPU0 Non-Secure SW. in omap4_boot_secondary()
219 * 1) Before doing the CPU1 wakeup, CPU0 must disable in omap4_boot_secondary()
/Linux-v5.10/tools/testing/selftests/ftrace/test.d/00basic/
Dringbuffer_size.tc19 if [ -d per_cpu/cpu0 ]; then
20 cd per_cpu/cpu0
/Linux-v5.10/Documentation/cpu-freq/
Dcpufreq-stats.rst48 <mysystem>:/sys/devices/system/cpu/cpu0/cpufreq/stats # ls -l
73 <mysystem>:/sys/devices/system/cpu/cpu0/cpufreq/stats # cat time_in_state
89 <mysystem>:/sys/devices/system/cpu/cpu0/cpufreq/stats # cat total_trans
108 <mysystem>:/sys/devices/system/cpu/cpu0/cpufreq/stats # cat trans_table
/Linux-v5.10/arch/arm64/boot/dts/marvell/
Darmada-ap80x.dtsi329 ap_thermal_cpu0: ap-thermal-cpu0 {
336 cpu0_hot: cpu0-hot {
341 cpu0_emerg: cpu0-emerg {
351 cooling-device = <&cpu0 1 2>,
356 cooling-device = <&cpu0 3 3>,
384 cooling-device = <&cpu0 1 2>,
389 cooling-device = <&cpu0 3 3>,
/Linux-v5.10/Documentation/core-api/
Dcpu_hotplug.rst54 Allow to shutdown CPU0.
100 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu0
128 The CPU is usable again. This should work on all CPUs. CPU0 is often special
131 shutdown CPU0. Alternatively the kernel command option *cpu0_hotplug* can be
132 used. Some known dependencies of CPU0:
134 * Resume from hibernate/suspend. Hibernate/suspend will fail if CPU0 is offline.
135 * PIC interrupts. CPU0 can't be removed if a PIC interrupt is detected.
138 on CPU0.

12345678910>>...29