From: David Woodhouse <[email protected]> A fast hypercall may return its output in XMM registers when the hypervisor reports HV_X64_HYPERCALL_XMM_OUTPUT_AVAILABLE, and Windows only uses those forms when the bit is set. KVM does not report it in KVM_GET_SUPPORTED_HV_CPUID, although nothing stops a VMM handling a forwarded fast hypercall from writing its output through the vCPU FPU state before resuming the vCPU.
Report the bit. None of the hypercalls KVM implements itself returns output, so it only matters for hypercalls the VMM handles, where the VMM writes the output registers. Signed-off-by: David Woodhouse <[email protected]> --- arch/x86/kvm/hyperv.c | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c index 858ee0f374e5..e0d9b2b1302d 100644 --- a/arch/x86/kvm/hyperv.c +++ b/arch/x86/kvm/hyperv.c @@ -2870,6 +2870,7 @@ int kvm_get_hv_cpuid(struct kvm_vcpu *vcpu, struct kvm_cpuid2 *cpuid, ent->ebx |= HV_ENABLE_EXTENDED_HYPERCALLS; ent->edx |= HV_X64_HYPERCALL_XMM_INPUT_AVAILABLE; + ent->edx |= HV_X64_HYPERCALL_XMM_OUTPUT_AVAILABLE; ent->edx |= HV_FEATURE_FREQUENCY_MSRS_AVAILABLE; ent->edx |= HV_FEATURE_GUEST_CRASH_MSR_AVAILABLE; -- 2.50.1
