From: David Woodhouse <[email protected]> A new plane vCPU for an AP starts, like any non-boot x86 vCPU, in the uninitialised wait-for-INIT state, and nothing ever sends INIT/SIPI to the higher plane of an AP. The VMM placing an initial VTL context on it has to mark it runnable itself.
Signed-off-by: David Woodhouse <[email protected]> Assisted-by: LLM --- arch/x86/kvm/x86.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c index ca5d8e081fdc..970c738558f2 100644 --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@ -6278,6 +6278,8 @@ bool kvm_arch_is_vcpu_plane_ioctl(unsigned ioctl) case KVM_SET_ONE_REG: case KVM_GET_SREGS2: case KVM_SET_SREGS2: + case KVM_GET_MP_STATE: + case KVM_SET_MP_STATE: case KVM_GET_VCPU_EVENTS: case KVM_SET_VCPU_EVENTS: case KVM_GET_XCRS: -- 2.50.1
