|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH v1 3/4] arm/sysctl: Implement cpu hotplug ops
Hi Mykyta, On 18/09/2025 13:16, Mykyta Poturai wrote: Implement XEN_SYSCTL_CPU_HOTPLUG_* calls to allow for enabling/disabling CPU cores in runtime. Signed-off-by: Mykyta Poturai <mykyta_poturai@xxxxxxxx> --- xen/arch/arm/sysctl.c | 67 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 67 insertions(+) diff --git a/xen/arch/arm/sysctl.c b/xen/arch/arm/sysctl.c index 32cab4feff..ca8fb550fd 100644 --- a/xen/arch/arm/sysctl.c +++ b/xen/arch/arm/sysctl.c @@ -12,6 +12,7 @@ #include <xen/dt-overlay.h> #include <xen/errno.h> #include <xen/hypercall.h> +#include <xen/cpu.h> #include <asm/arm64/sve.h> #include <public/sysctl.h>@@ -23,6 +24,68 @@ void arch_do_physinfo(struct xen_sysctl_physinfo *pi) Looking at the code, you will effectively disable all the CPUs but CPU0. But I don't understand why. From the name is goal seems to be disable SMT threading. Regardless what I wrote above, you likely want to handle preemption. + if ( ret ) + return ret; > + } I can't find a similar check on x86. Do you have any pointer? + return -EINVAL; On x86, they seem to check for XSM permission before continuing. Can you explain why this is not necessary? Same questions applies below. + return continue_hypercall_on_cpu(0, cpu_up_helper, _p(hotplug->cpu)); + + case XEN_SYSCTL_CPU_HOTPLUG_OFFLINE: + if ( hotplug->cpu == 0 ) + return -EINVAL; + return continue_hypercall_on_cpu(0, cpu_down_helper, _p(hotplug->cpu)); + + case XEN_SYSCTL_CPU_HOTPLUG_SMT_ENABLE: + case XEN_SYSCTL_CPU_HOTPLUG_SMT_DISABLE: Why are we implementing those helpers on Arm? This will also enable CPU hotplug on 32-bit Arm. Is this what you intended? (I see patch #4 only mention 64-bit Arm). Cheers, -- Julien Grall
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |