Support multiple KVM modules on the same host
Subsystems (4)
cover Support multiple KVM modules on the same host
This series is a rough, PoC-quality RFC to allow (un)loading and running multiple KVM modules simultaneously on a single host, e.g. to deploy fixes, mitigations, and/or new features without having to drain all VMs from the host. Multi-KVM will also allow running the "same" KVM module with different params, e.g. to run trusted VMs with different mitigations.
The goal of this RFC is to get feedback on the idea itself and the high-level approach. In particular, we're looking for input on:
- Combining kvm_intel.ko and kvm_amd.ko into kvm.ko
- Exposing multiple /dev/kvmX devices via Kconfig
- The name and prefix of the new base module
Feedback on individual patches is also welcome, but please keep in mind that this is very much a work in-progress
This builds on Sean's series to hide KVM internals:
https://lore.kernel.org/lkml/[email protected]
The whole thing can be found at:
https://github.com/asg-17/linux vac-rfc
The basic gist of the approach is to:
- Move system-wide virtualization resource management to a new base module to avoid collisions between different KVM modules, e.g. VPIDs and ASIDs need to be unique per VM, and callbacks from IRQ handlers need to be mediated so that things like PMIs get to the right KVM instance.
- Refactor KVM to make all upgradable assets visible only to KVM, i.e. make KVM a black box, so that the layout/size of things like "struct kvm_vcpu" isn't exposed to the kernel at-large.
- Fold kvm_intel.ko and kvm_amd.ko into kvm.ko to avoid complications having to generate unique symbols for every symbol exported by kvm.ko.
- Add a Kconfig string to allow defining a device and module postfix at build time, e.g. to create kvmX.ko and /dev/kvmX.
The proposed name of the new base module is vac.ko, a.k.a. Virtualization Acceleration Code (Unupgradable Units Module). Childish humor aside, "vac" is a unique name in the kernel and hopefully in x86 and hardware terminology, is a unique name in the kernel and hopefully in x86 and hardware terminology, e.g. git grep vac_ yields no hits in the kernel. It also has the same number of characters as "kvm", e.g. the namespace can be modified without needing whitespace adjustment if we want to go that route.
Requirements / Goals / Notes:
- Fully opt-in and backwards compatible (except for the disappearance of kvm_{amd,intel}.ko).
- User space ultimately controls and is responsible for deployment, usage, lifecycles, etc. Standard module refcounting applies, but ensuruing that a VM is created with the "right" KVM module is a user space problem.
- No user space *VMM* changes are required, e.g. /dev/kvm can be presented to a VMM by symlinking /dev/kvmX.
- Mutually exclusive with subsytems that have a hard dependency on KVM, i.e. KVMGT.
- x86 only (for the foreseeable future).
Anish Ghulati (13):
KVM: x86: Move common module params from SVM/VMX to x86
KVM: x86: Fold x86 vendor modules into the main KVM modules
KVM: x86: Remove unused exports
KVM: x86: Create stubs for a new VAC module
KVM: x86: Refactor hardware enable/disable operations into a new file
KVM: x86: Move user return msr operations out of KVM
KVM: SVM: Move shared SVM data structures into VAC
KVM: VMX: Move shared VMX data structures into VAC
KVM: VMX: Move VMX enable and disable into VAC
KVM: SVM: Move SVM enable and disable into VAC
KVM: x86: Move VMX and SVM support checks into VAC
KVM: x86: VAC: Move all hardware enable/disable code into VAC
KVM: VAC: Bring up VAC as a new module
Venkatesh Srinivas (1):
KVM: x86: Move shared KVM state into VAC
arch/x86/include/asm/kvm-x86-ops.h | 3 +- arch/x86/include/asm/kvm_host.h | 12 +- arch/x86/kernel/nmi.c | 2 +- arch/x86/kvm/Kconfig | 29 +- arch/x86/kvm/Makefile | 31 ++- arch/x86/kvm/cpuid.c | 8 +- arch/x86/kvm/hyperv.c | 2 - arch/x86/kvm/irq.c | 3 - arch/x86/kvm/irq_comm.c | 2 - arch/x86/kvm/kvm_onhyperv.c | 3 - arch/x86/kvm/lapic.c | 15 - arch/x86/kvm/mmu/mmu.c | 12 - arch/x86/kvm/mmu/spte.c | 4 - arch/x86/kvm/mtrr.c | 1 - arch/x86/kvm/pmu.c | 2 - arch/x86/kvm/svm/nested.c | 4 +- arch/x86/kvm/svm/sev.c | 2 +- arch/x86/kvm/svm/svm.c | 224 ++------------- arch/x86/kvm/svm/svm.h | 21 +- arch/x86/kvm/svm/svm_data.h | 23 ++ arch/x86/kvm/svm/svm_ops.h | 1 + arch/x86/kvm/svm/vac.c | 172 ++++++++++++ arch/x86/kvm/svm/vac.h | 20 ++ arch/x86/kvm/vac.c | 214 +++++++++++++++ arch/x86/kvm/vac.h | 69 +++++ arch/x86/kvm/vmx/nested.c | 6 +- arch/x86/kvm/vmx/vac.c | 287 +++++++++++++++++++ arch/x86/kvm/vmx/vac.h | 20 ++ arch/x86/kvm/vmx/vmx.c | 332 +++------------------- arch/x86/kvm/vmx/vmx.h | 2 - arch/x86/kvm/vmx/vmx_ops.h | 1 + arch/x86/kvm/x86.c | 423 ++--------------------------- arch/x86/kvm/x86.h | 15 +- include/linux/kvm_host.h | 2 + virt/kvm/Makefile.kvm | 14 +- virt/kvm/kvm_main.c | 210 +------------- virt/kvm/vac.c | 192 +++++++++++++ virt/kvm/vac.h | 40 +++ 38 files changed, 1212 insertions(+), 1211 deletions(-) create mode 100644 arch/x86/kvm/svm/svm_data.h create mode 100644 arch/x86/kvm/svm/vac.c create mode 100644 arch/x86/kvm/svm/vac.h create mode 100644 arch/x86/kvm/vac.c create mode 100644 arch/x86/kvm/vac.h create mode 100644 arch/x86/kvm/vmx/vac.c create mode 100644 arch/x86/kvm/vmx/vac.h create mode 100644 virt/kvm/vac.c create mode 100644 virt/kvm/vac.h
base-commit: 0b78fc46e5450f08ef92431e569c797a63f31517
Signature · 1 line
2.42.0.869.gea05f2083d-goog
RFC PATCH 1/14 KVM: x86: Move common module params from SVM/VMX to x86
Move nested and enable_vnmi from SVM and VMX into x86.
--- arch/x86/kvm/svm/nested.c | 4 ++-- arch/x86/kvm/svm/svm.c | 17 +++++------------ arch/x86/kvm/svm/svm.h | 3 +-- arch/x86/kvm/vmx/vmx.c | 11 ----------- arch/x86/kvm/x86.c | 11 +++++++++++ arch/x86/kvm/x86.h | 4 ++++ 6 files changed, 23 insertions(+), 27 deletions(-)
arch/x86/kvm/svm/nested.c +2 -2
@@ -666,7 +666,7 @@ static void nested_vmcb02_prepare_control(struct vcpu_svm *svm,else int_ctl_vmcb01_bits |= (V_GIF_MASK |V_GIF_ENABLE_MASK ); -if (vnmi) { +if (enable_vnmi) {if (vmcb01->control.int_ctl &V_NMI_PENDING_MASK ) { svm->vcpu.arch.nmi_pending++;kvm_make_request (KVM_REQ_EVENT , &svm->vcpu);
@@ -1083,7 +1083,7 @@ int nested_svm_vmexit(struct vcpu_svm *svm)svm_update_lbrv (vcpu); } -if (vnmi) { +if (enable_vnmi) {if (vmcb02->control.int_ctl &V_NMI_BLOCKING_MASK ) vmcb01->control.int_ctl |=V_NMI_BLOCKING_MASK ;else
arch/x86/kvm/svm/svm.c +5 -12
@@ -197,10 +197,6 @@ module_param(pause_filter_count_max, ushort, 0444);bool npt_enabled = true;module_param_named (npt, npt_enabled, bool,0444 ); -/* allow nested virtualization in KVM/SVM */ -static int nested = true; -module_param (nested, int,S_IRUGO ); -/* enable/disable Next RIP Save */ int nrips = true;module_param (nrips, int,0444 );
@@ -234,9 +230,6 @@ module_param(dump_invalid_vmcb, bool, 0644);bool intercept_smi = true;module_param (intercept_smi, bool,0444 ); -bool vnmi = true; -module_param (vnmi, bool,0444 ); -static bool svm_gp_erratum_intercept = true;static u8 rsm_ins_bytes[] ="\x0f\xaa" ;
@@ -1357,7 +1350,7 @@ static void init_vmcb(struct kvm_vcpu *vcpu)if (kvm_vcpu_apicv_active (vcpu))avic_init_vmcb (svm, vmcb); -if (vnmi) +if (enable_vnmi) svm->vmcb->control.int_ctl |=V_NMI_ENABLE_MASK ;if (vgif) {
@@ -5089,7 +5082,7 @@ static __init void svm_set_cpu_caps(void)if (vgif)kvm_cpu_cap_set (X86_FEATURE_VGIF ); -if (vnmi) +if (enable_vnmi)kvm_cpu_cap_set (X86_FEATURE_VNMI );/* Nested VM can receive #VMEXIT instead of triggering #GP */
@@ -5253,11 +5246,11 @@ static __init int svm_hardware_setup(void)pr_info ("Virtual GIF supported\n" ); } - vnmi = vgif && vnmi &&boot_cpu_has (X86_FEATURE_VNMI ); -if (vnmi) + enable_vnmi = vgif && enable_vnmi &&boot_cpu_has (X86_FEATURE_VNMI ); +if (enable_vnmi)pr_info ("Virtual NMI enabled\n" ); -if (!vnmi) { +if (!enable_vnmi) { svm_x86_ops.is_vnmi_pending =NULL ; svm_x86_ops.set_vnmi_pending =NULL ; }
arch/x86/kvm/svm/svm.h +1 -2
@@ -38,7 +38,6 @@ extern int nrips;extern int vgif;extern bool intercept_smi;extern bool x2avic_enabled; -extern bool vnmi;/* * Clean bits in VMCB.
@@ -510,7 +509,7 @@ static inline bool is_x2apic_msrpm_offset(u32 offset)static inline struct vmcb *get_vnmi_vmcb_l1 (struct vcpu_svm *svm) { -if (!vnmi) +if (!enable_vnmi)return NULL ;if (is_guest_mode (&svm->vcpu))
arch/x86/kvm/vmx/vmx.c +0 -11
@@ -80,9 +80,6 @@ MODULE_DEVICE_TABLE(x86cpu, vmx_cpu_id);bool __read_mostly enable_vpid =1 ;module_param_named (vpid, enable_vpid, bool,0444 ); -static bool __read_mostly enable_vnmi =1 ; -module_param_named (vnmi, enable_vnmi, bool,S_IRUGO ); -bool __read_mostly flexpriority_enabled =1 ;module_param_named (flexpriority, flexpriority_enabled, bool,S_IRUGO );
@@ -107,14 +104,6 @@ module_param(enable_apicv, bool, S_IRUGO);bool __read_mostly enable_ipiv = true;module_param (enable_ipiv, bool,0444 ); -/* -* If nested=1, nested virtualization is supported, i.e., guests may use -* VMX and be a hypervisor for its own guests. If nested=0, guests may not -* use VMX instructions. -*/ -static bool __read_mostly nested =1 ; -module_param (nested, bool,S_IRUGO ); -bool __read_mostly enable_pml =1 ;module_param_named (pml, enable_pml, bool,S_IRUGO );
arch/x86/kvm/x86.c +11 -0
@@ -176,6 +176,17 @@ bool __read_mostly enable_vmware_backdoor = false;module_param (enable_vmware_backdoor, bool,S_IRUGO );EXPORT_SYMBOL_GPL (enable_vmware_backdoor); +/* +* If nested=1, nested virtualization is supported +*/ +bool __read_mostly nested =1 ; +module_param (nested, bool,S_IRUGO ); +EXPORT_SYMBOL_GPL (nested); + +bool __read_mostly enable_vnmi =1 ; +module_param (enable_vnmi, bool,S_IRUGO ); +EXPORT_SYMBOL_GPL (enable_vnmi); +/* * Flags to manipulate forced emulation behavior (any non-zero value will * enable forced emulation).
arch/x86/kvm/x86.h +4 -0
@@ -367,6 +367,10 @@ extern unsigned int min_timer_period_us;extern bool enable_vmware_backdoor; +extern bool nested; + +extern bool enable_vnmi; +extern int pi_inject_timer;extern bool report_ignored_msrs;
Signature · 1 line
2.42.0.869.gea05f2083d-goog
RFC PATCH 2/14 KVM: x86: Fold x86 vendor modules into the main KVM modules
In reply to Anish GhulatiCollapse x86 vendor modules, i.e. kvm_intel and kvm_amd into kvm.ko.
Add a new vendor_exit function to kvm_x86_ops so that KVM knows which exit function to call when exiting. Since the vendor modules no longer exist the vendor_exit function call does not have to go through a static call.
Expose vendor init/exit/supported functions so that they can be called from vendor neutral KVM locations.
--- arch/x86/include/asm/kvm-x86-ops.h | 1 + arch/x86/include/asm/kvm_host.h | 2 + arch/x86/kernel/nmi.c | 2 +- arch/x86/kvm/Kconfig | 12 ++---- arch/x86/kvm/Makefile | 10 ++--- arch/x86/kvm/svm/svm.c | 38 +++++++---------- arch/x86/kvm/vmx/vmx.c | 66 +++++++++++++----------------- arch/x86/kvm/x86.c | 18 +++++--- arch/x86/kvm/x86.h | 15 +++++++ 9 files changed, 82 insertions(+), 82 deletions(-)
arch/x86/include/asm/kvm-x86-ops.h +1 -0
@@ -14,6 +14,7 @@ BUILD_BUG_ON(1)* to make a definition optional, but in this case the default will * be __static_call_return0. */ +KVM_X86_OP(vendor_exit) KVM_X86_OP(check_processor_compatibility) KVM_X86_OP(hardware_enable) KVM_X86_OP(hardware_disable)
arch/x86/include/asm/kvm_host.h +2 -0
@@ -1546,6 +1546,8 @@ static inline u16 kvm_lapic_irq_dest_mode(bool dest_mode_logical)struct kvm_x86_ops {const char *name; +void (*vendor_exit)(void ); +int (*check_processor_compatibility)(void );int (*hardware_enable)(void );
arch/x86/kernel/nmi.c +1 -1
@@ -565,7 +565,7 @@ DEFINE_IDTENTRY_RAW(exc_nmi_kvm_vmx) {exc_nmi (regs); } -#if IS_MODULE (CONFIG_KVM_INTEL ) +#if IS_MODULE (CONFIG_KVM ) &&IS_ENABLED (CONFIG_KVM_INTEL )EXPORT_SYMBOL_GPL (asm_exc_nmi_kvm_vmx);#endif #endif
arch/x86/kvm/Kconfig +3 -9
@@ -75,15 +75,12 @@ config KVM_WERROR If in doubt, say "N". config KVM_INTEL - tristate "KVM for Intel (and compatible) processors support" + bool "KVM for Intel (and compatible) processors support" depends on KVM && IA32_FEAT_CTL help Provides support for KVM on processors equipped with Intel's VT extensions, a.k.a. Virtual Machine Extensions (VMX). - To compile this as a module, choose M here: the module - will be called kvm-intel. - config X86_SGX_KVM bool "Software Guard eXtensions (SGX) Virtualization" depends on X86_SGX && KVM_INTEL
@@ -97,20 +94,17 @@ config X86_SGX_KVM If unsure, say N. config KVM_AMD - tristate "KVM for AMD processors support" + bool "KVM for AMD processors support" depends on KVM && (CPU_SUP_AMD || CPU_SUP_HYGON) help Provides support for KVM on AMD processors equipped with the AMD-V (SVM) extensions. - To compile this as a module, choose M here: the module - will be called kvm-amd. - config KVM_AMD_SEV def_bool y bool "AMD Secure Encrypted Virtualization (SEV) support" depends on KVM_AMD && X86_64 - depends on CRYPTO_DEV_SP_PSP && !(KVM_AMD=y && CRYPTO_DEV_CCP_DD=m) + depends on CRYPTO_DEV_SP_PSP && !(KVM=y && CRYPTO_DEV_CCP_DD=m) help Provides support for launching Encrypted VMs (SEV) and Encrypted VMs with Encrypted State (SEV-ES) on AMD processors.
arch/x86/kvm/Makefile +4 -6
@@ -21,20 +21,18 @@ kvm-$(CONFIG_X86_64) += mmu/tdp_iter.o mmu/tdp_mmu.o kvm-$(CONFIG_KVM_XEN) += xen.o kvm-$(CONFIG_KVM_SMM) += smm.o -kvm-intel-y += vmx/vmx.o vmx/vmenter.o vmx/pmu_intel.o vmx/vmcs12.o \ +kvm-$(CONFIG_KVM_INTEL) += vmx/vmx.o vmx/vmenter.o vmx/pmu_intel.o vmx/vmcs12.o \ vmx/hyperv.o vmx/nested.o vmx/posted_intr.o -kvm-intel-$(CONFIG_X86_SGX_KVM) += vmx/sgx.o +kvm-$(CONFIG_X86_SGX_KVM) += vmx/sgx.o -kvm-amd-y += svm/svm.o svm/vmenter.o svm/pmu.o svm/nested.o svm/avic.o \ +kvm-$(CONFIG_KVM_AMD) += svm/svm.o svm/vmenter.o svm/pmu.o svm/nested.o svm/avic.o \ svm/sev.o svm/hyperv.o ifdef CONFIG_HYPERV -kvm-amd-y += svm/svm_onhyperv.o +kvm-$(CONFIG_KVM_AMD) += svm/svm_onhyperv.o endif obj-$(CONFIG_KVM) += kvm.o -obj-$(CONFIG_KVM_INTEL) += kvm-intel.o -obj-$(CONFIG_KVM_AMD) += kvm-amd.o AFLAGS_svm/vmenter.o := -iquote $(obj) $(obj)/svm/vmenter.o: $(obj)/kvm-asm-offsets.h
arch/x86/kvm/svm/svm.c +14 -24
@@ -52,9 +52,6 @@#include "kvm_onhyperv.h" #include "svm_onhyperv.h" -MODULE_AUTHOR ("Qumranet" ); -MODULE_LICENSE ("GPL" ); -#ifdef MODULE static const struct x86_cpu_id svm_cpu_id[] = { X86_MATCH_FEATURE(X86_FEATURE_SVM, NULL),
@@ -551,7 +548,7 @@ static bool __kvm_is_svm_supported(void)return true; } -static bool kvm_is_svm_supported (void ) +bool kvm_is_svm_supported (void ) {bool supported;
@@ -4873,9 +4870,21 @@ static int svm_vm_init(struct kvm *kvm)return 0 ; } +static void __svm_exit (void ) +{ +cpu_emergency_unregister_virt_callback (svm_emergency_disable); +} + +void svm_module_exit (void ) +{ +__svm_exit (); +} +static struct kvm_x86_ops svm_x86_ops__initdata = { .name =KBUILD_MODNAME , + .vendor_exit = svm_module_exit, + .check_processor_compatibility = svm_check_processor_compat, .hardware_unsetup = svm_hardware_unsetup,
@@ -5298,22 +5307,12 @@ static struct kvm_x86_init_ops svm_init_ops __initdata = { .pmu_ops = &amd_pmu_ops, }; -static void __svm_exit (void ) -{ -kvm_x86_vendor_exit (); - -cpu_emergency_unregister_virt_callback (svm_emergency_disable); -} - -static int __init svm_init (void ) +int __init svm_init (void ) {int r;__unused_size_checks (); -if (!kvm_is_svm_supported ()) -return -EOPNOTSUPP ; - r =kvm_x86_vendor_init (&svm_init_ops);if (r)return r;
@@ -5335,12 +5334,3 @@ static int __init svm_init(void)__svm_exit ();return r; } - -static void __exit svm_exit(void) -{ -kvm_exit (); -__svm_exit (); -} - -module_init (svm_init) -module_exit (svm_exit)
arch/x86/kvm/vmx/vmx.c +29 -37
105 lines not on this page · raw message
arch/x86/kvm/x86.c +13 -5
@@ -15,6 +15,7 @@* Amit Shah <[email protected]> * Ben-Ami Yassour <[email protected]> */ +#include <asm-generic/errno.h> #define pr_fmt (fmt) KBUILD_MODNAME ": " fmt#include <linux/kvm_host.h>
@@ -13678,15 +13679,22 @@ static int __init kvm_x86_init(void) {kvm_mmu_x86_module_init (); mitigate_smt_rsb &=boot_cpu_has_bug (X86_BUG_SMT_RSB ) &&cpu_smt_possible (); -return 0 ; + +if (kvm_is_svm_supported ()) +return svm_init (); +else if (kvm_is_vmx_supported ()) +return vmx_init (); + +pr_err_ratelimited ("kvm: no hardware support for SVM or VMX\n" ); +return -EOPNOTSUPP ; }module_init (kvm_x86_init); static void __exit kvm_x86_exit(void) { -/* -* If module_init() is implemented, module_exit() must also be -* implemented to allow module unload. -*/ +kvm_exit (); +kvm_x86_vendor_exit (); + kvm_x86_ops.vendor_exit (); + }module_exit (kvm_x86_exit);
arch/x86/kvm/x86.h +15 -0
@@ -9,6 +9,21 @@#include "kvm_cache_regs.h" #include "kvm_emulate.h" +#ifdef CONFIG_KVM_AMD +bool kvm_is_svm_supported (void ); +int __init svm_init (void ); +void svm_module_exit (void ); +#else +bool kvm_is_svm_supported (void ) {return false; } +#endif +#ifdef CONFIG_KVM_INTEL +bool kvm_is_vmx_supported (void ); +int __init vmx_init (void ); +void vmx_module_exit (void ); +#else +bool kvm_is_vmx_supported (void ) {return false; } +#endif +struct kvm_caps {/* control of guest tsc rate supported? */ bool has_tsc_control;
Signature · 1 line
2.42.0.869.gea05f2083d-goog
RFC PATCH 3/14 KVM: x86: Remove unused exports
In reply to Anish GhulatiRemove all the unused exports from KVM now that vendor modules no longer exist.
--- arch/x86/kvm/cpuid.c | 7 -- arch/x86/kvm/hyperv.c | 2 - arch/x86/kvm/irq.c | 3 - arch/x86/kvm/irq_comm.c | 2 - arch/x86/kvm/kvm_onhyperv.c | 3 - arch/x86/kvm/lapic.c | 15 ---- arch/x86/kvm/mmu/mmu.c | 12 ---- arch/x86/kvm/mmu/spte.c | 4 -- arch/x86/kvm/mtrr.c | 1 - arch/x86/kvm/pmu.c | 2 - arch/x86/kvm/x86.c | 140 ------------------------------------ 11 files changed, 191 deletions(-)
arch/x86/kvm/cpuid.c +0 -7
@@ -34,7 +34,6 @@* aligned to sizeof(unsigned long) because it's not accessed via bitops. */ u32 kvm_cpu_caps[NR_KVM_CPU_CAPS ]__read_mostly ; -EXPORT_SYMBOL_GPL (kvm_cpu_caps);u32 xstate_required_size (u64 xstate_bv,bool compacted) {
@@ -310,7 +309,6 @@ void kvm_update_cpuid_runtime(struct kvm_vcpu *vcpu) {__kvm_update_cpuid_runtime (vcpu, vcpu->arch.cpuid_entries, vcpu->arch.cpuid_nent); } -EXPORT_SYMBOL_GPL (kvm_update_cpuid_runtime);static bool kvm_cpuid_has_hyperv (struct kvm_cpuid_entry2 *entries,int nent) {
@@ -808,7 +806,6 @@ void kvm_set_cpu_caps(void)kvm_cpu_cap_clear (X86_FEATURE_RDPID ); } } -EXPORT_SYMBOL_GPL (kvm_set_cpu_caps);struct kvm_cpuid_array {struct kvm_cpuid_entry2 *entries;
@@ -1432,7 +1429,6 @@ struct kvm_cpuid_entry2 *kvm_find_cpuid_entry_index(struct kvm_vcpu *vcpu,return cpuid_entry2_find (vcpu->arch.cpuid_entries, vcpu->arch.cpuid_nent, function, index); } -EXPORT_SYMBOL_GPL (kvm_find_cpuid_entry_index);struct kvm_cpuid_entry2 *kvm_find_cpuid_entry (struct kvm_vcpu *vcpu,u32 function)
@@ -1440,7 +1436,6 @@ struct kvm_cpuid_entry2 *kvm_find_cpuid_entry(struct kvm_vcpu *vcpu,return cpuid_entry2_find (vcpu->arch.cpuid_entries, vcpu->arch.cpuid_nent, function,KVM_CPUID_INDEX_NOT_SIGNIFICANT ); } -EXPORT_SYMBOL_GPL (kvm_find_cpuid_entry);/* * Intel CPUID semantics treats any query for an out-of-range leaf as if the
@@ -1560,7 +1555,6 @@ bool kvm_cpuid(struct kvm_vcpu *vcpu, u32 *eax, u32 *ebx, used_max_basic);return exact; } -EXPORT_SYMBOL_GPL (kvm_cpuid);int kvm_emulate_cpuid (struct kvm_vcpu *vcpu) {
@@ -1578,4 +1572,3 @@ int kvm_emulate_cpuid(struct kvm_vcpu *vcpu)kvm_rdx_write (vcpu, edx);return kvm_skip_emulated_instruction (vcpu); } -EXPORT_SYMBOL_GPL (kvm_emulate_cpuid);
arch/x86/kvm/hyperv.c +0 -2
@@ -917,7 +917,6 @@ bool kvm_hv_assist_page_enabled(struct kvm_vcpu *vcpu)return false;return vcpu->arch.pv_eoi.msr_val &KVM_MSR_ENABLED ; } -EXPORT_SYMBOL_GPL (kvm_hv_assist_page_enabled);int kvm_hv_get_assist_page (struct kvm_vcpu *vcpu) {
@@ -929,7 +928,6 @@ int kvm_hv_get_assist_page(struct kvm_vcpu *vcpu)return kvm_read_guest_cached (vcpu->kvm, &vcpu->arch.pv_eoi.data, &hv_vcpu->vp_assist_page,sizeof (struct hv_vp_assist_page )); } -EXPORT_SYMBOL_GPL (kvm_hv_get_assist_page);static void stimer_prepare_msg (struct kvm_vcpu_hv_stimer *stimer) {
arch/x86/kvm/irq.c +0 -3
@@ -89,7 +89,6 @@ int kvm_cpu_has_injectable_intr(struct kvm_vcpu *v)return kvm_apic_has_interrupt (v) !=-1 ;/* LAPIC */ } -EXPORT_SYMBOL_GPL (kvm_cpu_has_injectable_intr);/* * check if there is pending interrupt without
@@ -102,7 +101,6 @@ int kvm_cpu_has_interrupt(struct kvm_vcpu *v)return kvm_apic_has_interrupt (v) !=-1 ;/* LAPIC */ } -EXPORT_SYMBOL_GPL (kvm_cpu_has_interrupt);/* * Read pending interrupt(from non-APIC source)
@@ -141,7 +139,6 @@ int kvm_cpu_get_interrupt(struct kvm_vcpu *v)return kvm_get_apic_interrupt (v);/* APIC */ } -EXPORT_SYMBOL_GPL (kvm_cpu_get_interrupt);void kvm_inject_pending_timer_irqs (struct kvm_vcpu *vcpu) {
arch/x86/kvm/irq_comm.c +0 -2
@@ -120,7 +120,6 @@ void kvm_set_msi_irq(struct kvm *kvm, struct kvm_kernel_irq_routing_entry *e, irq->level =1 ; irq->shorthand =APIC_DEST_NOSHORT ; } -EXPORT_SYMBOL_GPL (kvm_set_msi_irq);static inline bool kvm_msi_route_invalid (struct kvm *kvm,struct kvm_kernel_irq_routing_entry *e)
@@ -356,7 +355,6 @@ bool kvm_intr_is_single_vcpu(struct kvm *kvm, struct kvm_lapic_irq *irq,return r ==1 ; } -EXPORT_SYMBOL_GPL (kvm_intr_is_single_vcpu);#define IOAPIC_ROUTING_ENTRY (irq) \ { .gsi = irq, .type = KVM_IRQ_ROUTING_IRQCHIP, \
arch/x86/kvm/kvm_onhyperv.c +0 -3
@@ -101,13 +101,11 @@ int hv_flush_remote_tlbs_range(struct kvm *kvm, gfn_t start_gfn, gfn_t nr_pages)return __hv_flush_remote_tlbs_range (kvm, &range); } -EXPORT_SYMBOL_GPL (hv_flush_remote_tlbs_range);int hv_flush_remote_tlbs (struct kvm *kvm) {return __hv_flush_remote_tlbs_range (kvm,NULL ); } -EXPORT_SYMBOL_GPL (hv_flush_remote_tlbs);void hv_track_root_tdp (struct kvm_vcpu *vcpu,hpa_t root_tdp) {
@@ -121,4 +119,3 @@ void hv_track_root_tdp(struct kvm_vcpu *vcpu, hpa_t root_tdp)spin_unlock (&kvm_arch->hv_root_tdp_lock); } } -EXPORT_SYMBOL_GPL (hv_track_root_tdp);
arch/x86/kvm/lapic.c +0 -15
@@ -682,7 +682,6 @@ bool __kvm_apic_update_irr(u32 *pir, void *regs, int *max_irr)return ((max_updated_irr !=-1 ) && (max_updated_irr == *max_irr)); } -EXPORT_SYMBOL_GPL (__kvm_apic_update_irr);bool kvm_apic_update_irr (struct kvm_vcpu *vcpu,u32 *pir,int *max_irr) {
@@ -693,7 +692,6 @@ bool kvm_apic_update_irr(struct kvm_vcpu *vcpu, u32 *pir, int *max_irr) apic->irr_pending = true;return irr_updated; } -EXPORT_SYMBOL_GPL (kvm_apic_update_irr);static inline int apic_search_irr (struct kvm_lapic *apic) {
@@ -736,7 +734,6 @@ void kvm_apic_clear_irr(struct kvm_vcpu *vcpu, int vec) {apic_clear_irr (vec, vcpu->arch.apic); } -EXPORT_SYMBOL_GPL (kvm_apic_clear_irr);static inline void apic_set_isr (int vec,struct kvm_lapic *apic) {
@@ -811,7 +808,6 @@ int kvm_lapic_find_highest_irr(struct kvm_vcpu *vcpu)*/ return apic_find_highest_irr (vcpu->arch.apic); } -EXPORT_SYMBOL_GPL (kvm_lapic_find_highest_irr); static int __apic_accept_irq(struct kvm_lapic *apic, int delivery_mode, int vector, int level, int trig_mode,
@@ -973,7 +969,6 @@ void kvm_apic_update_ppr(struct kvm_vcpu *vcpu) {apic_update_ppr (vcpu->arch.apic); } -EXPORT_SYMBOL_GPL (kvm_apic_update_ppr);static void apic_set_tpr (struct kvm_lapic *apic,u32 tpr) {
@@ -1084,7 +1079,6 @@ bool kvm_apic_match_dest(struct kvm_vcpu *vcpu, struct kvm_lapic *source,return false; } } -EXPORT_SYMBOL_GPL (kvm_apic_match_dest);int kvm_vector_to_index (u32 vector,u32 dest_vcpus,const unsigned long *bitmap,u32 bitmap_size)
@@ -1497,7 +1491,6 @@ void kvm_apic_set_eoi_accelerated(struct kvm_vcpu *vcpu, int vector)kvm_ioapic_send_eoi (apic, vector);kvm_make_request (KVM_REQ_EVENT , apic->vcpu); } -EXPORT_SYMBOL_GPL (kvm_apic_set_eoi_accelerated);void kvm_apic_send_ipi (struct kvm_lapic *apic,u32 icr_low,u32 icr_high) {
@@ -1522,7 +1515,6 @@ void kvm_apic_send_ipi(struct kvm_lapic *apic, u32 icr_low, u32 icr_high)kvm_irq_delivery_to_apic (apic->vcpu->kvm, apic, &irq,NULL ); } -EXPORT_SYMBOL_GPL (kvm_apic_send_ipi);static u32 apic_get_tmcct (struct kvm_lapic *apic) {
@@ -1638,7 +1630,6 @@ u64 kvm_lapic_readable_reg_mask(struct kvm_lapic *apic)return valid_reg_mask; } -EXPORT_SYMBOL_GPL (kvm_lapic_readable_reg_mask);static int kvm_lapic_reg_read (struct kvm_lapic *apic,u32 offset,int len,void *data)
@@ -1872,7 +1863,6 @@ void kvm_wait_lapic_expire(struct kvm_vcpu *vcpu) lapic_timer_int_injected(vcpu))__kvm_wait_lapic_expire (vcpu); } -EXPORT_SYMBOL_GPL (kvm_wait_lapic_expire);static void kvm_apic_inject_pending_timer_irqs (struct kvm_lapic *apic) {
@@ -2185,7 +2175,6 @@ void kvm_lapic_expired_hv_timer(struct kvm_vcpu *vcpu) out:preempt_enable (); } -EXPORT_SYMBOL_GPL (kvm_lapic_expired_hv_timer);void kvm_lapic_switch_to_hv_timer (struct kvm_vcpu *vcpu) {
@@ -2438,7 +2427,6 @@ void kvm_lapic_set_eoi(struct kvm_vcpu *vcpu) {kvm_lapic_reg_write (vcpu->arch.apic,APIC_EOI ,0 ); } -EXPORT_SYMBOL_GPL (kvm_lapic_set_eoi);/* emulate APIC access in a trap manner */ void kvm_apic_write_nodecode (struct kvm_vcpu *vcpu,u32 offset)
@@ -2461,7 +2449,6 @@ void kvm_apic_write_nodecode(struct kvm_vcpu *vcpu, u32 offset)kvm_lapic_reg_write (apic, offset, (u32 )val); } } -EXPORT_SYMBOL_GPL (kvm_apic_write_nodecode);void kvm_free_lapic (struct kvm_vcpu *vcpu) {
@@ -2627,7 +2614,6 @@ int kvm_alloc_apic_access_page(struct kvm *kvm)mutex_unlock (&kvm->slots_lock);return ret; } -EXPORT_SYMBOL_GPL (kvm_alloc_apic_access_page);void kvm_inhibit_apic_access_page (struct kvm_vcpu *vcpu) {
@@ -2858,7 +2844,6 @@ int kvm_apic_has_interrupt(struct kvm_vcpu *vcpu)__apic_update_ppr (apic, &ppr);return apic_has_interrupt_for_ppr (apic, ppr); } -EXPORT_SYMBOL_GPL (kvm_apic_has_interrupt);int kvm_apic_accept_pic_intr (struct kvm_vcpu *vcpu) {
arch/x86/kvm/mmu/mmu.c +0 -12
@@ -3610,7 +3610,6 @@ void kvm_mmu_free_roots(struct kvm *kvm, struct kvm_mmu *mmu,kvm_mmu_commit_zap_page (kvm, &invalid_list);write_unlock (&kvm->mmu_lock); } -EXPORT_SYMBOL_GPL (kvm_mmu_free_roots);void kvm_mmu_free_guest_mode_roots (struct kvm *kvm,struct kvm_mmu *mmu) {
@@ -3637,7 +3636,6 @@ void kvm_mmu_free_guest_mode_roots(struct kvm *kvm, struct kvm_mmu *mmu)kvm_mmu_free_roots (kvm, mmu, roots_to_free); } -EXPORT_SYMBOL_GPL (kvm_mmu_free_guest_mode_roots);static hpa_t mmu_alloc_root (struct kvm_vcpu *vcpu,gfn_t gfn,int quadrant,u8 level)
@@ -4441,7 +4439,6 @@ int kvm_handle_page_fault(struct kvm_vcpu *vcpu, u64 error_code,return r; } -EXPORT_SYMBOL_GPL (kvm_handle_page_fault);#ifdef CONFIG_X86_64 static int kvm_tdp_mmu_page_fault(struct kvm_vcpu *vcpu,
@@ -4660,7 +4657,6 @@ void kvm_mmu_new_pgd(struct kvm_vcpu *vcpu, gpa_t new_pgd)__clear_sp_write_flooding_count (sp); } } -EXPORT_SYMBOL_GPL (kvm_mmu_new_pgd);static bool sync_mmio_spte (struct kvm_vcpu *vcpu,u64 *sptep,gfn_t gfn,unsigned int access)
@@ -5294,7 +5290,6 @@ void kvm_init_shadow_npt_mmu(struct kvm_vcpu *vcpu, unsigned long cr0,shadow_mmu_init_context (vcpu, context, cpu_role, root_role);kvm_mmu_new_pgd (vcpu, nested_cr3); } -EXPORT_SYMBOL_GPL (kvm_init_shadow_npt_mmu); static union kvm_cpu_role kvm_calc_shadow_ept_root_page_role(struct kvm_vcpu *vcpu, bool accessed_dirty,
@@ -5348,7 +5343,6 @@ void kvm_init_shadow_ept_mmu(struct kvm_vcpu *vcpu, bool execonly,kvm_mmu_new_pgd (vcpu, new_eptp); } -EXPORT_SYMBOL_GPL (kvm_init_shadow_ept_mmu);static void init_kvm_softmmu (struct kvm_vcpu *vcpu,union kvm_cpu_role cpu_role)
@@ -5413,7 +5407,6 @@ void kvm_init_mmu(struct kvm_vcpu *vcpu)else init_kvm_softmmu (vcpu, cpu_role); } -EXPORT_SYMBOL_GPL (kvm_init_mmu);void kvm_mmu_after_set_cpuid (struct kvm_vcpu *vcpu) {
@@ -5449,7 +5442,6 @@ void kvm_mmu_reset_context(struct kvm_vcpu *vcpu)kvm_mmu_unload (vcpu);kvm_init_mmu (vcpu); } -EXPORT_SYMBOL_GPL (kvm_mmu_reset_context);int kvm_mmu_load (struct kvm_vcpu *vcpu) {
@@ -5763,7 +5755,6 @@ int noinline kvm_mmu_page_fault(struct kvm_vcpu *vcpu, gpa_t cr2_or_gpa, u64 errreturn x86_emulate_instruction (vcpu, cr2_or_gpa, emulation_type, insn, insn_len); } -EXPORT_SYMBOL_GPL (kvm_mmu_page_fault);static void __kvm_mmu_invalidate_addr (struct kvm_vcpu *vcpu,struct kvm_mmu *mmu,u64 addr,hpa_t root_hpa)
@@ -5829,7 +5820,6 @@ void kvm_mmu_invalidate_addr(struct kvm_vcpu *vcpu, struct kvm_mmu *mmu,__kvm_mmu_invalidate_addr (vcpu, mmu, addr, mmu->prev_roots[i].hpa); } } -EXPORT_SYMBOL_GPL (kvm_mmu_invalidate_addr);void kvm_mmu_invlpg (struct kvm_vcpu *vcpu,gva_t gva) {
@@ -5846,7 +5836,6 @@ void kvm_mmu_invlpg(struct kvm_vcpu *vcpu, gva_t gva)kvm_mmu_invalidate_addr (vcpu, vcpu->arch.walk_mmu, gva,KVM_MMU_ROOTS_ALL ); ++vcpu->stat.invlpg; } -EXPORT_SYMBOL_GPL (kvm_mmu_invlpg);void kvm_mmu_invpcid_gva (struct kvm_vcpu *vcpu,gva_t gva,unsigned long pcid)
@@ -5899,7 +5888,6 @@ void kvm_configure_mmu(bool enable_tdp, int tdp_forced_root_level,else max_huge_page_level =PG_LEVEL_2M ; } -EXPORT_SYMBOL_GPL (kvm_configure_mmu);/* The return value indicates if tlb flush on all vcpus is needed. */ typedef bool (*slot_rmaps_handler) (struct kvm *kvm,
arch/x86/kvm/mmu/spte.c +0 -4
@@ -22,7 +22,6 @@bool __read_mostly enable_mmio_caching = true;static bool __ro_after_init allow_mmio_caching;module_param_named (mmio_caching, enable_mmio_caching, bool,0444 ); -EXPORT_SYMBOL_GPL (enable_mmio_caching);u64 __read_mostly shadow_host_writable_mask;u64 __read_mostly shadow_mmu_writable_mask;
@@ -409,7 +408,6 @@ void kvm_mmu_set_mmio_spte_mask(u64 mmio_value, u64 mmio_mask, u64 access_mask) shadow_mmio_mask = mmio_mask; shadow_mmio_access_mask = access_mask; } -EXPORT_SYMBOL_GPL (kvm_mmu_set_mmio_spte_mask);void kvm_mmu_set_me_spte_mask (u64 me_value,u64 me_mask) {
@@ -420,7 +418,6 @@ void kvm_mmu_set_me_spte_mask(u64 me_value, u64 me_mask) shadow_me_value = me_value; shadow_me_mask = me_mask; } -EXPORT_SYMBOL_GPL (kvm_mmu_set_me_spte_mask);void kvm_mmu_set_ept_masks (bool has_ad_bits,bool has_exec_only) {
@@ -448,7 +445,6 @@ void kvm_mmu_set_ept_masks(bool has_ad_bits, bool has_exec_only)kvm_mmu_set_mmio_spte_mask (VMX_EPT_MISCONFIG_WX_VALUE ,VMX_EPT_RWX_MASK ,0 ); } -EXPORT_SYMBOL_GPL (kvm_mmu_set_ept_masks);void kvm_mmu_reset_all_pte_masks (void ) {
arch/x86/kvm/mtrr.c +0 -1
@@ -685,7 +685,6 @@ u8 kvm_mtrr_get_guest_memory_type(struct kvm_vcpu *vcpu, gfn_t gfn)return type; } -EXPORT_SYMBOL_GPL (kvm_mtrr_get_guest_memory_type);bool kvm_mtrr_check_gfn_range_consistency (struct kvm_vcpu *vcpu,gfn_t gfn,int page_num)
arch/x86/kvm/pmu.c +0 -2
@@ -27,7 +27,6 @@#define KVM_PMU_EVENT_FILTER_MAX_EVENTS 300struct x86_pmu_capability __read_mostly kvm_pmu_cap; -EXPORT_SYMBOL_GPL (kvm_pmu_cap);/* Precise Distribution of Instructions Retired (PDIR) */ static const struct x86_cpu_id vmx_pebs_pdir_cpu[] = {
@@ -773,7 +772,6 @@ void kvm_pmu_trigger_event(struct kvm_vcpu *vcpu, u64 perf_hw_id)kvm_pmu_incr_counter (pmc); } } -EXPORT_SYMBOL_GPL (kvm_pmu_trigger_event);static bool is_masked_filter_valid (const struct kvm_x86_pmu_event_filter *filter) {
arch/x86/kvm/x86.c +0 -140
763 lines not on this page · raw message
Signature · 1 line
2.42.0.869.gea05f2083d-goog
RFC PATCH 4/14 KVM: x86: Create stubs for a new VAC module
In reply to Anish GhulatiCreate emtpy stub files for what will eventually be a new module named Virtualization Acceleration Code: Unupgradable Units Module (backronym:
VACUUM, or VAC for short). VAC will function as a base module for multiple KVM modules and will contain the code needed to manage system-wide virtualization resources, like enabling/disabling virtualization hardware.
--- arch/x86/kvm/Makefile | 2 ++ arch/x86/kvm/svm/vac.c | 2 ++ arch/x86/kvm/vac.c | 3 +++ arch/x86/kvm/vac.h | 6 ++++++ arch/x86/kvm/vmx/vac.c | 2 ++ virt/kvm/Makefile.kvm | 1 + virt/kvm/vac.c | 3 +++ virt/kvm/vac.h | 6 ++++++ 8 files changed, 25 insertions(+) create mode 100644 arch/x86/kvm/svm/vac.c create mode 100644 arch/x86/kvm/vac.c create mode 100644 arch/x86/kvm/vac.h create mode 100644 arch/x86/kvm/vmx/vac.c create mode 100644 virt/kvm/vac.c create mode 100644 virt/kvm/vac.h
arch/x86/kvm/Makefile +2 -0
@@ -13,6 +13,8 @@ kvm-y += x86.o emulate.o i8259.o irq.o lapic.o \ hyperv.o debugfs.o mmu/mmu.o mmu/page_track.o \ mmu/spte.o +kvm-y += vac.o vmx/vac.o svm/vac.o + ifdef CONFIG_HYPERV kvm-y += kvm_onhyperv.o endif
arch/x86/kvm/svm/vac.c new file +2 -0
@@ -0,0 +1,2 @@ +// SPDX-License-Identifier: GPL-2.0-only +
arch/x86/kvm/vac.c new file +3 -0
@@ -0,0 +1,3 @@ +// SPDX-License-Identifier: GPL-2.0-only + +#include "vac.h"
arch/x86/kvm/vac.h new file +6 -0
@@ -0,0 +1,6 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +#ifndef ARCH_X86_KVM_VAC_H +#define ARCH_X86_KVM_VAC_H + +#endif // ARCH_X86_KVM_VAC_H
arch/x86/kvm/vmx/vac.c new file +2 -0
@@ -0,0 +1,2 @@ +// SPDX-License-Identifier: GPL-2.0-only +
virt/kvm/Makefile.kvm +1 -0
@@ -11,6 +11,7 @@ kvm-y := $(KVM)/kvm_main.o $(KVM)/eventfd.o $(KVM)/binary_stats.o ifdef CONFIG_VFIO kvm-y += $(KVM)/vfio.o endif +kvm-y += $(KVM)/vac.o kvm-$(CONFIG_KVM_MMIO) += $(KVM)/coalesced_mmio.o kvm-$(CONFIG_KVM_ASYNC_PF) += $(KVM)/async_pf.o kvm-$(CONFIG_HAVE_KVM_IRQ_ROUTING) += $(KVM)/irqchip.o
virt/kvm/vac.c new file +3 -0
@@ -0,0 +1,3 @@ +// SPDX-License-Identifier: GPL-2.0-only + +#include "vac.h"
virt/kvm/vac.h new file +6 -0
@@ -0,0 +1,6 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ + +#ifndef __KVM_VAC_H__ +#define __KVM_VAC_H__ + +#endif
Signature · 1 line
2.42.0.869.gea05f2083d-goog
RFC PATCH 5/14 KVM: x86: Refactor hardware enable/disable operations into a new file
In reply to Anish GhulatiMove KVM's hardware enabling to vac.{h,c} as a first step towards building VAC and all of the system-wide virtualization support as a separate module.
Defer moving arch code to future patches to keep the diff reasonable.
No functional change intended.
--- virt/kvm/kvm_main.c | 197 +------------------------------------------- virt/kvm/vac.c | 177 +++++++++++++++++++++++++++++++++++++++ virt/kvm/vac.h | 26 ++++++ 3 files changed, 204 insertions(+), 196 deletions(-)
virt/kvm/kvm_main.c +1 -196
@@ -59,6 +59,7 @@#include "coalesced_mmio.h" #include "async_pf.h" #include "kvm_mm.h" +#include "vac.h" #include "vfio.h" #include <trace/events/ipi.h>
@@ -140,8 +141,6 @@ static int kvm_no_compat_open(struct inode *inode, struct file *file)#define KVM_COMPAT (c) .compat_ioctl = kvm_no_compat_ioctl, \ .open = kvm_no_compat_open#endif -static int hardware_enable_all (void ); -static void hardware_disable_all (void );static void kvm_io_bus_destroy (struct kvm_io_bus *bus);
@@ -5167,200 +5166,6 @@ static struct miscdevice kvm_dev = { &kvm_chardev_ops, }; -#ifdef CONFIG_KVM_GENERIC_HARDWARE_ENABLING -__visible bool kvm_rebooting; -EXPORT_SYMBOL_GPL (kvm_rebooting); - -static DEFINE_PER_CPU(bool, hardware_enabled); -static int kvm_usage_count; - -static int __hardware_enable_nolock (void ) -{ -if (__this_cpu_read (hardware_enabled)) -return 0 ; - -if (kvm_arch_hardware_enable ()) { -pr_info ("kvm: enabling virtualization on CPU%d failed\n" , -raw_smp_processor_id ()); -return -EIO ; - } - -__this_cpu_write (hardware_enabled, true); -return 0 ; -} - -static void hardware_enable_nolock (void *failed) -{ -if (__hardware_enable_nolock ()) -atomic_inc (failed); -} - -static int kvm_online_cpu (unsigned int cpu) -{ -int ret =0 ; - -/* -* Abort the CPU online process if hardware virtualization cannot -* be enabled. Otherwise running VMs would encounter unrecoverable -* errors when scheduled to this CPU. -*/ -mutex_lock (&kvm_lock); -if (kvm_usage_count) - ret =__hardware_enable_nolock (); -mutex_unlock (&kvm_lock); -return ret; -} - -static void hardware_disable_nolock (void *junk) -{ -/* -* Note, hardware_disable_all_nolock() tells all online CPUs to disable -* hardware, not just CPUs that successfully enabled hardware! -*/ -if (!__this_cpu_read (hardware_enabled)) -return ; - -kvm_arch_hardware_disable (); - -__this_cpu_write (hardware_enabled, false); -} - -static int kvm_offline_cpu (unsigned int cpu) -{ -mutex_lock (&kvm_lock); -if (kvm_usage_count) -hardware_disable_nolock (NULL ); -mutex_unlock (&kvm_lock); -return 0 ; -} - -static void hardware_disable_all_nolock (void ) -{ -BUG_ON (!kvm_usage_count); - - kvm_usage_count--; -if (!kvm_usage_count) -on_each_cpu (hardware_disable_nolock,NULL ,1 ); -} - -static void hardware_disable_all (void ) -{ -cpus_read_lock (); -mutex_lock (&kvm_lock); -hardware_disable_all_nolock (); -mutex_unlock (&kvm_lock); -cpus_read_unlock (); -} - -static int hardware_enable_all (void ) -{ -atomic_t failed =ATOMIC_INIT (0 ); -int r; - -/* -* Do not enable hardware virtualization if the system is going down. -* If userspace initiated a forced reboot, e.g. reboot -f, then it's -* possible for an in-flight KVM_CREATE_VM to trigger hardware enabling -* after kvm_reboot() is called. Note, this relies on system_state -* being set _before_ kvm_reboot(), which is why KVM uses a syscore ops -* hook instead of registering a dedicated reboot notifier (the latter -* runs before system_state is updated). -*/ -if (system_state ==SYSTEM_HALT || system_state ==SYSTEM_POWER_OFF || - system_state ==SYSTEM_RESTART ) -return -EBUSY ; - -/* -* When onlining a CPU, cpu_online_mask is set before kvm_online_cpu() -* is called, and so on_each_cpu() between them includes the CPU that -* is being onlined. As a result, hardware_enable_nolock() may get -* invoked before kvm_online_cpu(), which also enables hardware if the -* usage count is non-zero. Disable CPU hotplug to avoid attempting to -* enable hardware multiple times. -*/ -cpus_read_lock (); -mutex_lock (&kvm_lock); - - r =0 ; - - kvm_usage_count++; -if (kvm_usage_count ==1 ) { -on_each_cpu (hardware_enable_nolock, &failed,1 ); - -if (atomic_read (&failed)) { -hardware_disable_all_nolock (); - r = -EBUSY ; - } - } - -mutex_unlock (&kvm_lock); -cpus_read_unlock (); - -return r; -} - -static void kvm_shutdown (void ) -{ -/* -* Disable hardware virtualization and set kvm_rebooting to indicate -* that KVM has asynchronously disabled hardware virtualization, i.e. -* that relevant errors and exceptions aren't entirely unexpected. -* Some flavors of hardware virtualization need to be disabled before -* transferring control to firmware (to perform shutdown/reboot), e.g. -* on x86, virtualization can block INIT interrupts, which are used by -* firmware to pull APs back under firmware control. Note, this path -* is used for both shutdown and reboot scenarios, i.e. neither name is -* 100% comprehensive. -*/ -pr_info ("kvm: exiting hardware virtualization\n" ); - kvm_rebooting = true; -on_each_cpu (hardware_disable_nolock,NULL ,1 ); -} - -static int kvm_suspend (void ) -{ -/* -* Secondary CPUs and CPU hotplug are disabled across the suspend/resume -* callbacks, i.e. no need to acquire kvm_lock to ensure the usage count -* is stable. Assert that kvm_lock is not held to ensure the system -* isn't suspended while KVM is enabling hardware. Hardware enabling -* can be preempted, but the task cannot be frozen until it has dropped -* all locks (userspace tasks are frozen via a fake signal). -*/ -lockdep_assert_not_held (&kvm_lock); -lockdep_assert_irqs_disabled (); - -if (kvm_usage_count) -hardware_disable_nolock (NULL ); -return 0 ; -} - -static void kvm_resume (void ) -{ -lockdep_assert_not_held (&kvm_lock); -lockdep_assert_irqs_disabled (); - -if (kvm_usage_count) -WARN_ON_ONCE (__hardware_enable_nolock ()); -} - -static struct syscore_ops kvm_syscore_ops = { - .suspend = kvm_suspend, - .resume = kvm_resume, - .shutdown = kvm_shutdown, -}; -#else /* CONFIG_KVM_GENERIC_HARDWARE_ENABLING */ -static int hardware_enable_all (void ) -{ -return 0 ; -} - -static void hardware_disable_all (void ) -{ - -} -#endif /* CONFIG_KVM_GENERIC_HARDWARE_ENABLING */ -static void kvm_iodevice_destructor (struct kvm_io_device *dev) {if (dev->ops->destructor)
virt/kvm/vac.c +177 -0
180 lines not on this page · raw message
virt/kvm/vac.h +26 -0
@@ -3,4 +3,30 @@#ifndef __KVM_VAC_H__#define __KVM_VAC_H__ +#ifdef CONFIG_KVM_GENERIC_HARDWARE_ENABLING + +#include <linux/kvm_host.h> +#include <linux/syscore_ops.h> + +int kvm_online_cpu (unsigned int cpu); +int kvm_offline_cpu (unsigned int cpu); +void hardware_disable_all (void ); +int hardware_enable_all (void ); + +extern struct notifier_block kvm_reboot_notifier; + +extern struct syscore_ops kvm_syscore_ops; + +#else /* CONFIG_KVM_GENERIC_HARDWARE_ENABLING */ +static inline int hardware_enable_all (void ) +{ +return 0 ; +} + +static inline void hardware_disable_all (void ) +{ + +} +#endif /* CONFIG_KVM_GENERIC_HARDWARE_ENABLING */ +#endif
Signature · 1 line
2.42.0.869.gea05f2083d-goog
RFC PATCH 6/14 KVM: x86: Move user return msr operations out of KVM
In reply to Anish GhulatiMove kvm_user_return_msrs into VAC. Create helper functions to access user return msrs from KVM and (temporarily) expose them via vac.h. When more code is moved to VAC these functions will no longer need to be public and can be made internal.
--- arch/x86/include/asm/kvm_host.h | 10 --- arch/x86/kvm/cpuid.c | 1 + arch/x86/kvm/svm/svm.c | 1 + arch/x86/kvm/vac.c | 131 +++++++++++++++++++++++++++++ arch/x86/kvm/vac.h | 34 ++++++++ arch/x86/kvm/vmx/vmx.c | 1 + arch/x86/kvm/x86.c | 142 ++------------------------------ 7 files changed, 173 insertions(+), 147 deletions(-)
arch/x86/include/asm/kvm_host.h +0 -10
@@ -1785,7 +1785,6 @@ struct kvm_arch_async_pf {bool direct_map; }; -extern u32 __read_mostly kvm_nr_uret_msrs;extern u64 __read_mostly host_efer;extern bool __read_mostly allow_smaller_maxphyaddr;extern bool __read_mostly enable_apicv;
@@ -2139,15 +2138,6 @@ int kvm_pv_send_ipi(struct kvm *kvm, unsigned long ipi_bitmap_low, unsigned long ipi_bitmap_high, u32 min, unsigned long icr, int op_64_bit); -int kvm_add_user_return_msr (u32 msr); -int kvm_find_user_return_msr (u32 msr); -int kvm_set_user_return_msr (unsigned index,u64 val,u64 mask); - -static inline bool kvm_is_supported_user_return_msr (u32 msr) -{ -return kvm_find_user_return_msr (msr) >=0 ; -} -u64 kvm_scale_tsc (u64 tsc,u64 ratio);u64 kvm_read_l1_tsc (struct kvm_vcpu *vcpu,u64 host_tsc);u64 kvm_calc_nested_tsc_offset (u64 l1_offset,u64 l2_offset,u64 l2_multiplier);
arch/x86/kvm/cpuid.c +1 -0
@@ -28,6 +28,7 @@#include "trace.h" #include "pmu.h" #include "xen.h" +#include "vac.h" /* * Unlike "struct cpuinfo_x86.x86_capability", kvm_cpu_caps doesn't need to be
arch/x86/kvm/svm/svm.c +1 -0
@@ -5,6 +5,7 @@#include "irq.h" #include "mmu.h" #include "kvm_cache_regs.h" +#include "vac.h" #include "x86.h" #include "smm.h" #include "cpuid.h"
arch/x86/kvm/vac.c +131 -0
134 lines not on this page · raw message
arch/x86/kvm/vac.h +34 -0
@@ -3,4 +3,38 @@#ifndef ARCH_X86_KVM_VAC_H #define ARCH_X86_KVM_VAC_H +#include <linux/user-return-notifier.h> + +/* +* Restoring the host value for MSRs that are only consumed when running in +* usermode, e.g. SYSCALL MSRs and TSC_AUX, can be deferred until the CPU +* returns to userspace, i.e. the kernel can run with the guest's value. +*/ +#define KVM_MAX_NR_USER_RETURN_MSRS 16 + +struct kvm_user_return_msrs { +struct user_return_notifier urn; +bool registered; +struct kvm_user_return_msr_values { +u64 host; +u64 curr; + } values[KVM_MAX_NR_USER_RETURN_MSRS ]; +}; + +extern u32 __read_mostly kvm_nr_uret_msrs; + +int kvm_alloc_user_return_msrs (void ); +void kvm_free_user_return_msrs (void ); +int kvm_add_user_return_msr (u32 msr); +int kvm_find_user_return_msr (u32 msr); +int kvm_set_user_return_msr (unsigned int slot,u64 value,u64 mask); +void kvm_on_user_return (struct user_return_notifier *urn); +void kvm_user_return_msr_cpu_online (void ); +void drop_user_return_notifiers (void ); + +static inline bool kvm_is_supported_user_return_msr (u32 msr) +{ +return kvm_find_user_return_msr (msr) >=0 ; +} +#endif // ARCH_X86_KVM_VAC_H
arch/x86/kvm/vmx/vmx.c +1 -0
@@ -64,6 +64,7 @@#include "vmcs12.h" #include "vmx.h" #include "x86.h" +#include "vac.h" #include "smm.h" #ifdef MODULE
arch/x86/kvm/x86.c +5 -137
179 lines not on this page · raw message
Signature · 1 line
2.42.0.869.gea05f2083d-goog
RFC PATCH 7/14 KVM: SVM: Move shared SVM data structures into VAC
In reply to Anish GhulatiMove svm_cpu_data into VAC.
TODO: Explain why this data should be shared between KVMs and should be made global by moving it into VAC.
--- arch/x86/kvm/svm/svm.c | 9 ++++++++- arch/x86/kvm/svm/svm.h | 16 +--------------- arch/x86/kvm/svm/vac.c | 5 +++++ arch/x86/kvm/svm/vac.h | 23 +++++++++++++++++++++++ 4 files changed, 37 insertions(+), 16 deletions(-) create mode 100644 arch/x86/kvm/svm/vac.h
arch/x86/kvm/svm/svm.c +8 -1
@@ -234,7 +234,14 @@ static u8 rsm_ins_bytes[] = "\x0f\xaa";static unsigned long iopm_base; -DEFINE_PER_CPU(struct svm_cpu_data, svm_data); +struct kvm_ldttss_desc { +u16 limit0; +u16 base0; +unsigned base1:8 , type:5 , dpl:2 , p:1 ; +unsigned limit1:4 , zero0:3 , g:1 , base2:8 ; +u32 base3; +u32 zero1; +} __attribute__((packed));/* * Only MSR_TSC_AUX is switched via the user return hook. EFER is switched via
arch/x86/kvm/svm/svm.h +1 -15
@@ -24,6 +24,7 @@#include "cpuid.h" #include "kvm_cache_regs.h" +#include "vac.h" #define __sme_page_pa (x) __sme_set(page_to_pfn(x) << PAGE_SHIFT)
@@ -291,21 +292,6 @@ struct vcpu_svm {bool guest_gif; }; -struct svm_cpu_data { -u64 asid_generation; -u32 max_asid; -u32 next_asid; -u32 min_asid; - -struct page *save_area; -unsigned long save_area_pa; - -struct vmcb *current_vmcb; - -/* index = sev_asid, value = vmcb pointer */ -struct vmcb **sev_vmcbs; -}; - DECLARE_PER_CPU(struct svm_cpu_data, svm_data);void recalc_intercepts (struct vcpu_svm *svm);
arch/x86/kvm/svm/vac.c +5 -0
@@ -1,2 +1,7 @@// SPDX-License-Identifier: GPL-2.0-only +#include <linux/percpu-defs.h> + +#include "vac.h" + +DEFINE_PER_CPU(struct svm_cpu_data, svm_data);
arch/x86/kvm/svm/vac.h new file +23 -0
@@ -0,0 +1,23 @@ +// SPDX-License-Identifier: GPL-2.0-only +// +#ifndef ARCH_X86_KVM_SVM_VAC_H +#define ARCH_X86_KVM_SVM_VAC_H + +#include "../vac.h" + +struct svm_cpu_data { +u64 asid_generation; +u32 max_asid; +u32 next_asid; +u32 min_asid; + +struct page *save_area; +unsigned long save_area_pa; + +struct vmcb *current_vmcb; + +/* index = sev_asid, value = vmcb pointer */ +struct vmcb **sev_vmcbs; +}; + +#endif // ARCH_X86_KVM_SVM_VAC_H
Signature · 1 line
2.42.0.869.gea05f2083d-goog
RFC PATCH 8/14 KVM: VMX: Move shared VMX data structures into VAC
In reply to Anish GhulatiMove vmxarea and current_vmcs into VAC.
Move VPID bitmap into the VAC
TODO: Explain why this data needs to be shared among multiple KVM modules and moved into VAC.
--- arch/x86/kvm/vmx/nested.c | 1 + arch/x86/kvm/vmx/vac.c | 47 +++++++++++++++++++++++++++++++++++++++ arch/x86/kvm/vmx/vac.h | 12 ++++++++++ arch/x86/kvm/vmx/vmx.c | 41 +++++----------------------------- arch/x86/kvm/vmx/vmx.h | 2 -- 5 files changed, 65 insertions(+), 38 deletions(-) create mode 100644 arch/x86/kvm/vmx/vac.h
arch/x86/kvm/vmx/nested.c +1 -0
@@ -14,6 +14,7 @@#include "pmu.h" #include "sgx.h" #include "trace.h" +#include "vac.h" #include "vmx.h" #include "x86.h" #include "smm.h"
arch/x86/kvm/vmx/vac.c +47 -0
49 lines not on this page · raw message
arch/x86/kvm/vmx/vac.h new file +12 -0
@@ -0,0 +1,12 @@ +// SPDX-License-Identifier: GPL-2.0-only + +#include <asm/vmx.h> + +#include "../vac.h" +#include "vmcs.h" + +void vac_set_vmxarea (struct vmcs *vmcs,int cpu); + +struct vmcs *vac_get_vmxarea (int cpu); +int allocate_vpid (void ); +void free_vpid (int vpid);
arch/x86/kvm/vmx/vmx.c +5 -36
89 lines not on this page · raw message
arch/x86/kvm/vmx/vmx.h +0 -2
@@ -376,8 +376,6 @@ struct kvm_vmx {void vmx_vcpu_load_vmcs (struct kvm_vcpu *vcpu,int cpu,struct loaded_vmcs *buddy); -int allocate_vpid (void ); -void free_vpid (int vpid);void vmx_set_constant_host_state (struct vcpu_vmx *vmx);void vmx_prepare_switch_to_guest (struct kvm_vcpu *vcpu); void vmx_set_host_fs_gs(struct vmcs_host_state *host, u16 fs_sel, u16 gs_sel,
Signature · 1 line
2.42.0.869.gea05f2083d-goog
RFC PATCH 9/14 KVM: x86: Move shared KVM state into VAC
In reply to Anish GhulatiFrom: Venkatesh Srinivas <[email protected]>
Move kcpu_kick_mask and vm_running_vcpu* from arch neutral KVM code into VAC.
TODO: Explain why this needs to be moved into VAC.
--- virt/kvm/kvm_main.c | 6 ++++-- virt/kvm/vac.c | 5 +++++ virt/kvm/vac.h | 3 +++ 3 files changed, 12 insertions(+), 2 deletions(-)
virt/kvm/kvm_main.c +4 -2
@@ -108,7 +108,6 @@ LIST_HEAD(vm_list);static struct kmem_cache *kvm_vcpu_cache;static __read_mostly struct preempt_ops kvm_preempt_ops; -static DEFINE_PER_CPU(struct kvm_vcpu *, kvm_running_vcpu);struct dentry *kvm_debugfs_dir;EXPORT_SYMBOL_GPL (kvm_debugfs_dir);
@@ -150,7 +149,10 @@ static void kvm_uevent_notify_change(unsigned int type, struct kvm *kvm);static unsigned long long kvm_createvm_count;static unsigned long long kvm_active_vms; -static DEFINE_PER_CPU(cpumask_var_t, cpu_kick_mask); +__weak void kvm_arch_mmu_notifier_invalidate_range (struct kvm *kvm, +unsigned long start,unsigned long end) +{ +}__weak void kvm_arch_guest_memory_reclaimed (struct kvm *kvm) {
virt/kvm/vac.c +5 -0
@@ -6,6 +6,11 @@#include <linux/percpu.h> #include <linux/mutex.h> +DEFINE_PER_CPU (cpumask_var_t, cpu_kick_mask); +EXPORT_SYMBOL (cpu_kick_mask); + +DEFINE_PER_CPU(struct kvm_vcpu *, kvm_running_vcpu); +#ifdef CONFIG_KVM_GENERIC_HARDWARE_ENABLING DEFINE_MUTEX (vac_lock);
virt/kvm/vac.h +3 -0
@@ -29,4 +29,7 @@ static inline void hardware_disable_all(void) }#endif /* CONFIG_KVM_GENERIC_HARDWARE_ENABLING */ +DECLARE_PER_CPU (cpumask_var_t, cpu_kick_mask); +DECLARE_PER_CPU(struct kvm_vcpu *, kvm_running_vcpu); +#endif
Signature · 1 line
2.42.0.869.gea05f2083d-goog
Re: [RFC PATCH 09/14] KVM: x86: Move shared KVM state into VAC
Quoted 5 lines · Anish Ghulati
From: Venkatesh Srinivas <[email protected]>
Move
kcpu_kick_maskand vm_running_vcpu* from arch neutral KVM code into VAC.
Hello, Venkatesh, Anish
IMO, the allocation code for cpu_kick_mask has to be moved too.
Thanks
Lai
Sean Christopherson
maintainerRe: [RFC PATCH 09/14] KVM: x86: Move shared KVM state into VAC
Quoted 10 lines · Lai Jiangshan
Quoted 5 lines · Anish Ghulati
From: Venkatesh Srinivas <[email protected]>
Move
kcpu_kick_maskand vm_running_vcpu* from arch neutral KVM code into VAC.Hello, Venkatesh, Anish
IMO, the allocation code for
cpu_kick_maskhas to be moved too.
I'm pretty sure this patch should be dropped. I can't think of any reason why cpu_kick_mask needs to be in VAC, and kvm_running_vcpu definitely needs to be per-KVM.
RFC PATCH 10/14 KVM: VMX: Move VMX enable and disable into VAC
In reply to Anish GhulatiMove loaded_vmcss_on_cpu into VAC. loaded_vmcss_on_cpu is a list of VMCSs that have been loaded on a CPU; when offlining or kexec/crashing, this needs to be VMCLEAR'd.
Register and unregister callbacks for vmx_emergency_disable in vac_vmx_init/exit. These are init and exit functions for the VMX portion of VAC. Temporarily call init and exit from vmx_init and __vmx_exit. This will change once VAC is a module (the init/exit will be called via module init and exit functions).
Move the call to hv_reset_evmcs from vmx_hardware_disable to vmx_module_exit. This is because vmx_hardware_enable/disable is now part of VAC.
--- arch/x86/kvm/vac.h | 14 +++ arch/x86/kvm/vmx/vac.c | 190 +++++++++++++++++++++++++++++++++++++++++ arch/x86/kvm/vmx/vac.h | 7 +- arch/x86/kvm/vmx/vmx.c | 182 ++------------------------------------- 4 files changed, 219 insertions(+), 174 deletions(-)
arch/x86/kvm/vac.h +14 -0
@@ -5,6 +5,20 @@#include <linux/user-return-notifier.h> +int __init vac_init (void ); +void vac_exit (void ); + +#ifdef CONFIG_KVM_INTEL +int __init vac_vmx_init (void ); +void vac_vmx_exit (void ); +#else +int __init vac_vmx_init (void ) +{ +return 0 ; +} +void vac_vmx_exit (void ) {} +#endif +/* * Restoring the host value for MSRs that are only consumed when running in * usermode, e.g. SYSCALL MSRs and TSC_AUX, can be deferred until the CPU
arch/x86/kvm/vmx/vac.c +190 -0
203 lines not on this page · raw message
arch/x86/kvm/vmx/vac.h +6 -1
@@ -9,4 +9,9 @@ void vac_set_vmxarea(struct vmcs *vmcs, int cpu);struct vmcs *vac_get_vmxarea (int cpu);int allocate_vpid (void ); -void free_vpid (int vpid); +void add_vmcs_to_loaded_vmcss_on_cpu ( +struct list_head *loaded_vmcss_on_cpu_link, +int cpu); +void loaded_vmcs_clear (struct loaded_vmcs *loaded_vmcs); +int vmx_hardware_enable (void ); +void vmx_hardware_disable (void );
arch/x86/kvm/vmx/vmx.c +9 -173
230 lines not on this page · raw message
Signature · 1 line
2.42.0.869.gea05f2083d-goog
RFC PATCH 11/14 KVM: SVM: Move SVM enable and disable into VAC
In reply to Anish GhulatiMove SVM's hardware enable and disable into VAC.
Similar to VMX this requires a temporary call to new init and exit functions within VAC, and moving svm_init_erratum_383 into svm_init instead of hardware enable.
Delete __svm_exit and make svm_module_exit a noop.
--- arch/x86/kvm/svm/sev.c | 2 +- arch/x86/kvm/svm/svm.c | 129 ++---------------------------------- arch/x86/kvm/svm/svm.h | 4 +- arch/x86/kvm/svm/svm_data.h | 23 +++++++ arch/x86/kvm/svm/vac.c | 116 ++++++++++++++++++++++++++++++++ arch/x86/kvm/svm/vac.h | 23 +++---- arch/x86/kvm/vac.h | 12 ++++ arch/x86/kvm/vmx/vac.h | 5 ++ 8 files changed, 175 insertions(+), 139 deletions(-) create mode 100644 arch/x86/kvm/svm/svm_data.h
arch/x86/kvm/svm/sev.c +1 -1
@@ -28,6 +28,7 @@#include "mmu.h" #include "x86.h" #include "svm.h" +#include "svm_data.h" #include "svm_ops.h" #include "cpuid.h" #include "trace.h"
@@ -68,7 +69,6 @@ module_param_named(debug_swap, sev_es_debug_swap_enabled, bool, 0444);static u8 sev_enc_bit;static DECLARE_RWSEM (sev_deactivate_lock);static DEFINE_MUTEX (sev_bitmap_lock); -unsigned int max_sev_asid;static unsigned int min_sev_asid;static unsigned long sev_me_mask;static unsigned int nr_asids;
arch/x86/kvm/svm/svm.c +7 -122
177 lines not on this page · raw message
arch/x86/kvm/svm/svm.h +1 -3
@@ -24,7 +24,7 @@#include "cpuid.h" #include "kvm_cache_regs.h" -#include "vac.h" +#include "svm_data.h" #define __sme_page_pa (x) __sme_set(page_to_pfn(x) << PAGE_SHIFT)
@@ -651,8 +651,6 @@ void avic_refresh_virtual_apic_mode(struct kvm_vcpu *vcpu);#define GHCB_VERSION_MIN 1ULL -extern unsigned int max_sev_asid; -void sev_vm_destroy (struct kvm *kvm);int sev_mem_enc_ioctl (struct kvm *kvm,void __user *argp); int sev_mem_enc_register_region(struct kvm *kvm,
arch/x86/kvm/svm/svm_data.h new file +23 -0
@@ -0,0 +1,23 @@ +// SPDX-License-Identifier: GPL-2.0-only + +#ifndef ARCH_X86_KVM_SVM_DATA_H +#define ARCH_X86_KVM_SVM_DATA_H + +struct svm_cpu_data { +u64 asid_generation; +u32 max_asid; +u32 next_asid; +u32 min_asid; + +struct page *save_area; +unsigned long save_area_pa; + +struct vmcb *current_vmcb; + +/* index = sev_asid, value = vmcb pointer */ +struct vmcb **sev_vmcbs; +}; + +extern unsigned int max_sev_asid; + +#endif // ARCH_X86_KVM_SVM_DATA_H
arch/x86/kvm/svm/vac.c +116 -0
123 lines not on this page · raw message
arch/x86/kvm/svm/vac.h +10 -13
@@ -1,23 +1,20 @@// SPDX-License-Identifier: GPL-2.0-only -// +#ifndef ARCH_X86_KVM_SVM_VAC_H #define ARCH_X86_KVM_SVM_VAC_H #include "../vac.h" +#include "svm_data.h" -struct svm_cpu_data { -u64 asid_generation; -u32 max_asid; -u32 next_asid; -u32 min_asid; - -struct page *save_area; -unsigned long save_area_pa; +static int tsc_scaling = true; -struct vmcb *current_vmcb; +/* +* Set osvw_len to higher value when updated Revision Guides +* are published and we know what the new status bits are +*/ +static uint64_t osvw_len =4 , osvw_status; -/* index = sev_asid, value = vmcb pointer */ -struct vmcb **sev_vmcbs; -}; +int svm_hardware_enable (void ); +void svm_hardware_disable (void );#endif // ARCH_X86_KVM_SVM_VAC_H
arch/x86/kvm/vac.h +12 -0
@@ -19,6 +19,18 @@ int __init vac_vmx_init(void)void vac_vmx_exit (void ) {}#endif +#ifdef CONFIG_KVM_AMD +int __init vac_svm_init (void ); +void vac_svm_exit (void ); +#else +int __init vac_svm_init (void ) +{ +return 0 ; +} +void vac_svm_exit (void ) {} +#endif + +/* * Restoring the host value for MSRs that are only consumed when running in * usermode, e.g. SYSCALL MSRs and TSC_AUX, can be deferred until the CPU
arch/x86/kvm/vmx/vac.h +5 -0
@@ -1,5 +1,8 @@// SPDX-License-Identifier: GPL-2.0-only +#ifndef ARCH_X86_KVM_VMX_VAC_H +#define ARCH_X86_KVM_VMX_VAC_H +#include <asm/vmx.h> #include "../vac.h"
@@ -15,3 +18,5 @@ void add_vmcs_to_loaded_vmcss_on_cpu(void loaded_vmcs_clear (struct loaded_vmcs *loaded_vmcs);int vmx_hardware_enable (void );void vmx_hardware_disable (void ); + +#endif // ARCH_X86_KVM_VMX_VAC_H
Signature · 1 line
2.42.0.869.gea05f2083d-goog
RFC PATCH 12/14 KVM: x86: Move VMX and SVM support checks into VAC
In reply to Anish Ghulatikvm_is_***_supported checks to see if VMX and SVM are supported on the host. Move this to VAC because it needs to be called before each h/w enable and disable call.
--- arch/x86/kvm/svm/svm.c | 45 +----------------------------------------- arch/x86/kvm/svm/vac.c | 43 ++++++++++++++++++++++++++++++++++++++++ arch/x86/kvm/vac.h | 4 ++++ arch/x86/kvm/vmx/vac.c | 29 +++++++++++++++++++++++++++ arch/x86/kvm/vmx/vmx.c | 31 +---------------------------- arch/x86/kvm/x86.h | 6 ------ 6 files changed, 78 insertions(+), 80 deletions(-)
arch/x86/kvm/svm/svm.c +1 -44
@@ -515,52 +515,9 @@ static void svm_init_osvw(struct kvm_vcpu *vcpu) vcpu->arch.osvw.status |=1 ; } -static bool __kvm_is_svm_supported (void ) -{ -int cpu =smp_processor_id (); -struct cpuinfo_x86 *c = &cpu_data (cpu); - -u64 vm_cr; - -if (c->x86_vendor !=X86_VENDOR_AMD && - c->x86_vendor !=X86_VENDOR_HYGON ) { -pr_err ("CPU %d isn't AMD or Hygon\n" , cpu); -return false; - } - -if (!cpu_has (c,X86_FEATURE_SVM )) { -pr_err ("SVM not supported by CPU %d\n" , cpu); -return false; - } - -if (cc_platform_has (CC_ATTR_GUEST_MEM_ENCRYPT )) { -pr_info ("KVM is unsupported when running as an SEV guest\n" ); -return false; - } - -rdmsrl (MSR_VM_CR , vm_cr); -if (vm_cr & (1 <<SVM_VM_CR_SVM_DISABLE )) { -pr_err ("SVM disabled (by BIOS) in MSR_VM_CR on CPU %d\n" , cpu); -return false; - } - -return true; -} - -bool kvm_is_svm_supported (void ) -{ -bool supported; - -migrate_disable (); - supported =__kvm_is_svm_supported (); -migrate_enable (); - -return supported; -} -static int svm_check_processor_compat (void ) { -if (!__kvm_is_svm_supported ()) +if (!kvm_is_svm_supported ())return -EIO ;return 0 ;
arch/x86/kvm/svm/vac.c +43 -0
49 lines not on this page · raw message
arch/x86/kvm/vac.h +4 -0
@@ -9,9 +9,11 @@ int __init vac_init(void);void vac_exit (void );#ifdef CONFIG_KVM_INTEL +bool kvm_is_vmx_supported (void );int __init vac_vmx_init (void );void vac_vmx_exit (void );#else +bool kvm_is_vmx_supported(void) { return false }int __init vac_vmx_init (void ) {return 0 ;
@@ -20,9 +22,11 @@ void vac_vmx_exit(void) {}#endif #ifdef CONFIG_KVM_AMD +bool kvm_is_svm_supported (void );int __init vac_svm_init (void );void vac_svm_exit (void );#else +bool kvm_is_svm_supported(void) { return false }int __init vac_svm_init (void ) {return 0 ;
arch/x86/kvm/vmx/vac.c +29 -0
@@ -31,6 +31,35 @@ struct vmcs *vac_get_vmxarea(int cpu) static DECLARE_BITMAP(vmx_vpid_bitmap, VMX_NR_VPIDS);static DEFINE_SPINLOCK (vmx_vpid_lock); +static bool __kvm_is_vmx_supported (void ) +{ +int cpu =smp_processor_id (); + +if (!(cpuid_ecx (1 ) &feature_bit (VMX ))) { +pr_err ("VMX not supported by CPU %d\n" , cpu); +return false; + } + +if (!this_cpu_has (X86_FEATURE_MSR_IA32_FEAT_CTL ) || + !this_cpu_has (X86_FEATURE_VMX )) { +pr_err ("VMX not enabled (by BIOS) in MSR_IA32_FEAT_CTL on CPU %d\n" , cpu); +return false; + } + +return true; +} + +bool kvm_is_vmx_supported (void ) +{ +bool supported; + +migrate_disable (); + supported =__kvm_is_vmx_supported (); +migrate_enable (); + +return supported; +} +int allocate_vpid (void ) {int vpid;
arch/x86/kvm/vmx/vmx.c +1 -30
@@ -2625,42 +2625,13 @@ static int setup_vmcs_config(struct vmcs_config *vmcs_conf,return 0 ; } -static bool __kvm_is_vmx_supported (void ) -{ -int cpu =smp_processor_id (); - -if (!(cpuid_ecx (1 ) &feature_bit (VMX ))) { -pr_err ("VMX not supported by CPU %d\n" , cpu); -return false; - } - -if (!this_cpu_has (X86_FEATURE_MSR_IA32_FEAT_CTL ) || - !this_cpu_has (X86_FEATURE_VMX )) { -pr_err ("VMX not enabled (by BIOS) in MSR_IA32_FEAT_CTL on CPU %d\n" , cpu); -return false; - } - -return true; -} - -bool kvm_is_vmx_supported (void ) -{ -bool supported; - -migrate_disable (); - supported =__kvm_is_vmx_supported (); -migrate_enable (); - -return supported; -} -static int vmx_check_processor_compat (void ) {int cpu =raw_smp_processor_id ();struct vmcs_config vmcs_conf;struct vmx_capability vmx_cap; -if (!__kvm_is_vmx_supported ()) +if (!kvm_is_vmx_supported ())return -EIO ;if (setup_vmcs_config (&vmcs_conf, &vmx_cap) <0 ) {
arch/x86/kvm/x86.h +0 -6
@@ -10,18 +10,12 @@#include "kvm_emulate.h" #ifdef CONFIG_KVM_AMD -bool kvm_is_svm_supported (void );int __init svm_init (void );void svm_module_exit (void ); -#else -bool kvm_is_svm_supported (void ) {return false; }#endif #ifdef CONFIG_KVM_INTEL -bool kvm_is_vmx_supported (void );int __init vmx_init (void );void vmx_module_exit (void ); -#else -bool kvm_is_vmx_supported (void ) {return false; }#endif struct kvm_caps {
Signature · 1 line
2.42.0.869.gea05f2083d-goog
RFC PATCH 13/14 KVM: x86: VAC: Move all hardware enable/disable code into VAC
In reply to Anish GhulatiDe-indirect hardware enable and disable. Now that all of these functions are in the VAC, they don't need to be called via an indirect ops table and static call.
--- arch/x86/include/asm/kvm-x86-ops.h | 2 - arch/x86/kvm/svm/svm.c | 2 - arch/x86/kvm/svm/svm_ops.h | 1 + arch/x86/kvm/vac.c | 46 +++++++++++- arch/x86/kvm/vac.h | 9 ++- arch/x86/kvm/vmx/vmx.c | 2 - arch/x86/kvm/vmx/vmx_ops.h | 1 + arch/x86/kvm/x86.c | 117 ----------------------------- arch/x86/kvm/x86.h | 2 - include/linux/kvm_host.h | 2 + virt/kvm/vac.h | 5 ++ 11 files changed, 58 insertions(+), 131 deletions(-)
arch/x86/include/asm/kvm-x86-ops.h +0 -2
@@ -16,8 +16,6 @@ BUILD_BUG_ON(1)*/ KVM_X86_OP(vendor_exit) KVM_X86_OP(check_processor_compatibility) -KVM_X86_OP(hardware_enable) -KVM_X86_OP(hardware_disable) KVM_X86_OP(hardware_unsetup) KVM_X86_OP(has_emulated_msr) KVM_X86_OP(vcpu_after_set_cpuid)
arch/x86/kvm/svm/svm.c +0 -2
@@ -4739,8 +4739,6 @@ static struct kvm_x86_ops svm_x86_ops __initdata = { .check_processor_compatibility = svm_check_processor_compat, .hardware_unsetup = svm_hardware_unsetup, - .hardware_enable = svm_hardware_enable, - .hardware_disable = svm_hardware_disable, .has_emulated_msr = svm_has_emulated_msr, .vcpu_create = svm_vcpu_create,
arch/x86/kvm/svm/svm_ops.h +1 -0
@@ -4,6 +4,7 @@#include <linux/compiler_types.h> +#include "../vac.h" #include "x86.h" #define svm_asm(insn, clobber...) \
arch/x86/kvm/vac.c +44 -2
70 lines not on this page · raw message
arch/x86/kvm/vac.h +5 -4
@@ -5,13 +5,14 @@#include <linux/user-return-notifier.h> -int __init vac_init (void ); -void vac_exit (void ); +void kvm_spurious_fault (void );#ifdef CONFIG_KVM_INTEL bool kvm_is_vmx_supported (void );int __init vac_vmx_init (void );void vac_vmx_exit (void ); +int vmx_hardware_enable (void ); +void vmx_hardware_disable (void );#else bool kvm_is_vmx_supported(void) { return false }int __init vac_vmx_init (void )
@@ -25,6 +26,8 @@ void vac_vmx_exit(void) {}bool kvm_is_svm_supported (void );int __init vac_svm_init (void );void vac_svm_exit (void ); +int svm_hardware_enable (void ); +void svm_hardware_disable (void );#else bool kvm_is_svm_supported(void) { return false }int __init vac_svm_init (void )
@@ -59,8 +62,6 @@ int kvm_add_user_return_msr(u32 msr);int kvm_find_user_return_msr (u32 msr);int kvm_set_user_return_msr (unsigned int slot,u64 value,u64 mask);void kvm_on_user_return (struct user_return_notifier *urn); -void kvm_user_return_msr_cpu_online (void ); -void drop_user_return_notifiers (void );static inline bool kvm_is_supported_user_return_msr (u32 msr) {
arch/x86/kvm/vmx/vmx.c +0 -2
@@ -8013,8 +8013,6 @@ static struct kvm_x86_ops vmx_x86_ops __initdata = { .hardware_unsetup = vmx_hardware_unsetup, - .hardware_enable = vmx_hardware_enable, - .hardware_disable = vmx_hardware_disable, .has_emulated_msr = vmx_has_emulated_msr, .vm_size = sizeof(struct kvm_vmx),
arch/x86/kvm/vmx/vmx_ops.h +1 -0
@@ -8,6 +8,7 @@#include "hyperv.h" #include "vmcs.h" +#include "../vac.h" #include "../x86.h" void vmread_error (unsigned long field);
arch/x86/kvm/x86.c +0 -117
141 lines not on this page · raw message
arch/x86/kvm/x86.h +0 -2
@@ -40,8 +40,6 @@ struct kvm_caps {u64 supported_perf_cap; }; -void kvm_spurious_fault (void ); -#define KVM_NESTED_VMENTER_CONSISTENCY_CHECK (consistency_check) \ ({ \ bool failed = (consistency_check); \
include/linux/kvm_host.h +2 -0
@@ -1467,9 +1467,11 @@ static inline void kvm_create_vcpu_debugfs(struct kvm_vcpu *vcpu) {}#endif #ifdef CONFIG_KVM_GENERIC_HARDWARE_ENABLING +#ifndef CONFIG_X86 int kvm_arch_hardware_enable (void );void kvm_arch_hardware_disable (void );#endif +#endif int kvm_arch_vcpu_runnable (struct kvm_vcpu *vcpu);bool kvm_arch_vcpu_in_kernel (struct kvm_vcpu *vcpu);int kvm_arch_vcpu_should_kick (struct kvm_vcpu *vcpu);
virt/kvm/vac.h +5 -0
@@ -13,6 +13,11 @@ int kvm_offline_cpu(unsigned int cpu);void hardware_disable_all (void );int hardware_enable_all (void ); +#ifdef CONFIG_X86 +int kvm_arch_hardware_enable (void ); +void kvm_arch_hardware_disable (void ); +#endif +extern struct notifier_block kvm_reboot_notifier;extern struct syscore_ops kvm_syscore_ops;
Signature · 1 line
2.42.0.869.gea05f2083d-goog
RFC PATCH 14/14 KVM: VAC: Bring up VAC as a new module
In reply to Anish GhulatiAdd Kconfig options to build VAC as a new module. Make KVM dependent on this new "base" module.
Add another Kconfig option to accept a postfix ID for multi-KVM. This option allows setting a postfix to KVM module and character device names to distinguish multiple KVMs running on the same host. Set the default value to null.
Opportunistically fix indentation on the Makefile.
Resolve TODOs by moving vac_vmx/svm_init/exit() calls to the module_init and module_exit functions of VAC.
Add exports for VAC data and functions that are required in KVM. Also make some functions private now that they are not needed outside VAC.
TODO: Fix the module name, which is currently set to kvm-vac.
--- arch/x86/kvm/Kconfig | 17 ++++++++++++++++ arch/x86/kvm/Makefile | 29 +++++++++++++++------------ arch/x86/kvm/svm/svm.c | 3 --- arch/x86/kvm/svm/vac.c | 8 +++++++- arch/x86/kvm/vac.c | 42 +++++++++++++++++++++++++++++++++++++-- arch/x86/kvm/vac.h | 2 -- arch/x86/kvm/vmx/nested.c | 5 +++-- arch/x86/kvm/vmx/vac.c | 25 ++++++++++++++++++++--- arch/x86/kvm/vmx/vac.h | 2 -- arch/x86/kvm/vmx/vmx.c | 14 +++++-------- arch/x86/kvm/x86.c | 7 ------- virt/kvm/Makefile.kvm | 15 +++++++------- virt/kvm/kvm_main.c | 7 ++++--- virt/kvm/vac.c | 7 +++++++ 14 files changed, 128 insertions(+), 55 deletions(-)
arch/x86/kvm/Kconfig +17 -0
@@ -17,10 +17,19 @@ menuconfig VIRTUALIZATION if VIRTUALIZATION +config VAC + tristate "Virtualization Acceleration Component (VAC)" + select KVM_GENERIC_HARDWARE_ENABLING + help + Support running multiple KVM modules on the same host. If VAC is not + selected to run as a separate module, it will run as part of KVM, and + the system will only support a single KVM. + config KVM tristate "Kernel-based Virtual Machine (KVM) support" depends on HIGH_RES_TIMERS depends on X86_LOCAL_APIC + depends on VAC select PREEMPT_NOTIFIERS select MMU_NOTIFIER select HAVE_KVM_IRQCHIP
@@ -60,6 +69,14 @@ config KVM If unsure, say N. +config KVM_ID + string "KVM: Postfix ID for multi-KVM" + depends on KVM + default "" + help + This is the postfix string to append to the KVM module and + character device to differentiate multiple KVM builds. + config KVM_WERROR bool "Compile KVM with -Werror" # KASAN may cause the build to fail due to larger frames
arch/x86/kvm/Makefile +16 -13
@@ -8,33 +8,36 @@ endif include $(srctree)/virt/kvm/Makefile.kvm -kvm-y += x86.o emulate.o i8259.o irq.o lapic.o \ +kvm-vac-y := $(KVM)/vac.o vac.o +kvm-vac-$(CONFIG_KVM_INTEL) += vmx/vac.o +kvm-vac-$(CONFIG_KVM_AMD) += svm/vac.o + +kvm$(CONFIG_KVM_ID)-y += x86.o emulate.o i8259.o irq.o lapic.o \ i8254.o ioapic.o irq_comm.o cpuid.o pmu.o mtrr.o \ hyperv.o debugfs.o mmu/mmu.o mmu/page_track.o \ mmu/spte.o -kvm-y += vac.o vmx/vac.o svm/vac.o - ifdef CONFIG_HYPERV -kvm-y += kvm_onhyperv.o +kvm$(CONFIG_KVM_ID)-y += kvm_onhyperv.o endif -kvm-$(CONFIG_X86_64) += mmu/tdp_iter.o mmu/tdp_mmu.o -kvm-$(CONFIG_KVM_XEN) += xen.o -kvm-$(CONFIG_KVM_SMM) += smm.o +kvm$(CONFIG_KVM_ID)-$(CONFIG_X86_64) += mmu/tdp_iter.o mmu/tdp_mmu.o +kvm$(CONFIG_KVM_ID)-$(CONFIG_KVM_XEN) += xen.o +kvm$(CONFIG_KVM_ID)-$(CONFIG_KVM_SMM) += smm.o -kvm-$(CONFIG_KVM_INTEL) += vmx/vmx.o vmx/vmenter.o vmx/pmu_intel.o vmx/vmcs12.o \ - vmx/hyperv.o vmx/nested.o vmx/posted_intr.o -kvm-$(CONFIG_X86_SGX_KVM) += vmx/sgx.o +kvm$(CONFIG_KVM_ID)-$(CONFIG_KVM_INTEL) += vmx/vmx.o vmx/vmenter.o vmx/pmu_intel.o vmx/vmcs12.o \ + vmx/hyperv.o vmx/nested.o vmx/posted_intr.o +kvm$(CONFIG_KVM_ID)-$(CONFIG_X86_SGX_KVM) += vmx/sgx.o -kvm-$(CONFIG_KVM_AMD) += svm/svm.o svm/vmenter.o svm/pmu.o svm/nested.o svm/avic.o \ - svm/sev.o svm/hyperv.o +kvm$(CONFIG_KVM_ID)-$(CONFIG_KVM_AMD) += svm/svm.o svm/vmenter.o svm/pmu.o svm/nested.o svm/avic.o \ + svm/sev.o svm/hyperv.o ifdef CONFIG_HYPERV kvm-$(CONFIG_KVM_AMD) += svm/svm_onhyperv.o endif -obj-$(CONFIG_KVM) += kvm.o +obj-$(CONFIG_VAC) += kvm-vac.o +obj-$(CONFIG_KVM) += kvm$(CONFIG_KVM_ID).o AFLAGS_svm/vmenter.o := -iquote $(obj) $(obj)/svm/vmenter.o: $(obj)/kvm-asm-offsets.h
arch/x86/kvm/svm/svm.c +0 -3
@@ -5166,9 +5166,6 @@ int __init svm_init(void)if (r)return r; -//TODO: Remove this init call once VAC is a module -vac_svm_init (); -/* * Common KVM initialization _must_ come last, after this, /dev/kvm is * exposed to userspace!
arch/x86/kvm/svm/vac.c +7 -1
@@ -8,7 +8,10 @@#include "vac.h" DEFINE_PER_CPU(struct svm_cpu_data, svm_data); +EXPORT_SYMBOL_GPL (svm_data); +unsigned int max_sev_asid; +EXPORT_SYMBOL_GPL (max_sev_asid);static bool __kvm_is_svm_supported (void ) {
@@ -52,6 +55,7 @@ bool kvm_is_svm_supported(void)return supported; } +EXPORT_SYMBOL_GPL (kvm_is_svm_supported);static inline void kvm_cpu_svm_disable (void ) {
@@ -87,6 +91,7 @@ void svm_hardware_disable(void)amd_pmu_disable_virt (); } +EXPORT_SYMBOL_GPL (svm_hardware_disable);int svm_hardware_enable (void ) {
@@ -152,6 +157,7 @@ int svm_hardware_enable(void)return 0 ; } +EXPORT_SYMBOL_GPL (svm_hardware_enable);int __init vac_svm_init (void ) {
@@ -160,7 +166,7 @@ int __init vac_svm_init(void)return 0 ; } -void vac_svm_exit (void ) +void __exit vac_svm_exit(void) {cpu_emergency_unregister_virt_callback (svm_emergency_disable); }
arch/x86/kvm/vac.c +40 -2
86 lines not on this page · raw message
arch/x86/kvm/vac.h +0 -2
@@ -56,8 +56,6 @@ struct kvm_user_return_msrs {extern u32 __read_mostly kvm_nr_uret_msrs; -int kvm_alloc_user_return_msrs (void ); -void kvm_free_user_return_msrs (void );int kvm_add_user_return_msr (u32 msr);int kvm_find_user_return_msr (u32 msr);int kvm_set_user_return_msr (unsigned int slot,u64 value,u64 mask);
arch/x86/kvm/vmx/nested.c +3 -2
@@ -307,7 +307,8 @@ static void free_nested(struct kvm_vcpu *vcpu) vmx->nested.vmxon = false; vmx->nested.smm.vmxon = false; vmx->nested.vmxon_ptr =INVALID_GPA ; -free_vpid (vmx->nested.vpid02); +if (enable_vpid) +free_vpid (vmx->nested.vpid02); vmx->nested.posted_intr_nv =-1 ; vmx->nested.current_vmptr =INVALID_GPA ;if (enable_shadow_vmcs) {
@@ -5115,7 +5116,7 @@ static int enter_vmx_operation(struct kvm_vcpu *vcpu) HRTIMER_MODE_ABS_PINNED); vmx->nested.preemption_timer.function = vmx_preemption_timer_fn; - vmx->nested.vpid02 =allocate_vpid (); + vmx->nested.vpid02 = enable_vpid ?allocate_vpid () :0 ; vmx->nested.vmcs02_initialized = false; vmx->nested.vmxon = true;
arch/x86/kvm/vmx/vac.c +22 -3
@@ -8,6 +8,10 @@#include "vmx_ops.h" #include "posted_intr.h" +// TODO: Move these to VAC +void vmclear_error (struct vmcs *vmcs,u64 phys_addr) {} +void invept_error (unsigned long ext,u64 eptp,gpa_t gpa) {} +/* * We maintain a per-CPU linked-list of VMCS loaded on that CPU. This is needed * when a CPU is brought down, and we need to VMCLEAR all VMCSs loaded on it.
@@ -17,16 +21,19 @@ static DEFINE_PER_CPU(struct list_head, loaded_vmcss_on_cpu); static DEFINE_PER_CPU(struct vmcs *, vmxarea);DEFINE_PER_CPU (struct vmcs *, current_vmcs); +EXPORT_SYMBOL_GPL (current_vmcs);void vac_set_vmxarea (struct vmcs *vmcs,int cpu) {per_cpu (vmxarea, cpu) = vmcs; } +EXPORT_SYMBOL_GPL (vac_set_vmxarea);struct vmcs *vac_get_vmxarea (int cpu) {return per_cpu (vmxarea, cpu); } +EXPORT_SYMBOL_GPL (vac_get_vmxarea); static DECLARE_BITMAP(vmx_vpid_bitmap, VMX_NR_VPIDS);static DEFINE_SPINLOCK (vmx_vpid_lock);
@@ -59,6 +66,7 @@ bool kvm_is_vmx_supported(void)return supported; } +EXPORT_SYMBOL_GPL (kvm_is_vmx_supported);int allocate_vpid (void ) {
@@ -75,6 +83,7 @@ int allocate_vpid(void)spin_unlock (&vmx_vpid_lock);return vpid; } +EXPORT_SYMBOL_GPL (allocate_vpid);void free_vpid (int vpid) {
@@ -84,6 +93,7 @@ void free_vpid(int vpid)__clear_bit (vpid, vmx_vpid_bitmap);spin_unlock (&vmx_vpid_lock); } +EXPORT_SYMBOL_GPL (free_vpid); void add_vmcs_to_loaded_vmcss_on_cpu( struct list_head *loaded_vmcss_on_cpu_link,
@@ -91,6 +101,7 @@ void add_vmcs_to_loaded_vmcss_on_cpu( {list_add (loaded_vmcss_on_cpu_link, &per_cpu (loaded_vmcss_on_cpu, cpu)); } +EXPORT_SYMBOL_GPL (add_vmcs_to_loaded_vmcss_on_cpu);static void __loaded_vmcs_clear (void *arg) {
@@ -130,6 +141,7 @@ void loaded_vmcs_clear(struct loaded_vmcs *loaded_vmcs) __loaded_vmcs_clear, loaded_vmcs, 1); } +EXPORT_SYMBOL_GPL (loaded_vmcs_clear);static int kvm_cpu_vmxon (u64 vmxon_pointer) {
@@ -175,11 +187,16 @@ int vmx_hardware_enable(void)return r; } -if (enable_ept) +// TODO: VAC: Since we can have a mix of KVMs with enable_ept=0 and =1, +// we need to perform a global INVEPT here. +// TODO: Check for the +// vmx_capability invept bit before executing this. +if (1 )ept_sync_global ();return 0 ; } +EXPORT_SYMBOL_GPL (vmx_hardware_enable);static void vmclear_local_loaded_vmcss (void ) {
@@ -246,6 +263,7 @@ void vmx_hardware_disable(void)intel_pt_handle_vmx (0 ); } +EXPORT_SYMBOL_GPL (vmx_hardware_disable);int __init vac_vmx_init (void ) {
@@ -254,7 +272,8 @@ int __init vac_vmx_init(void)for_each_possible_cpu (cpu) {INIT_LIST_HEAD (&per_cpu (loaded_vmcss_on_cpu, cpu)); -pi_init_cpu (cpu); +// TODO: Move posted interrupts list to VAC +// pi_init_cpu(cpu); }cpu_emergency_register_virt_callback (vmx_emergency_disable);
@@ -262,7 +281,7 @@ int __init vac_vmx_init(void)return 0 ; } -void vac_vmx_exit (void ) +void __exit vac_vmx_exit(void) {cpu_emergency_unregister_virt_callback (vmx_emergency_disable); }
arch/x86/kvm/vmx/vac.h +0 -2
@@ -16,7 +16,5 @@ void add_vmcs_to_loaded_vmcss_on_cpu(struct list_head *loaded_vmcss_on_cpu_link, int cpu);void loaded_vmcs_clear (struct loaded_vmcs *loaded_vmcs); -int vmx_hardware_enable (void ); -void vmx_hardware_disable (void );#endif // ARCH_X86_KVM_VMX_VAC_H
arch/x86/kvm/vmx/vmx.c +5 -9
@@ -7201,7 +7201,8 @@ static void vmx_vcpu_free(struct kvm_vcpu *vcpu)if (enable_pml)vmx_destroy_pml_buffer (vmx); -free_vpid (vmx->vpid); +if (enable_vpid) +free_vpid (vmx->vpid);nested_vmx_free_vcpu (vcpu);free_loaded_vmcs (vmx->loaded_vmcs); }
@@ -7219,7 +7220,7 @@ static int vmx_vcpu_create(struct kvm_vcpu *vcpu) err = -ENOMEM ; - vmx->vpid =allocate_vpid (); + vmx->vpid = enable_vpid ?allocate_vpid () :0 ;/* * If PML is turned on, failure on enabling PML just results in failure
@@ -7308,7 +7309,8 @@ static int vmx_vcpu_create(struct kvm_vcpu *vcpu) free_pml:vmx_destroy_pml_buffer (vmx); free_vpid: -free_vpid (vmx->vpid); +if (enable_vpid) +free_vpid (vmx->vpid);return err; }
@@ -7992,9 +7994,6 @@ static void __vmx_exit(void) { allow_smaller_maxphyaddr = false; -//TODO: Remove this exit call once VAC is a module -vac_vmx_exit (); -vmx_cleanup_l1d_flush (); }
@@ -8436,9 +8435,6 @@ int __init vmx_init(void)if (r) goto err_l1d_flush; -//TODO: Remove this init call once VAC is a module -vac_vmx_init (); -vmx_check_vmcs12_offsets ();/*
arch/x86/kvm/x86.c +0 -7
@@ -9274,10 +9274,6 @@ static int __kvm_x86_vendor_init(struct kvm_x86_init_ops *ops)return -ENOMEM ; } - r =kvm_alloc_user_return_msrs (); -if (r) - goto out_free_x86_emulator_cache; - r =kvm_mmu_vendor_module_init ();if (r) goto out_free_percpu;
@@ -9354,8 +9350,6 @@ static int __kvm_x86_vendor_init(struct kvm_x86_init_ops *ops) out_mmu_exit:kvm_mmu_vendor_module_exit (); out_free_percpu: -kvm_free_user_return_msrs (); -out_free_x86_emulator_cache:kmem_cache_destroy (x86_emulator_cache);return r; }
@@ -9393,7 +9387,6 @@ void kvm_x86_vendor_exit(void)#endif static_call (kvm_x86_hardware_unsetup)();kvm_mmu_vendor_module_exit (); -kvm_free_user_return_msrs ();kmem_cache_destroy (x86_emulator_cache);#ifdef CONFIG_KVM_XEN static_key_deferred_flush (&kvm_xen_enabled);
virt/kvm/Makefile.kvm +7 -8
@@ -7,13 +7,12 @@ ccflags-y += -I$(srctree)/$(src) -D__KVM__ KVM ?= ../../../virt/kvm -kvm-y := $(KVM)/kvm_main.o $(KVM)/eventfd.o $(KVM)/binary_stats.o +kvm$(CONFIG_KVM_ID)-y := $(KVM)/kvm_main.o $(KVM)/eventfd.o $(KVM)/binary_stats.o ifdef CONFIG_VFIO -kvm-y += $(KVM)/vfio.o +kvm$(CONFIG_KVM_ID)-y += $(KVM)/vfio.o endif -kvm-y += $(KVM)/vac.o -kvm-$(CONFIG_KVM_MMIO) += $(KVM)/coalesced_mmio.o -kvm-$(CONFIG_KVM_ASYNC_PF) += $(KVM)/async_pf.o -kvm-$(CONFIG_HAVE_KVM_IRQ_ROUTING) += $(KVM)/irqchip.o -kvm-$(CONFIG_HAVE_KVM_DIRTY_RING) += $(KVM)/dirty_ring.o -kvm-$(CONFIG_HAVE_KVM_PFNCACHE) += $(KVM)/pfncache.o +kvm$(CONFIG_KVM_ID)-$(CONFIG_KVM_MMIO) += $(KVM)/coalesced_mmio.o +kvm$(CONFIG_KVM_ID)-$(CONFIG_KVM_ASYNC_PF) += $(KVM)/async_pf.o +kvm$(CONFIG_KVM_ID)-$(CONFIG_HAVE_KVM_IRQ_ROUTING) += $(KVM)/irqchip.o +kvm$(CONFIG_KVM_ID)-$(CONFIG_HAVE_KVM_DIRTY_RING) += $(KVM)/dirty_ring.o +kvm$(CONFIG_KVM_ID)-$(CONFIG_HAVE_KVM_PFNCACHE) += $(KVM)/pfncache.o
virt/kvm/kvm_main.c +4 -3
@@ -5163,9 +5163,8 @@ static struct file_operations kvm_chardev_ops = { };static struct miscdevice kvm_dev = { -KVM_MINOR , -"kvm" , - &kvm_chardev_ops, + .minor =KVM_MINOR , + .fops = &kvm_chardev_ops, };static void kvm_iodevice_destructor (struct kvm_io_device *dev)
@@ -5914,7 +5913,9 @@ int kvm_init(unsigned vcpu_size, unsigned vcpu_align, struct module *module)/* * Registration _must_ be the very last thing done, as this exposes * /dev/kvm to userspace, i.e. all infrastructure must be setup! +* Append CONFIG_KVM_ID to the device name. */ + kvm_dev.name =kasprintf (GFP_KERNEL ,"kvm%s" ,CONFIG_KVM_ID ); r =misc_register (&kvm_dev);if (r) {pr_err ("kvm: misc device register failed\n" );
virt/kvm/vac.c +7 -0
@@ -10,6 +10,7 @@ DEFINE_PER_CPU(cpumask_var_t, cpu_kick_mask);EXPORT_SYMBOL (cpu_kick_mask); DEFINE_PER_CPU(struct kvm_vcpu *, kvm_running_vcpu); +EXPORT_SYMBOL_GPL (kvm_running_vcpu);#ifdef CONFIG_KVM_GENERIC_HARDWARE_ENABLING DEFINE_MUTEX (vac_lock);
@@ -56,6 +57,7 @@ int kvm_online_cpu(unsigned int cpu)mutex_unlock (&vac_lock);return ret; } +EXPORT_SYMBOL_GPL (kvm_online_cpu);static void hardware_disable_nolock (void *junk) {
@@ -79,6 +81,7 @@ int kvm_offline_cpu(unsigned int cpu)mutex_unlock (&vac_lock);return 0 ; } +EXPORT_SYMBOL_GPL (kvm_offline_cpu);static void hardware_disable_all_nolock (void ) {
@@ -97,6 +100,7 @@ void hardware_disable_all(void)mutex_unlock (&vac_lock);cpus_read_unlock (); } +EXPORT_SYMBOL_GPL (hardware_disable_all);int hardware_enable_all (void ) {
@@ -129,6 +133,7 @@ int hardware_enable_all(void)return r; } +EXPORT_SYMBOL_GPL (hardware_enable_all);static int kvm_reboot (struct notifier_block *notifier,unsigned long val,void *v)
@@ -176,10 +181,12 @@ struct notifier_block kvm_reboot_notifier = { .notifier_call = kvm_reboot, .priority =0 , }; +EXPORT_SYMBOL_GPL (kvm_reboot_notifier);struct syscore_ops kvm_syscore_ops = { .suspend = kvm_suspend, .resume = kvm_resume, }; +EXPORT_SYMBOL_GPL (kvm_syscore_ops);#endif
Signature · 1 line
2.42.0.869.gea05f2083d-goog
Quoted 10 lines · Anish Ghulati
This series is a rough, PoC-quality RFC to allow (un)loading and running multiple KVM modules simultaneously on a single host, e.g. to deploy fixes, mitigations, and/or new features without having to drain all VMs from the host. Multi-KVM will also allow running the "same" KVM module with different params, e.g. to run trusted VMs with different mitigations.
The goal of this RFC is to get feedback on the idea itself and the high-level approach. In particular, we're looking for input on:
Quoted 6 lines
- Combining kvm_intel.ko and kvm_amd.ko into kvm.ko
- Exposing multiple/dev/kvmXdevices viaKconfig
- The name and prefix of the new base moduleFeedback on individual patches is also welcome, but please keep in mind that this is very much a work in-progress
Hello Anish
Scarce effort on multi-KVM can be seen in the mail list albeit many companies enable multi-KVM internally.
I'm glad that you took a big step in upstreaming it. And I hope it can be materialized soon.
Quoted 5 lines
- Move system-wide virtualization resource management to a new base module to avoid collisions between different KVM modules, e.g. VPIDs and ASIDs need to be unique per VM, and callbacks from IRQ handlers need to be mediated so that things like PMIs get to the right KVM instance.
perf_register_guest_info_callbacks() also accesses to system-wide resources, but I don't see its relating code including kvm_guest_cbs being moved to AVC.
Quoted 7 lines
- Refactor KVM to make all upgradable assets visible only to KVM, i.e. make KVM a black box, so that the layout/size of things like "struct
kvm_vcpu" isn't exposed to the kernel at-large.- Fold kvm_intel.ko and kvm_amd.ko into kvm.ko to avoid complications having to generate unique symbols for every symbol exported by kvm.ko.
The sizes of kvm_intel.ko and kvm_amd.ko are big, and there is only 1G in the kernel available for modules. So I don't think folding two vendors' code into kvm.ko is a good idea.
Since the symbols in the new module are invisible outside, I recommend:
new kvm_intel.ko = kvm_intel.ko + kvm.ko
new kvm_amd.ko = kvm_amd.ko + kvm.ko
Quoted 4 lines
- Add a
Kconfigstring to allow defining a device and module postfix at build time, e.g. to create kvmX.ko and/dev/kvmX.
Quoted 8 lines
The proposed name of the new base module is vac.ko, a.k.a. Virtualization Acceleration Code (Unupgradable Units Module). Childish humor aside, "vac" is a unique name in the kernel and hopefully in x86 and hardware terminology, is a unique name in the kernel and hopefully in x86 and hardware terminology, e.g.
git grep vac_yields no hits in the kernel. It also has the same number of characters as "kvm", e.g. the namespace can be modified without needing whitespace adjustment if we want to go that route.
How about the name kvm_base.ko?
And the variable/function name in it can still be kvm_foo (other than kvm_base_foo).
Thanks
Lai
Sean Christopherson
maintainerQuoted 28 lines · Lai Jiangshan
Quoted 10 lines · Anish Ghulati
This series is a rough, PoC-quality RFC to allow (un)loading and running multiple KVM modules simultaneously on a single host, e.g. to deploy fixes, mitigations, and/or new features without having to drain all VMs from the host. Multi-KVM will also allow running the "same" KVM module with different params, e.g. to run trusted VMs with different mitigations.
The goal of this RFC is to get feedback on the idea itself and the high-level approach. In particular, we're looking for input on:
Quoted 6 lines
- Combining kvm_intel.ko and kvm_amd.ko into kvm.ko
- Exposing multiple/dev/kvmXdevices viaKconfig
- The name and prefix of the new base moduleFeedback on individual patches is also welcome, but please keep in mind that this is very much a work in-progress
Hello Anish
Scarce effort on multi-KVM can be seen in the mail list albeit many companies enable multi-KVM internally.
I'm glad that you took a big step in upstreaming it. And I hope it can be materialized soon.
Quoted 1 line
Quoted 7 lines
Quoted 4 lines
- Move system-wide virtualization resource management to a new base module to avoid collisions between different KVM modules, e.g. VPIDs and ASIDs need to be unique per VM, and callbacks from IRQ handlers need to be mediated so that things like PMIs get to the right KVM instance.
perf_register_guest_info_callbacks()also accesses to system-wide resources, but I don't see its relating code includingkvm_guest_cbsbeing moved to AVC.
Yeah, that's on the TODO list. IIRC, the plan is to have VAC register a single callback with perf, and then have VAC deal with invoking the callback(s) for the correct KVM instance.
Quoted 7 lines
Quoted 6 lines
- Refactor KVM to make all upgradable assets visible only to KVM, i.e. make KVM a black box, so that the layout/size of things like "struct
kvm_vcpu" isn't exposed to the kernel at-large.- Fold kvm_intel.ko and kvm_amd.ko into kvm.ko to avoid complications having to generate unique symbols for every symbol exported by kvm.ko.
Quoted 7 lines
The sizes of kvm_intel.ko and kvm_amd.ko are big, and there is only 1G in the kernel available for modules. So I don't think folding two vendors' code into kvm.ko is a good idea.
Since the symbols in the new module are invisible outside, I recommend:
new kvm_intel.ko = kvm_intel.ko + kvm.ko
new kvm_amd.ko = kvm_amd.ko + kvm.ko
Yeah, Paolo also suggested this at LPC.
Quoted 12 lines
Quoted 11 lines
- Add a
Kconfigstring to allow defining a device and module postfix at build time, e.g. to create kvmX.ko and/dev/kvmX.The proposed name of the new base module is vac.ko, a.k.a. Virtualization Acceleration Code (Unupgradable Units Module). Childish humor aside, "vac" is a unique name in the kernel and hopefully in x86 and hardware terminology, is a unique name in the kernel and hopefully in x86 and hardware terminology, e.g.
git grep vac_yields no hits in the kernel. It also has the same number of characters as "kvm", e.g. the namespace can be modified without needing whitespace adjustment if we want to go that route.
Quoted 4 lines
How about the name kvm_base.ko?
And the variable/function name in it can still be
kvm_foo(other thankvm_base_foo).
My preference is to have a unique name that allows us to differentitate between the "base" module/code and KVM code. Verbal conversations about all of this get quite confusing because it's not always clear whether "base KVM" refers to what is currently kvm.ko, or what would become kvm_base.ko/vac.ko.
Quoted 72 lines · Sean Christopherson
Quoted 28 lines · Lai Jiangshan
Quoted 10 lines · Anish Ghulati
This series is a rough, PoC-quality RFC to allow (un)loading and running multiple KVM modules simultaneously on a single host, e.g. to deploy fixes, mitigations, and/or new features without having to drain all VMs from the host. Multi-KVM will also allow running the "same" KVM module with different params, e.g. to run trusted VMs with different mitigations.
The goal of this RFC is to get feedback on the idea itself and the high-level approach. In particular, we're looking for input on:
Quoted 6 lines
- Combining kvm_intel.ko and kvm_amd.ko into kvm.ko
- Exposing multiple/dev/kvmXdevices viaKconfig
- The name and prefix of the new base moduleFeedback on individual patches is also welcome, but please keep in mind that this is very much a work in-progress
Hello Anish
Scarce effort on multi-KVM can be seen in the mail list albeit many companies enable multi-KVM internally.
I'm glad that you took a big step in upstreaming it. And I hope it can be materialized soon.
Quoted 1 line
Quoted 7 lines
Quoted 4 lines
- Move system-wide virtualization resource management to a new base module to avoid collisions between different KVM modules, e.g. VPIDs and ASIDs need to be unique per VM, and callbacks from IRQ handlers need to be mediated so that things like PMIs get to the right KVM instance.
perf_register_guest_info_callbacks()also accesses to system-wide resources, but I don't see its relating code includingkvm_guest_cbsbeing moved to AVC.Yeah, that's on the TODO list. IIRC, the plan is to have VAC register a single callback with perf, and then have VAC deal with invoking the callback(s) for the correct KVM instance.
Quoted 7 lines
Quoted 6 lines
- Refactor KVM to make all upgradable assets visible only to KVM, i.e. make KVM a black box, so that the layout/size of things like "struct
kvm_vcpu" isn't exposed to the kernel at-large.- Fold kvm_intel.ko and kvm_amd.ko into kvm.ko to avoid complications having to generate unique symbols for every symbol exported by kvm.ko.
Quoted 7 lines
The sizes of kvm_intel.ko and kvm_amd.ko are big, and there is only 1G in the kernel available for modules. So I don't think folding two vendors' code into kvm.ko is a good idea.
Since the symbols in the new module are invisible outside, I recommend:
new kvm_intel.ko = kvm_intel.ko + kvm.ko
new kvm_amd.ko = kvm_amd.ko + kvm.koYeah, Paolo also suggested this at LPC.
Quoted 14 lines
Quoted 11 lines
- Add a
Kconfigstring to allow defining a device and module postfix at build time, e.g. to create kvmX.ko and/dev/kvmX.The proposed name of the new base module is vac.ko, a.k.a. Virtualization Acceleration Code (Unupgradable Units Module). Childish humor aside, "vac" is a unique name in the kernel and hopefully in x86 and hardware terminology, is a unique name in the kernel and hopefully in x86 and hardware terminology, e.g.
git grep vac_yields no hits in the kernel. It also has the same number of characters as "kvm", e.g. the namespace can be modified without needing whitespace adjustment if we want to go that route.How about the name kvm_base.ko?
Quoted 8 lines
Quoted 2 lines
And the variable/function name in it can still be
kvm_foo(other thankvm_base_foo).My preference is to have a unique name that allows us to differentitate between the "base" module/code and KVM code. Verbal conversations about all of this get quite confusing because it's not always clear whether "base KVM" refers to what is currently kvm.ko, or what would become
kvm_base.ko/vac.ko.
Hi, Sean and Anish.
Sorry for revisiting this topic after a long time. I haven't seen any new updates regarding this topic/series, and I didn’t find any recent activity on the GitHub repository. Is the multi-KVM topic still being considered for upstreaming, or is there anything blocking this?
As Lai pointed out, we also have a similar multi-KVM implementation in our internal environment, so we are quite interested in this topic. Recently, when we upgraded our kernel version, we found that maintaining multi-KVM has become a significant burden. We are willing to move forward with it if multi-KVM is still accepted for upstream. So I look forward to feedback from the maintainers.
From what I've seen, the recent patch set that enables VMX/SVM during booting is a good starting point for multi-KVM as well.
Thanks!
Sean Christopherson
maintainerQuoted 4 lines · Hou Wenlong
Sorry for revisiting this topic after a long time. I haven't seen any new updates regarding this topic/series, and I didn’t find any recent activity on the GitHub repository. Is the multi-KVM topic still being considered for upstreaming, or is there anything blocking this?
We have abandoned upstreaming multi-KVM. The operational cost+complexity is too high relative to the benefits, especially when factoring in things like ASI and live patching, and the benefits are almost entirely obsoleted by kernel live update support.
Quoted 4 lines
As Lai pointed out, we also have a similar multi-KVM implementation in our internal environment, so we are quite interested in this topic. Recently, when we upgraded our kernel version, we found that maintaining multi-KVM has become a significant burden.
Yeah, I can imagine the pain all too well. :-/
Quoted 5 lines
We are willing to move forward with it if multi-KVM is still accepted for upstream. So I look forward to feedback from the maintainers.
From what I've seen, the recent patch set that enables VMX/SVM during booting is a good starting point for multi-KVM as well.
I have mixed feelings on multi-KVM. Without considering maintenance and support costs, I still love the idea of reworking the kernel to support running multiple hypervisors concurrently. But as I explained in the first cover letter of that series[0], there is a massive amount of complexity, both in initial development and ongoing maintenance, needed to provide such infrastructure:
: I got quite far long on rebasing some internal patches we have to extract the : core virtualization bits out of KVM x86, but as I paged back in all of the : things we had punted on (because they were waaay out of scope for our needs), : I realized more and more that providing truly generic virtualization : instrastructure is vastly different than providing infrastructure that can be : shared by multiple instances of KVM (or things very similar to KVM)[1]. :
: So while I still don't want to blindly do VMXON, I also think that trying to : actually support another in-tree hypervisor, without an imminent user to drive : the development, is a waste of resources, and would saddle KVM with a pile of : pointless complexity.
For deployment to a relatively homogeneous fleet, many of the pain points can be avoided by either avoiding them entirely or making the settings "inflexible", because there is effectively one use case and so such caveats are a non-issue. But those types of simplifications don't work upstream, e.g. saying "eVMCS is unsupported if multi-KVM is possible" instead of moving eVMCS enabling to a base module isn't acceptable.
So I guess my "official" stance is that I'm not opposed to upstreaming multi-KVM (or similar) functionality, but I'm not exactly in favor of it either. And practically speaking, because multi-KVM would be in constant conflict with so much ongoing/new feature support (both in software and hardware), and is not a priority for anyone pursuing kernel live update, upstreaming would be likely take several years, without any guarantee of a successful landing.
[0] https://lore.kernel.org/all/[email protected]
[1] https://lore.kernel.org/all/[email protected]
Quoted 11 lines · Sean Christopherson
Quoted 4 lines · Hou Wenlong
Sorry for revisiting this topic after a long time. I haven't seen any new updates regarding this topic/series, and I didn’t find any recent activity on the GitHub repository. Is the multi-KVM topic still being considered for upstreaming, or is there anything blocking this?
We have abandoned upstreaming multi-KVM. The operational cost+complexity is too high relative to the benefits, especially when factoring in things like ASI and live patching, and the benefits are almost entirely obsoleted by kernel live update support.
We need to look into the new features to see if they’re compatible with multi-KVM and how we can integrate them effectively. This is definitely challenging work. We also have the option to explore the kernel live update now.
Quoted 45 lines
Quoted 4 lines
As Lai pointed out, we also have a similar multi-KVM implementation in our internal environment, so we are quite interested in this topic. Recently, when we upgraded our kernel version, we found that maintaining multi-KVM has become a significant burden.
Yeah, I can imagine the pain all too well. :-/
Quoted 5 lines
We are willing to move forward with it if multi-KVM is still accepted for upstream. So I look forward to feedback from the maintainers.
From what I've seen, the recent patch set that enables VMX/SVM during booting is a good starting point for multi-KVM as well.
I have mixed feelings on multi-KVM. Without considering maintenance and support costs, I still love the idea of reworking the kernel to support running multiple hypervisors concurrently. But as I explained in the first cover letter of that series[0], there is a massive amount of complexity, both in initial development and ongoing maintenance, needed to provide such infrastructure:
: I got quite far long on rebasing some internal patches we have to extract the : core virtualization bits out of KVM x86, but as I paged back in all of the : things we had punted on (because they were waaay out of scope for our needs), : I realized more and more that providing truly generic virtualization : instrastructure is vastly different than providing infrastructure that can be : shared by multiple instances of KVM (or things very similar to KVM)[1]. :
: So while I still don't want to blindly do VMXON, I also think that trying to : actually support another in-tree hypervisor, without an imminent user to drive : the development, is a waste of resources, and would saddle KVM with a pile of : pointless complexity.For deployment to a relatively homogeneous fleet, many of the pain points can be avoided by either avoiding them entirely or making the settings "inflexible", because there is effectively one use case and so such caveats are a non-issue. But those types of simplifications don't work upstream, e.g. saying "eVMCS is unsupported if multi-KVM is possible" instead of moving eVMCS enabling to a base module isn't acceptable.
So I guess my "official" stance is that I'm not opposed to upstreaming multi-KVM (or similar) functionality, but I'm not exactly in favor of it either. And practically speaking, because multi-KVM would be in constant conflict with so much ongoing/new feature support (both in software and hardware), and is not a priority for anyone pursuing kernel live update, upstreaming would be likely take several years, without any guarantee of a successful landing.
Quoted 2 lines
[0] https://lore.kernel.org/all/[email protected]
[1] https://lore.kernel.org/all/[email protected]
Got it, thanks for your feedback!