KVM: VMX: Stub out enable_evmcs static key
Subsystems (4)
Sean Christopherson
maintainerv2 cover KVM: VMX: Stub out enable_evmcs static key
Stub out and rename the eVMCS static key when CONFIG_HYPERV=n. gcc (as of gcc-12) isn't clever enough to elide the nop placeholder when there's no code guarded by a static branch. With gcc-12, because of the vast number of VMCS accesses, eliminating the nops reduces the size of kvm-intel.ko by ~7.5% (200KiB).
Please holler if you would rather patch 3 be squashed into patch 2, i.e. add the wrapper and rename the key in one go. I split them because the combined changelog was getting into "here's a list of changes" territory.
Patch 1 is tangentially related cleanup.
Applies on [email protected]:kvm-x86/linux.git vmx.
v2:
- Collect reviews. [Vitaly]
- Rename wrapper. [Vitaly, Paolo]
- Rename key too.
v1: https://lore.kernel.org/all/[email protected]
Sean Christopherson (3):
KVM: nVMX: Move EVMCS1_SUPPORT_* macros to hyperv.c
KVM: VMX: Stub out enable_evmcs static key for CONFIG_HYPERV=n
KVM: VMX: Rename "KVM is using eVMCS" static key to match its wrapper
arch/x86/kvm/vmx/hyperv.c | 107 +++++++++++++++++++++++++++++++++- arch/x86/kvm/vmx/hyperv.h | 115 +++---------------------------------- arch/x86/kvm/vmx/vmx.c | 17 +++--- arch/x86/kvm/vmx/vmx_ops.h | 22 +++---- 4 files changed, 133 insertions(+), 128 deletions(-)
base-commit: 93827a0a36396f2fd6368a54a020f420c8916e9b
Signature · 1 line
2.39.1.581.gbfd45094c4-goog
Sean Christopherson
maintainerPATCH v2 1/3 KVM: nVMX: Move EVMCS1_SUPPORT_* macros to hyperv.c
Move the macros that define the set of VMCS controls that are supported
by eVMCS1 from hyperv.h to hyperv.c, i.e. make them "private". The
macros should never be consumed directly by KVM at-large since the "final" set of supported controls depends on guest CPUID.
No functional change intended.
--- arch/x86/kvm/vmx/hyperv.c | 105 ++++++++++++++++++++++++++++++++++++++ arch/x86/kvm/vmx/hyperv.h | 105 -------------------------------------- 2 files changed, 105 insertions(+), 105 deletions(-)
arch/x86/kvm/vmx/hyperv.c +105 -0
@@ -13,6 +13,111 @@#define CC KVM_NESTED_VMENTER_CONSISTENCY_CHECK +/* +* Enlightened VMCSv1 doesn't support these: +* +* POSTED_INTR_NV = 0x00000002, +* GUEST_INTR_STATUS = 0x00000810, +* APIC_ACCESS_ADDR = 0x00002014, +* POSTED_INTR_DESC_ADDR = 0x00002016, +* EOI_EXIT_BITMAP0 = 0x0000201c, +* EOI_EXIT_BITMAP1 = 0x0000201e, +* EOI_EXIT_BITMAP2 = 0x00002020, +* EOI_EXIT_BITMAP3 = 0x00002022, +* GUEST_PML_INDEX = 0x00000812, +* PML_ADDRESS = 0x0000200e, +* VM_FUNCTION_CONTROL = 0x00002018, +* EPTP_LIST_ADDRESS = 0x00002024, +* VMREAD_BITMAP = 0x00002026, +* VMWRITE_BITMAP = 0x00002028, +* +* TSC_MULTIPLIER = 0x00002032, +* PLE_GAP = 0x00004020, +* PLE_WINDOW = 0x00004022, +* VMX_PREEMPTION_TIMER_VALUE = 0x0000482E, +* +* Currently unsupported in KVM: +* GUEST_IA32_RTIT_CTL = 0x00002814, +*/ +#define EVMCS1_SUPPORTED_PINCTRL \ + (PIN_BASED_ALWAYSON_WITHOUT_TRUE_MSR | \ + PIN_BASED_EXT_INTR_MASK | \ + PIN_BASED_NMI_EXITING | \ + PIN_BASED_VIRTUAL_NMIS) + +#define EVMCS1_SUPPORTED_EXEC_CTRL \ + (CPU_BASED_ALWAYSON_WITHOUT_TRUE_MSR | \ + CPU_BASED_HLT_EXITING | \ + CPU_BASED_CR3_LOAD_EXITING | \ + CPU_BASED_CR3_STORE_EXITING | \ + CPU_BASED_UNCOND_IO_EXITING | \ + CPU_BASED_MOV_DR_EXITING | \ + CPU_BASED_USE_TSC_OFFSETTING | \ + CPU_BASED_MWAIT_EXITING | \ + CPU_BASED_MONITOR_EXITING | \ + CPU_BASED_INVLPG_EXITING | \ + CPU_BASED_RDPMC_EXITING | \ + CPU_BASED_INTR_WINDOW_EXITING | \ + CPU_BASED_CR8_LOAD_EXITING | \ + CPU_BASED_CR8_STORE_EXITING | \ + CPU_BASED_RDTSC_EXITING | \ + CPU_BASED_TPR_SHADOW | \ + CPU_BASED_USE_IO_BITMAPS | \ + CPU_BASED_MONITOR_TRAP_FLAG | \ + CPU_BASED_USE_MSR_BITMAPS | \ + CPU_BASED_NMI_WINDOW_EXITING | \ + CPU_BASED_PAUSE_EXITING | \ + CPU_BASED_ACTIVATE_SECONDARY_CONTROLS) + +#define EVMCS1_SUPPORTED_2NDEXEC \ + (SECONDARY_EXEC_VIRTUALIZE_X2APIC_MODE | \ + SECONDARY_EXEC_WBINVD_EXITING | \ + SECONDARY_EXEC_ENABLE_VPID | \ + SECONDARY_EXEC_ENABLE_EPT | \ + SECONDARY_EXEC_UNRESTRICTED_GUEST | \ + SECONDARY_EXEC_DESC | \ + SECONDARY_EXEC_ENABLE_RDTSCP | \ + SECONDARY_EXEC_ENABLE_INVPCID | \ + SECONDARY_EXEC_XSAVES | \ + SECONDARY_EXEC_RDSEED_EXITING | \ + SECONDARY_EXEC_RDRAND_EXITING | \ + SECONDARY_EXEC_TSC_SCALING | \ + SECONDARY_EXEC_ENABLE_USR_WAIT_PAUSE | \ + SECONDARY_EXEC_PT_USE_GPA | \ + SECONDARY_EXEC_PT_CONCEAL_VMX | \ + SECONDARY_EXEC_BUS_LOCK_DETECTION | \ + SECONDARY_EXEC_NOTIFY_VM_EXITING | \ + SECONDARY_EXEC_ENCLS_EXITING) + +#define EVMCS1_SUPPORTED_3RDEXEC (0ULL) + +#define EVMCS1_SUPPORTED_VMEXIT_CTRL \ + (VM_EXIT_ALWAYSON_WITHOUT_TRUE_MSR | \ + VM_EXIT_SAVE_DEBUG_CONTROLS | \ + VM_EXIT_ACK_INTR_ON_EXIT | \ + VM_EXIT_HOST_ADDR_SPACE_SIZE | \ + VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL | \ + VM_EXIT_SAVE_IA32_PAT | \ + VM_EXIT_LOAD_IA32_PAT | \ + VM_EXIT_SAVE_IA32_EFER | \ + VM_EXIT_LOAD_IA32_EFER | \ + VM_EXIT_CLEAR_BNDCFGS | \ + VM_EXIT_PT_CONCEAL_PIP | \ + VM_EXIT_CLEAR_IA32_RTIT_CTL) + +#define EVMCS1_SUPPORTED_VMENTRY_CTRL \ + (VM_ENTRY_ALWAYSON_WITHOUT_TRUE_MSR | \ + VM_ENTRY_LOAD_DEBUG_CONTROLS | \ + VM_ENTRY_IA32E_MODE | \ + VM_ENTRY_LOAD_IA32_PERF_GLOBAL_CTRL | \ + VM_ENTRY_LOAD_IA32_PAT | \ + VM_ENTRY_LOAD_IA32_EFER | \ + VM_ENTRY_LOAD_BNDCFGS | \ + VM_ENTRY_PT_CONCEAL_PIP | \ + VM_ENTRY_LOAD_IA32_RTIT_CTL) + +#define EVMCS1_SUPPORTED_VMFUNC (0) +DEFINE_STATIC_KEY_FALSE (enable_evmcs);#define EVMCS1_OFFSET (x) offsetof(struct hv_enlightened_vmcs, x)
arch/x86/kvm/vmx/hyperv.h +0 -105
111 lines not on this page · raw message
Signature · 1 line
2.39.1.581.gbfd45094c4-goog
Sean Christopherson
maintainerPATCH v2 2/3 KVM: VMX: Stub out enable_evmcs static key for CONFIG_HYPERV=n
In reply to Sean ChristophersonWrap enable_evmcs in a helper and stub it out when CONFIG_HYPERV=n in order to eliminate the static branch nop placeholders. clang-14 is clever enough to elide the nop, but gcc-12 is not. Stubbing out the key reduces the size of kvm-intel.ko by ~7.5% (200KiB) when compiled with gcc-12 (there are a _lot_ of VMCS accesses throughout KVM).
--- arch/x86/kvm/vmx/hyperv.c | 4 ++-- arch/x86/kvm/vmx/hyperv.h | 10 ++++++++-- arch/x86/kvm/vmx/vmx.c | 15 +++++++-------- arch/x86/kvm/vmx/vmx_ops.h | 22 +++++++++++----------- 4 files changed, 28 insertions(+), 23 deletions(-)
arch/x86/kvm/vmx/hyperv.c +2 -2
@@ -118,8 +118,6 @@#define EVMCS1_SUPPORTED_VMFUNC (0) -DEFINE_STATIC_KEY_FALSE (enable_evmcs); -#define EVMCS1_OFFSET (x) offsetof(struct hv_enlightened_vmcs, x)#define EVMCS1_FIELD (number, name, clean_field)[ROL16(number, 6)] = \ {EVMCS1_OFFSET(name), clean_field}
@@ -611,6 +609,8 @@ int nested_evmcs_check_controls(struct vmcs12 *vmcs12) }#if IS_ENABLED (CONFIG_HYPERV ) +DEFINE_STATIC_KEY_FALSE (enable_evmcs); +/* * KVM on Hyper-V always uses the latest known eVMCSv1 revision, the assumption * is: in case a feature has corresponding fields in eVMCS described and it was
arch/x86/kvm/vmx/hyperv.h +8 -2
@@ -16,8 +16,6 @@struct vmcs_config ; -DECLARE_STATIC_KEY_FALSE (enable_evmcs); -#define current_evmcs ((struct hv_enlightened_vmcs *)this_cpu_read(current_vmcs))#define KVM_EVMCS_VERSION 1
@@ -69,6 +67,13 @@ static inline u64 evmcs_read_any(struct hv_enlightened_vmcs *evmcs,#if IS_ENABLED (CONFIG_HYPERV ) +DECLARE_STATIC_KEY_FALSE (enable_evmcs); + +static __always_inline bool kvm_is_using_evmcs(void) +{ +return static_branch_unlikely (&enable_evmcs); +} + static __always_inline int get_evmcs_offset(unsigned long field,u16 *clean_field) {
@@ -158,6 +163,7 @@ static inline void evmcs_load(u64 phys_addr)void evmcs_sanitize_exec_ctrls (struct vmcs_config *vmcs_conf);#else /* !IS_ENABLED(CONFIG_HYPERV) */ +static __always_inline bool kvm_is_using_evmcs(void) { return false; } static __always_inline void evmcs_write64(unsigned long field, u64 value) {} static __always_inline void evmcs_write32(unsigned long field, u32 value) {} static __always_inline void evmcs_write16(unsigned long field, u16 value) {}
arch/x86/kvm/vmx/vmx.c +7 -8
@@ -595,7 +595,7 @@ static void hv_reset_evmcs(void) {struct hv_vp_assist_page *vp_ap; -if (!static_branch_unlikely (&enable_evmcs)) +if (!kvm_is_using_evmcs ())return ;/*
@@ -2818,8 +2818,7 @@ static int vmx_hardware_enable(void)* This can happen if we hot-added a CPU but failed to allocate * VP assist page for it. */ -if (static_branch_unlikely (&enable_evmcs) && - !hv_get_vp_assist_page (cpu)) +if (kvm_is_using_evmcs () && !hv_get_vp_assist_page (cpu))return -EFAULT ;intel_pt_handle_vmx (1 );
@@ -2871,7 +2870,7 @@ struct vmcs *alloc_vmcs_cpu(bool shadow, int cpu, gfp_t flags)memset (vmcs,0 , vmcs_config.size);/* KVM supports Enlightened VMCS v1 only */ -if (static_branch_unlikely (&enable_evmcs)) +if (kvm_is_using_evmcs ()) vmcs->hdr.revision_id =KVM_EVMCS_VERSION ;else vmcs->hdr.revision_id = vmcs_config.revision_id;
@@ -2966,7 +2965,7 @@ static __init int alloc_kvm_area(void)* still be marked with revision_id reported by * physical CPU. */ -if (static_branch_unlikely (&enable_evmcs)) +if (kvm_is_using_evmcs ()) vmcs->hdr.revision_id = vmcs_config.revision_id;per_cpu (vmxarea, cpu) = vmcs;
@@ -3936,7 +3935,7 @@ static void vmx_msr_bitmap_l01_changed(struct vcpu_vmx *vmx)* 'Enlightened MSR Bitmap' feature L0 needs to know that MSR * bitmap has changed. */ -if (IS_ENABLED (CONFIG_HYPERV ) &&static_branch_unlikely (&enable_evmcs)) { +if (kvm_is_using_evmcs ()) {struct hv_enlightened_vmcs *evmcs = (void *)vmx->vmcs01.vmcs;if (evmcs->hv_enlightenments_control.msr_bitmap)
@@ -7313,7 +7312,7 @@ static fastpath_t vmx_vcpu_run(struct kvm_vcpu *vcpu)vmx_vcpu_enter_exit (vcpu,__vmx_vcpu_run_flags (vmx));/* All fields are clean at this point */ -if (static_branch_unlikely (&enable_evmcs)) { +if (kvm_is_using_evmcs ()) { current_evmcs->hv_clean_fields |=HV_VMX_ENLIGHTENED_CLEAN_FIELD_ALL ;
@@ -7443,7 +7442,7 @@ static int vmx_vcpu_create(struct kvm_vcpu *vcpu)* feature only for vmcs01, KVM currently isn't equipped to realize any * performance benefits from enabling it for vmcs02. */ -if (IS_ENABLED (CONFIG_HYPERV ) &&static_branch_unlikely (&enable_evmcs) && +if (kvm_is_using_evmcs () && (ms_hyperv.nested_features &HV_X64_NESTED_MSR_BITMAP )) {struct hv_enlightened_vmcs *evmcs = (void *)vmx->vmcs01.vmcs;
arch/x86/kvm/vmx/vmx_ops.h +11 -11
@@ -147,7 +147,7 @@ static __always_inline unsigned long __vmcs_readl(unsigned long field) static __always_inline u16 vmcs_read16(unsigned long field) {vmcs_check16 (field); -if (static_branch_unlikely (&enable_evmcs)) +if (kvm_is_using_evmcs ())return evmcs_read16 (field);return __vmcs_readl (field); }
@@ -155,7 +155,7 @@ static __always_inline u16 vmcs_read16(unsigned long field) static __always_inline u32 vmcs_read32(unsigned long field) {vmcs_check32 (field); -if (static_branch_unlikely (&enable_evmcs)) +if (kvm_is_using_evmcs ())return evmcs_read32 (field);return __vmcs_readl (field); }
@@ -163,7 +163,7 @@ static __always_inline u32 vmcs_read32(unsigned long field) static __always_inline u64 vmcs_read64(unsigned long field) {vmcs_check64 (field); -if (static_branch_unlikely (&enable_evmcs)) +if (kvm_is_using_evmcs ())return evmcs_read64 (field);#ifdef CONFIG_X86_64 return __vmcs_readl (field);
@@ -175,7 +175,7 @@ static __always_inline u64 vmcs_read64(unsigned long field)static __always_inline unsigned long vmcs_readl (unsigned long field) {vmcs_checkl (field); -if (static_branch_unlikely (&enable_evmcs)) +if (kvm_is_using_evmcs ())return evmcs_read64 (field);return __vmcs_readl (field); }
@@ -222,7 +222,7 @@ static __always_inline void __vmcs_writel(unsigned long field, unsigned long val static __always_inline void vmcs_write16(unsigned long field, u16 value) {vmcs_check16 (field); -if (static_branch_unlikely (&enable_evmcs)) +if (kvm_is_using_evmcs ())return evmcs_write16 (field, value);__vmcs_writel (field, value);
@@ -231,7 +231,7 @@ static __always_inline void vmcs_write16(unsigned long field, u16 value) static __always_inline void vmcs_write32(unsigned long field, u32 value) {vmcs_check32 (field); -if (static_branch_unlikely (&enable_evmcs)) +if (kvm_is_using_evmcs ())return evmcs_write32 (field, value);__vmcs_writel (field, value);
@@ -240,7 +240,7 @@ static __always_inline void vmcs_write32(unsigned long field, u32 value) static __always_inline void vmcs_write64(unsigned long field, u64 value) {vmcs_check64 (field); -if (static_branch_unlikely (&enable_evmcs)) +if (kvm_is_using_evmcs ())return evmcs_write64 (field, value);__vmcs_writel (field, value);
@@ -252,7 +252,7 @@ static __always_inline void vmcs_write64(unsigned long field, u64 value) static __always_inline void vmcs_writel(unsigned long field, unsigned long value) {vmcs_checkl (field); -if (static_branch_unlikely (&enable_evmcs)) +if (kvm_is_using_evmcs ())return evmcs_write64 (field, value);__vmcs_writel (field, value);
@@ -262,7 +262,7 @@ static __always_inline void vmcs_clear_bits(unsigned long field, u32 mask) {BUILD_BUG_ON_MSG (__builtin_constant_p (field) && ((field) &0x6000 ) ==0x2000 ,"vmcs_clear_bits does not support 64-bit fields" ); -if (static_branch_unlikely (&enable_evmcs)) +if (kvm_is_using_evmcs ())return evmcs_write32 (field,evmcs_read32 (field) & ~mask);__vmcs_writel (field,__vmcs_readl (field) & ~mask);
@@ -272,7 +272,7 @@ static __always_inline void vmcs_set_bits(unsigned long field, u32 mask) {BUILD_BUG_ON_MSG (__builtin_constant_p (field) && ((field) &0x6000 ) ==0x2000 ,"vmcs_set_bits does not support 64-bit fields" ); -if (static_branch_unlikely (&enable_evmcs)) +if (kvm_is_using_evmcs ())return evmcs_write32 (field,evmcs_read32 (field) | mask);__vmcs_writel (field,__vmcs_readl (field) | mask);
@@ -289,7 +289,7 @@ static inline void vmcs_load(struct vmcs *vmcs) {u64 phys_addr =__pa (vmcs); -if (static_branch_unlikely (&enable_evmcs)) +if (kvm_is_using_evmcs ())return evmcs_load (phys_addr);vmx_asm1 (vmptrld,"m" (phys_addr), vmcs, phys_addr);
Signature · 1 line
2.39.1.581.gbfd45094c4-goog
Sean Christopherson
maintainerPATCH v2 3/3 KVM: VMX: Rename "KVM is using eVMCS" static key to match its wrapper
In reply to Sean ChristophersonRename enable_evmcs to __kvm_is_using_evmcs to match its wrapper, and to avoid confusion with enabling eVMCS for nested virtualization, i.e. have "enable eVMCS" be reserved for "enable eVMCS support for L1".
No functional change intended.
--- arch/x86/kvm/vmx/hyperv.c | 2 +- arch/x86/kvm/vmx/hyperv.h | 4 ++-- arch/x86/kvm/vmx/vmx.c | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-)
arch/x86/kvm/vmx/hyperv.c +1 -1
@@ -609,7 +609,7 @@ int nested_evmcs_check_controls(struct vmcs12 *vmcs12) }#if IS_ENABLED (CONFIG_HYPERV ) -DEFINE_STATIC_KEY_FALSE (enable_evmcs); +DEFINE_STATIC_KEY_FALSE (__kvm_is_using_evmcs);/* * KVM on Hyper-V always uses the latest known eVMCSv1 revision, the assumption
arch/x86/kvm/vmx/hyperv.h +2 -2
@@ -67,11 +67,11 @@ static inline u64 evmcs_read_any(struct hv_enlightened_vmcs *evmcs,#if IS_ENABLED (CONFIG_HYPERV ) -DECLARE_STATIC_KEY_FALSE (enable_evmcs); +DECLARE_STATIC_KEY_FALSE (__kvm_is_using_evmcs); static __always_inline bool kvm_is_using_evmcs(void) { -return static_branch_unlikely (&enable_evmcs); +return static_branch_unlikely (&__kvm_is_using_evmcs); } static __always_inline int get_evmcs_offset(unsigned long field,
arch/x86/kvm/vmx/vmx.c +1 -1
@@ -579,7 +579,7 @@ static __init void hv_init_evmcs(void)if (enlightened_vmcs) {pr_info ("Using Hyper-V Enlightened VMCS\n" ); -static_branch_enable (&enable_evmcs); +static_branch_enable (&__kvm_is_using_evmcs); }if (ms_hyperv.nested_features &HV_X64_NESTED_DIRECT_FLUSH )
Signature · 1 line
2.39.1.581.gbfd45094c4-goog
Re: [PATCH v2 3/3] KVM: VMX: Rename "KVM is using eVMCS" static key to match its wrapper
Quoted 49 lines · Sean Christopherson
Rename
enable_evmcsto__kvm_is_using_evmcsto match its wrapper, and to avoid confusion with enabling eVMCS for nested virtualization, i.e. have "enable eVMCS" be reserved for "enable eVMCS support for L1".No functional change intended.
Signed-off-by Sean Christopherson <[email protected]>--- arch/x86/kvm/vmx/hyperv.c | 2 +- arch/x86/kvm/vmx/hyperv.h | 4 ++-- arch/x86/kvm/vmx/vmx.c | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-)arch/x86/kvm/vmx/hyperv.c +1
-1@@ -609,7 +609,7 @@ int nested_evmcs_check_controls(struct vmcs12 *vmcs12) }#if IS_ENABLED (CONFIG_HYPERV ) -DEFINE_STATIC_KEY_FALSE (enable_evmcs); +DEFINE_STATIC_KEY_FALSE (__kvm_is_using_evmcs);/* * KVM on Hyper-V always uses the latest known eVMCSv1 revision, the assumption arch/x86/kvm/vmx/hyperv.h +2
-2@@ -67,11 +67,11 @@ static inline u64 evmcs_read_any(struct hv_enlightened_vmcs *evmcs,#if IS_ENABLED (CONFIG_HYPERV ) -DECLARE_STATIC_KEY_FALSE (enable_evmcs); +DECLARE_STATIC_KEY_FALSE (__kvm_is_using_evmcs); static __always_inline bool kvm_is_using_evmcs(void) { -return static_branch_unlikely (&enable_evmcs); +return static_branch_unlikely (&__kvm_is_using_evmcs); } static __always_inline int get_evmcs_offset(unsigned long field,arch/x86/kvm/vmx/vmx.c +0
-0
arch/x86/kvm/vmx/vmx.c static __init void hv_init_evmcs(void) · line 585
Quoted 8 lines
arch/x86/kvm/vmx/vmx.c +1
-1@@ -579,7 +579,7 @@ static __init void hv_init_evmcs(void)if (enlightened_vmcs) {pr_info ("Using Hyper-V Enlightened VMCS\n" ); -static_branch_enable (&enable_evmcs); +static_branch_enable (&__kvm_is_using_evmcs); }if (ms_hyperv.nested_features &HV_X64_NESTED_DIRECT_FLUSH )
Signature · 1 line
Vitaly
Queued, thanks.
Paolo
Sean Christopherson
maintainerQuoted 1 line · Paolo Bonzini
Queued, thanks.
Paolo,
Are you grabbing this for 6.3 or 6.4? If it's for 6.4, what is your plan for 6.4? I assumed we were taking the same approach as we did for 6.3, where you handle the current cycle (stabilizing 6.3) and I focus on the next cycle (building 6.4).
Paolo Bonzini
maintainerIl mar 14 mar 2023, 15:29 Sean Christopherson <[email protected]> ha scritto:
Quoted 9 lines · Paolo Bonzini
Quoted 1 line
Queued, thanks.
Paolo,
Are you grabbing this for 6.3 or 6.4? If it's for 6.4, what is your plan for 6.4? I assumed we were taking the same approach as we did for 6.3, where you handle the current cycle (stabilizing 6.3) and I focus on the next cycle (building 6.4).
This one is for 6.4. What we did for 6.3 included me merging a handful of series that were not included in the previous merge window; so that's what I did today. If that's okay for you, once the -rc3 pull request is sent (probably tomorrow) I will push to kvm/next and that will be it.
I do plan to review a few other outstanding series of yours, especially the MSRs and the reboot ones.
Paolo
Sean Christopherson
maintainerQuoted 12 lines · Paolo Bonzini
Il mar 14 mar 2023, 15:29 Sean Christopherson <[email protected]> ha scritto:
Quoted 9 lines · Paolo Bonzini
Quoted 1 line
Queued, thanks.
Paolo,
Are you grabbing this for 6.3 or 6.4? If it's for 6.4, what is your plan for 6.4? I assumed we were taking the same approach as we did for 6.3, where you handle the current cycle (stabilizing 6.3) and I focus on the next cycle (building 6.4).
Quoted 5 lines
This one is for 6.4. What we did for 6.3 included me merging a handful of series that were not included in the previous merge window; so that's what I did today. If that's okay for you, once the -rc3 pull request is sent (probably tomorrow) I will push to kvm/next and that will be it.
Works for me, thanks!