Vitaly Kuznetsov 8f014550df KVM: x86: hyper-v: Make Hyper-V emulation enablement conditional ... Hyper-V emulation is enabled in KVM unconditionally. This is bad at least from security standpoint as it is an extra attack surface. Ideally, there should be a per-VM capability explicitly enabled by VMM but currently it is not the case and we can't mandate one without breaking backwards compatibility. We can, however, check guest visible CPUIDs and only enable Hyper-V emulation when "Hv#1" interface was exposed in HYPERV_CPUID_INTERFACE. Note, VMMs are free to act in any sequence they like, e.g. they can try to set MSRs first and CPUIDs later so we still need to allow the host to read/write Hyper-V specific MSRs unconditionally. Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com> Message-Id: <20210126134816.1880136-14-vkuznets@redhat.com> [Add selftest vcpu_set_hv_cpuid API to avoid breaking xen_vmcall_test. - Paolo] Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>		2021-02-09 08:39:56 -05:00
..
processor.h	KVM: x86: hyper-v: Make Hyper-V emulation enablement conditional	2021-02-09 08:39:56 -05:00
svm_util.h	KVM: selftests: do not substitute SVM/VMX check with KVM_CAP_NESTED_STATE check	2020-06-11 12:35:17 -04:00
svm.h	selftests: KVM: AMD Nested test infrastructure	2020-02-12 20:09:39 +01:00
vmx.h	KVM: selftests: Verify supported CR4 bits can be set before KVM_SET_CPUID2	2020-11-15 09:49:08 -05:00