|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v2 03/10] xen/arm: Implement CPU_OFF PSCI call (physical interface)
Hi Mirela, On 20/04/18 13:25, Mirela Simonovic wrote: During the system suspend to RAM non-boot CPUs will be hotplugged. This will be triggered via disable_nonboot_cpus() call. When hotplugged the CPU will end up in an infinite wfi loop in stop_cpu(). This patch adds PSCI CPU_OFF call to the EL3 with the aim to get powered down the calling CPU during the suspend. If PSCI CPU_OFF call to the EL3 succeeds it will not return. Otherwise, when the PSCI CPU_OFF call returns we'll raise panic, because the calling CPU could be enabled afterwards. If a CPU executes stop_cpu() when the system is not suspending the calling CPU will loop in the infinite while/wfi, as it was looping before this change. Note that there is no check for PSCI version in PSCI CPU_OFF implementation because the version will be checked prior to triggering the system suspend. Then the code should contain an ASSERT + comment to make it clear on the interface. But I don't think this is the right way to go (see below).
CPU_OFF will only return on error. So the if is not necessary below. I don't think this should be call only on suspend/resume. System shutdown could also benefit of PSCI CPU off. This is also paving the way to more use case of turning off a CPU. Cheers, -- Julien Grall _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |