KVM: SVM: Fix soft int/ex re-injection
v3 cover KVM: SVM: Fix soft int/ex re-injection
From: "Maciej S. Szmigiero" <[email protected]>
This series is an updated version of Sean's SVM soft interrupt/exception re-injection fixes patch set, which in turn extended and generalized my nSVM L1 -> L2 event injection fixes series.
Detailed list of changes in this version:
* "Downgraded" the commit affecting !nrips CPUs to just drop nested SVM support for such parts instead of SVM support in general,
* Removed the BUG_ON() from svm_inject_irq() completely, instead of replacing it with WARN() - Maxim has pointed out it can still be triggered by userspace via KVM_SET_VCPU_EVENTS,
* Updated the new KVM self-test to switch to an alternate IDT before attempting a second L1 -> L2 injection to cause intervening NPF again,
* Added a fix for L1/L2 NMI state confusion during L1 -> L2 NMI re-injection,
* Updated the new KVM self-test to also check for the NMI injection scenario being fixed (that was found causing issues with a real guest),
* Changed "kvm_inj_virq" trace event "reinjected" field type to bool,
* Integrated the fix from patch 5 for nested_vmcb02_prepare_control() call argument in svm_set_nested_state() to patch 1,
* Collected Maxim's "Reviewed-by:" for tracepoint patches.
Previous versions:
Sean's v2:
https://lore.kernel.org/kvm/[email protected]
Sean's v1:
https://lore.kernel.org/kvm/[email protected]
My original series:
https://lore.kernel.org/kvm/[email protected]
Maciej S. Szmigiero (4):
KVM: nSVM: Sync next_rip field from vmcb12 to vmcb02
KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0
KVM: nSVM: Transparently handle L1 -> L2 NMI re-injection
KVM: selftests: nSVM: Add svm_nested_soft_inject_test
Sean Christopherson (8):
KVM: SVM: Unwind "speculative" RIP advancement if INTn injection
"fails"
KVM: SVM: Stuff next_rip on emulated INT3 injection if NRIPS is
supported
KVM: SVM: Re-inject INT3/INTO instead of retrying the instruction
KVM: SVM: Re-inject INTn instead of retrying the insn on "failure"
KVM: x86: Trace re-injected exceptions
KVM: x86: Print error code in exception injection tracepoint iff valid
KVM: x86: Differentiate Soft vs. Hard IRQs vs. reinjected in
tracepoint
KVM: nSVM: Drop support for CPUs without NRIPS (NextRIP Save) support
arch/x86/include/asm/kvm_host.h | 2 +- arch/x86/kvm/svm/nested.c | 55 ++++- arch/x86/kvm/svm/svm.c | 179 +++++++++++---- arch/x86/kvm/svm/svm.h | 8 +- arch/x86/kvm/trace.h | 31 ++- arch/x86/kvm/vmx/vmx.c | 4 +- arch/x86/kvm/x86.c | 20 +- tools/testing/selftests/kvm/.gitignore | 3 +- tools/testing/selftests/kvm/Makefile | 1 + .../selftests/kvm/include/x86_64/processor.h | 17 ++ .../selftests/kvm/include/x86_64/svm_util.h | 12 + .../kvm/x86_64/svm_nested_soft_inject_test.c | 217 ++++++++++++++++++ 12 files changed, 478 insertions(+), 71 deletions(-) create mode 100644 tools/testing/selftests/kvm/x86_64/svm_nested_soft_inject_test.c
PATCH v3 1/12 KVM: nSVM: Sync next_rip field from vmcb12 to vmcb02
From: "Maciej S. Szmigiero" <[email protected]>
The next_rip field of a VMCB is *not* an output-only field for a VMRUN. This field value (instead of the saved guest RIP) in used by the CPU for the return address pushed on stack when injecting a software interrupt or INT3 or INTO exception.
Make sure this field gets synced from vmcb12 to vmcb02 when entering L2 or loading a nested state and NRIPS is exposed to L1. If NRIPS is supported in hardware but not exposed to L1 (nrips=0 or hidden by userspace), stuff vmcb02's next_rip from the new L2 RIP to emulate a !NRIPS CPU (which saves RIP on the stack as-is).
--- arch/x86/kvm/svm/nested.c | 22 +++++++++++++++++++--- arch/x86/kvm/svm/svm.h | 1 + 2 files changed, 20 insertions(+), 3 deletions(-)
arch/x86/kvm/svm/nested.c +19 -3
@@ -371,6 +371,7 @@ void __nested_copy_vmcb_control_to_cache(struct kvm_vcpu *vcpu, to->nested_ctl = from->nested_ctl; to->event_inj = from->event_inj; to->event_inj_err = from->event_inj_err; + to->next_rip = from->next_rip; to->nested_cr3 = from->nested_cr3; to->virt_ext = from->virt_ext; to->pause_filter_count = from->pause_filter_count;
@@ -608,7 +609,8 @@ static void nested_vmcb02_prepare_save(struct vcpu_svm *svm, struct vmcb *vmcb12 } } -static void nested_vmcb02_prepare_control (struct vcpu_svm *svm) +static void nested_vmcb02_prepare_control (struct vcpu_svm *svm, +unsigned long vmcb12_rip) {u32 int_ctl_vmcb01_bits =V_INTR_MASKING_MASK ;u32 int_ctl_vmcb12_bits =V_TPR_MASK |V_IRQ_INJECTION_BITS_MASK ;
@@ -662,6 +664,19 @@ static void nested_vmcb02_prepare_control(struct vcpu_svm *svm) vmcb02->control.event_inj = svm->nested.ctl.event_inj; vmcb02->control.event_inj_err = svm->nested.ctl.event_inj_err; +/* +* next_rip is consumed on VMRUN as the return address pushed on the +* stack for injected soft exceptions/interrupts. If nrips is exposed +* to L1, take it verbatim from vmcb12. If nrips is supported in +* hardware but not exposed to L1, stuff the actual L2 RIP to emulate +* what a nrips=0 CPU would do (L1 is responsible for advancing RIP +* prior to injecting the event). +*/ +if (svm->nrips_enabled) + vmcb02->control.next_rip = svm->nested.ctl.next_rip; +else if (boot_cpu_has (X86_FEATURE_NRIPS )) + vmcb02->control.next_rip = vmcb12_rip; + vmcb02->control.virt_ext = vmcb01->control.virt_ext &LBR_CTL_ENABLE_MASK ;if (svm->lbrv_enabled)
@@ -745,7 +760,7 @@ int enter_svm_guest_mode(struct kvm_vcpu *vcpu, u64 vmcb12_gpa,nested_svm_copy_common_state (svm->vmcb01.ptr, svm->nested.vmcb02.ptr);svm_switch_vmcb (svm, &svm->nested.vmcb02); -nested_vmcb02_prepare_control (svm); +nested_vmcb02_prepare_control (svm, vmcb12->save.rip);nested_vmcb02_prepare_save (svm, vmcb12); ret = nested_svm_load_cr3(&svm->vcpu, svm->nested.save.cr3,
@@ -1418,6 +1433,7 @@ static void nested_copy_vmcb_cache_to_control(struct vmcb_control_area *dst, dst->nested_ctl = from->nested_ctl; dst->event_inj = from->event_inj; dst->event_inj_err = from->event_inj_err; + dst->next_rip = from->next_rip; dst->nested_cr3 = from->nested_cr3; dst->virt_ext = from->virt_ext; dst->pause_filter_count = from->pause_filter_count;
@@ -1602,7 +1618,7 @@ static int svm_set_nested_state(struct kvm_vcpu *vcpu,nested_copy_vmcb_control_to_cache (svm, ctl);svm_switch_vmcb (svm, &svm->nested.vmcb02); -nested_vmcb02_prepare_control (svm); +nested_vmcb02_prepare_control (svm, svm->vmcb->save.rip);/* * While the nested guest CR3 is already checked and set by
arch/x86/kvm/svm/svm.h +1 -0
@@ -139,6 +139,7 @@ struct vmcb_ctrl_area_cached {u64 nested_ctl;u32 event_inj;u32 event_inj_err; +u64 next_rip;u64 nested_cr3;u64 virt_ext;u32 clean;
PATCH v3 2/12 KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0
In reply to Maciej S. SzmigieroFrom: "Maciej S. Szmigiero" <[email protected]>
Don't BUG/WARN on interrupt injection due to GIF being cleared, since it's trivial for userspace to force the situation via KVM_SET_VCPU_EVENTS (even if having at least a WARN there would be correct for KVM internally generated injections).
kernel BUG at arch/x86/kvm/svm/svm.c:3386!
invalid opcode: 0000 [#1] SMP
CPU: 15 PID: 926 Comm: smm_test Not tainted 5.17.0-rc3+ #264 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 RIP: 0010:svm_inject_irq+0xab/0xb0 [kvm_amd] Code: <0f> 0b 0f 1f 00 0f 1f 44 00 00 80 3d ac b3 01 00 00 55 48 89 f5 53 RSP: 0018:ffffc90000b37d88 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff88810a234ac0 RCX: 0000000000000006 RDX: 0000000000000000 RSI: ffffc90000b37df7 RDI: ffff88810a234ac0 RBP: ffffc90000b37df7 R08: ffff88810a1fa410 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: ffff888109571000 R14: ffff88810a234ac0 R15: 0000000000000000 FS: 0000000001821380(0000) GS:ffff88846fdc0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f74fc550008 CR3: 000000010a6fe000 CR4: 0000000000350ea0 Call Trace: <TASK> inject_pending_event+0x2f7/0x4c0 [kvm] kvm_arch_vcpu_ioctl_run+0x791/0x17a0 [kvm] kvm_vcpu_ioctl+0x26d/0x650 [kvm] __x64_sys_ioctl+0x82/0xb0 do_syscall_64+0x3b/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae </TASK>
--- arch/x86/kvm/svm/svm.c | 2 -- 1 file changed, 2 deletions(-)
arch/x86/kvm/svm/svm.c +0 -2
@@ -3384,8 +3384,6 @@ static void svm_inject_irq(struct kvm_vcpu *vcpu) {struct vcpu_svm *svm =to_svm (vcpu); -BUG_ON (!(gif_set (svm))); -trace_kvm_inj_virq (vcpu->arch.interrupt.nr); ++vcpu->stat.irq_injections;
PATCH v3 3/12 KVM: SVM: Unwind "speculative" RIP advancement if INTn injection "fails"
In reply to Maciej S. SzmigieroFrom: Sean Christopherson <[email protected]>
Unwind the RIP advancement done by svm_queue_exception() when injecting an INT3 ultimately "fails" due to the CPU encountering a VM-Exit while vectoring the injected event, even if the exception reported by the CPU isn't the same event that was injected. If vectoring INT3 encounters an exception, e.g. #NP, and vectoring the #NP encounters an intercepted exception, e.g. #PF when KVM is using shadow paging, then the #NP will be reported as the event that was in-progress.
Note, this is still imperfect, as it will get a false positive if the INT3 is cleanly injected, no VM-Exit occurs before the IRET from the INT3 handler in the guest, the instruction following the INT3 generates an exception (directly or indirectly), _and_ vectoring that exception encounters an exception that is intercepted by KVM. The false positives could theoretically be solved by further analyzing the vectoring event, e.g. by comparing the error code against the expected error code were an exception to occur when vectoring the original injected exception, but SVM without NRIPS is a complete disaster, trying to make it 100% correct is a waste of time.
--- arch/x86/kvm/svm/svm.c | 23 +++++++++++++++-------- 1 file changed, 15 insertions(+), 8 deletions(-)
arch/x86/kvm/svm/svm.c +15 -8
@@ -3698,6 +3698,18 @@ static void svm_complete_interrupts(struct kvm_vcpu *vcpu) vector = exitintinfo &SVM_EXITINTINFO_VEC_MASK ; type = exitintinfo &SVM_EXITINTINFO_TYPE_MASK ; +/* +* If NextRIP isn't enabled, KVM must manually advance RIP prior to +* injecting the soft exception/interrupt. That advancement needs to +* be unwound if vectoring didn't complete. Note, the _new_ event may +* not be the injected event, e.g. if KVM injected an INTn, the INTn +* hit a #NP in the guest, and the #NP encountered a #PF, the #NP will +* be the reported vectored event, but RIP still needs to be unwound. +*/ +if (int3_injected && type ==SVM_EXITINTINFO_TYPE_EXEPT && +kvm_is_linear_rip (vcpu, svm->int3_rip)) +kvm_rip_write (vcpu,kvm_rip_read (vcpu) - int3_injected); +switch (type) {case SVM_EXITINTINFO_TYPE_NMI : vcpu->arch.nmi_injected = true;
@@ -3711,16 +3723,11 @@ static void svm_complete_interrupts(struct kvm_vcpu *vcpu)/* * In case of software exceptions, do not reinject the vector, -* but re-execute the instruction instead. Rewind RIP first -* if we emulated INT3 before. +* but re-execute the instruction instead. */ -if (kvm_exception_is_soft (vector)) { -if (vector ==BP_VECTOR && int3_injected && -kvm_is_linear_rip (vcpu, svm->int3_rip)) -kvm_rip_write (vcpu, -kvm_rip_read (vcpu) - int3_injected); +if (kvm_exception_is_soft (vector))break ; - } +if (exitintinfo &SVM_EXITINTINFO_VALID_ERR ) {u32 err = svm->vmcb->control.exit_int_info_err;kvm_requeue_exception_e (vcpu, vector, err);
PATCH v3 4/12 KVM: SVM: Stuff next_rip on emulated INT3 injection if NRIPS is supported
In reply to Maciej S. SzmigieroFrom: Sean Christopherson <[email protected]>
If NRIPS is supported in hardware but disabled in KVM, set next_rip to the next RIP when advancing RIP as part of emulating INT3 injection. There is no flag to tell the CPU that KVM isn't using next_rip, and so leaving next_rip is left as is will result in the CPU pushing garbage onto the stack when vectoring the injected event.
--- arch/x86/kvm/svm/svm.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
arch/x86/kvm/svm/svm.c +5 -1
@@ -392,6 +392,10 @@ static void svm_queue_exception(struct kvm_vcpu *vcpu)*/ (void )svm_skip_emulated_instruction (vcpu); rip =kvm_rip_read (vcpu); + +if (boot_cpu_has (X86_FEATURE_NRIPS )) + svm->vmcb->control.next_rip = rip; + svm->int3_rip = rip + svm->vmcb->save.cs.base; svm->int3_injected = rip - old_rip; }
@@ -3701,7 +3705,7 @@ static void svm_complete_interrupts(struct kvm_vcpu *vcpu)/* * If NextRIP isn't enabled, KVM must manually advance RIP prior to * injecting the soft exception/interrupt. That advancement needs to -* be unwound if vectoring didn't complete. Note, the _new_ event may +* be unwound if vectoring didn't complete. Note, the new event may * not be the injected event, e.g. if KVM injected an INTn, the INTn * hit a #NP in the guest, and the #NP encountered a #PF, the #NP will * be the reported vectored event, but RIP still needs to be unwound.
PATCH v3 5/12 KVM: SVM: Re-inject INT3/INTO instead of retrying the instruction
In reply to Maciej S. SzmigieroFrom: Sean Christopherson <[email protected]>
Re-inject INT3/INTO instead of retrying the instruction if the CPU encountered an intercepted exception while vectoring the software exception, e.g. if vectoring INT3 encounters a #PF and KVM is using shadow paging. Retrying the instruction is architecturally wrong, e.g. will result in a spurious #DB if there's a code breakpoint on the INT3/O, and lack of re-injection also breaks nested virtualization, e.g. if L1 injects a software exception and vectoring the injected exception encounters an exception that is intercepted by L0 but not L1.
Due to, ahem, deficiencies in the SVM architecture, acquiring the next RIP may require flowing through the emulator even if NRIPS is supported, as the CPU clears next_rip if the VM-Exit is due to an exception other than "exceptions caused by the INT3, INTO, and BOUND instructions". To deal with this, "skip" the instruction to calculate next_rip (if it's not already known), and then unwind the RIP write and any side effects (RFLAGS updates).
Save the computed next_rip and use it to re-stuff next_rip if injection doesn't complete. This allows KVM to do the right thing if next_rip was known prior to injection, e.g. if L1 injects a soft event into L2, and there is no backing INTn instruction, e.g. if L1 is injecting an arbitrary event.
Note, it's impossible to guarantee architectural correctness given SVM's architectural flaws. E.g. if the guest executes INTn (no KVM injection), an exit occurs while vectoring the INTn, and the guest modifies the code stream while the exit is being handled, KVM will compute the incorrect next_rip due to "skipping" the wrong instruction. A future enhancement to make this less awful would be for KVM to detect that the decoded instruction is not the correct INTn and drop the to-be-injected soft event (retrying is a lesser evil compared to shoving the wrong RIP on the exception stack).
--- arch/x86/kvm/svm/nested.c | 26 +++++++ arch/x86/kvm/svm/svm.c | 140 +++++++++++++++++++++++++++----------- arch/x86/kvm/svm/svm.h | 6 +- 3 files changed, 129 insertions(+), 43 deletions(-)
arch/x86/kvm/svm/nested.c +26 -0
@@ -609,6 +609,21 @@ static void nested_vmcb02_prepare_save(struct vcpu_svm *svm, struct vmcb *vmcb12 } } +static inline bool is_evtinj_soft (u32 evtinj) +{ +u32 type = evtinj &SVM_EVTINJ_TYPE_MASK ; +u8 vector = evtinj &SVM_EVTINJ_VEC_MASK ; + +if (!(evtinj &SVM_EVTINJ_VALID )) +return false; + +/* +* Intentionally return false for SOFT events, SVM doesn't yet support +* re-injecting soft interrupts. +*/ +return type ==SVM_EVTINJ_TYPE_EXEPT &&kvm_exception_is_soft (vector); +} +static void nested_vmcb02_prepare_control (struct vcpu_svm *svm,unsigned long vmcb12_rip) {
@@ -677,6 +692,16 @@ static void nested_vmcb02_prepare_control(struct vcpu_svm *svm,else if (boot_cpu_has (X86_FEATURE_NRIPS )) vmcb02->control.next_rip = vmcb12_rip; +if (is_evtinj_soft (vmcb02->control.event_inj)) { + svm->soft_int_injected = true; + svm->soft_int_csbase = svm->vmcb->save.cs.base; + svm->soft_int_old_rip = vmcb12_rip; +if (svm->nrips_enabled) + svm->soft_int_next_rip = svm->nested.ctl.next_rip; +else + svm->soft_int_next_rip = vmcb12_rip; + } + vmcb02->control.virt_ext = vmcb01->control.virt_ext &LBR_CTL_ENABLE_MASK ;if (svm->lbrv_enabled)
@@ -849,6 +874,7 @@ int nested_svm_vmrun(struct kvm_vcpu *vcpu) out_exit_err: svm->nested.nested_run_pending =0 ; + svm->soft_int_injected = false; svm->vmcb->control.exit_code =SVM_EXIT_ERR ; svm->vmcb->control.exit_code_hi =0 ;
arch/x86/kvm/svm/svm.c +99 -41
196 lines not on this page · raw message
arch/x86/kvm/svm/svm.h +4 -2
@@ -230,8 +230,10 @@ struct vcpu_svm {bool nmi_singlestep;u64 nmi_singlestep_guest_rflags; -unsigned int3_injected; -unsigned long int3_rip; +unsigned long soft_int_csbase; +unsigned long soft_int_old_rip; +unsigned long soft_int_next_rip; +bool soft_int_injected;/* optional nested SVM features that are enabled for this guest */ bool nrips_enabled : 1;
PATCH v3 6/12 KVM: SVM: Re-inject INTn instead of retrying the insn on "failure"
In reply to Maciej S. SzmigieroFrom: Sean Christopherson <[email protected]>
Re-inject INTn software interrupts instead of retrying the instruction if the CPU encountered an intercepted exception while vectoring the INTn, e.g. if KVM intercepted a #PF when utilizing shadow paging. Retrying the instruction is architecturally wrong e.g. will result in a spurious #DB if there's a code breakpoint on the INT3/O, and lack of re-injection also breaks nested virtualization, e.g. if L1 injects a software interrupt and vectoring the injected interrupt encounters an exception that is intercepted by L0 but not L1.
--- arch/x86/kvm/svm/nested.c | 7 +++---- arch/x86/kvm/svm/svm.c | 23 +++++++++++++++++++---- 2 files changed, 22 insertions(+), 8 deletions(-)
arch/x86/kvm/svm/nested.c +3 -4
@@ -617,10 +617,9 @@ static inline bool is_evtinj_soft(u32 evtinj)if (!(evtinj &SVM_EVTINJ_VALID ))return false; -/* -* Intentionally return false for SOFT events, SVM doesn't yet support -* re-injecting soft interrupts. -*/ +if (type ==SVM_EVTINJ_TYPE_SOFT ) +return true; +return type ==SVM_EVTINJ_TYPE_EXEPT &&kvm_exception_is_soft (vector); }
arch/x86/kvm/svm/svm.c +19 -4
@@ -3430,12 +3430,22 @@ static void svm_inject_nmi(struct kvm_vcpu *vcpu)static void svm_inject_irq (struct kvm_vcpu *vcpu) {struct vcpu_svm *svm =to_svm (vcpu); +u32 type; + +if (vcpu->arch.interrupt.soft) { +if (svm_update_soft_interrupt_rip (vcpu)) +return ; + + type =SVM_EVTINJ_TYPE_SOFT ; + }else { + type =SVM_EVTINJ_TYPE_INTR ; + }trace_kvm_inj_virq (vcpu->arch.interrupt.nr); ++vcpu->stat.irq_injections; svm->vmcb->control.event_inj = vcpu->arch.interrupt.nr | -SVM_EVTINJ_VALID |SVM_EVTINJ_TYPE_INTR ; +SVM_EVTINJ_VALID | type; } void svm_complete_interrupt_delivery(struct kvm_vcpu *vcpu, int delivery_mode,
@@ -3715,6 +3725,8 @@ static inline void sync_lapic_to_cr8(struct kvm_vcpu *vcpu)static void svm_complete_soft_interrupt (struct kvm_vcpu *vcpu,u8 vector,int type) { +bool is_exception = (type ==SVM_EXITINTINFO_TYPE_EXEPT ); +bool is_soft = (type ==SVM_EXITINTINFO_TYPE_SOFT );struct vcpu_svm *svm =to_svm (vcpu);/*
@@ -3726,8 +3738,7 @@ static void svm_complete_soft_interrupt(struct kvm_vcpu *vcpu, u8 vector,* the same event, i.e. if the event is a soft exception/interrupt, * otherwise next_rip is unused on VMRUN. */ -if (nrips && type ==SVM_EXITINTINFO_TYPE_EXEPT && -kvm_exception_is_soft (vector) && +if (nrips && (is_soft || (is_exception &&kvm_exception_is_soft (vector))) &&kvm_is_linear_rip (vcpu, svm->soft_int_old_rip + svm->soft_int_csbase)) svm->vmcb->control.next_rip = svm->soft_int_next_rip;/*
@@ -3738,7 +3749,7 @@ static void svm_complete_soft_interrupt(struct kvm_vcpu *vcpu, u8 vector,* hit a #NP in the guest, and the #NP encountered a #PF, the #NP will * be the reported vectored event, but RIP still needs to be unwound. */ - else if (!nrips && type == SVM_EXITINTINFO_TYPE_EXEPT && + else if (!nrips && (is_soft || is_exception) && kvm_is_linear_rip(vcpu, svm->soft_int_next_rip + svm->soft_int_csbase))kvm_rip_write (vcpu, svm->soft_int_old_rip); }
@@ -3800,9 +3811,13 @@ static void svm_complete_interrupts(struct kvm_vcpu *vcpu)case SVM_EXITINTINFO_TYPE_INTR :kvm_queue_interrupt (vcpu, vector, false);break ; +case SVM_EXITINTINFO_TYPE_SOFT : +kvm_queue_interrupt (vcpu, vector, true); +break ;default :break ; } + }static void svm_cancel_injection (struct kvm_vcpu *vcpu)
PATCH v3 7/12 KVM: x86: Trace re-injected exceptions
In reply to Maciej S. SzmigieroFrom: Sean Christopherson <[email protected]>
Trace exceptions that are re-injected, not just those that KVM is injecting for the first time. Debugging re-injection bugs is painful enough as is, not having visibility into what KVM is doing only makes things worse.
Delay propagating pending=>injected in the non-reinjection path so that the tracing can properly identify reinjected exceptions.
--- arch/x86/kvm/trace.h | 12 ++++++++---- arch/x86/kvm/x86.c | 16 +++++++++------- 2 files changed, 17 insertions(+), 11 deletions(-)
arch/x86/kvm/trace.h +8 -4
@@ -358,25 +358,29 @@ TRACE_EVENT(kvm_inj_virq,* Tracepoint for kvm interrupt injection: */ TRACE_EVENT (kvm_inj_exception, - TP_PROTO(unsigned exception, bool has_error, unsigned error_code), -TP_ARGS (exception, has_error, error_code), + TP_PROTO(unsigned exception, bool has_error, unsigned error_code, + bool reinjected), +TP_ARGS (exception, has_error, error_code, reinjected),TP_STRUCT__entry ( __field( u8, exception ) __field( u8, has_error ) __field( u32, error_code ) +__field ( bool, reinjected ) ),TP_fast_assign ( __entry->exception = exception; __entry->has_error = has_error; __entry->error_code = error_code; + __entry->reinjected = reinjected; ), -TP_printk ("%s (0x%x)" , +TP_printk ("%s (0x%x)%s" ,__print_symbolic (__entry->exception, kvm_trace_sym_exc),/* FIXME: don't print error_code if not present */ - __entry->has_error ? __entry->error_code :0 ) + __entry->has_error ? __entry->error_code :0 , + __entry->reinjected ?" [reinjected]" :"" ) );/*
arch/x86/kvm/x86.c +9 -7
@@ -9393,6 +9393,11 @@ int kvm_check_nested_events(struct kvm_vcpu *vcpu)static void kvm_inject_exception (struct kvm_vcpu *vcpu) { +trace_kvm_inj_exception (vcpu->arch.exception.nr, + vcpu->arch.exception.has_error_code, + vcpu->arch.exception.error_code, + vcpu->arch.exception.injected); +if (vcpu->arch.exception.error_code && !is_protmode (vcpu)) vcpu->arch.exception.error_code = false;static_call (kvm_x86_queue_exception)(vcpu);
@@ -9450,13 +9455,6 @@ static int inject_pending_event(struct kvm_vcpu *vcpu, bool *req_immediate_exit)/* try to inject new event if pending */ if (vcpu->arch.exception.pending) { -trace_kvm_inj_exception (vcpu->arch.exception.nr, - vcpu->arch.exception.has_error_code, - vcpu->arch.exception.error_code); - - vcpu->arch.exception.pending = false; - vcpu->arch.exception.injected = true; -if (exception_type (vcpu->arch.exception.nr) ==EXCPT_FAULT )__kvm_set_rflags (vcpu,kvm_get_rflags (vcpu) |X86_EFLAGS_RF );
@@ -9470,6 +9468,10 @@ static int inject_pending_event(struct kvm_vcpu *vcpu, bool *req_immediate_exit) }kvm_inject_exception (vcpu); + + vcpu->arch.exception.pending = false; + vcpu->arch.exception.injected = true; + can_inject = false; }
PATCH v3 8/12 KVM: x86: Print error code in exception injection tracepoint iff valid
In reply to Maciej S. SzmigieroFrom: Sean Christopherson <[email protected]>
Print the error code in the exception injection tracepoint if and only if the exception has an error code. Define the entire error code sequence as a set of formatted strings, print empty strings if there's no error code, and abuse __print_symbolic() by passing it an empty array to coerce it into printing the error code as a hex string.
--- arch/x86/kvm/trace.h | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
arch/x86/kvm/trace.h +4 -3
@@ -376,10 +376,11 @@ TRACE_EVENT(kvm_inj_exception, __entry->reinjected = reinjected; ), -TP_printk ("%s (0x%x)%s" , +TP_printk ("%s%s%s%s%s" ,__print_symbolic (__entry->exception, kvm_trace_sym_exc), -/* FIXME: don't print error_code if not present */ - __entry->has_error ? __entry->error_code :0 , + !__entry->has_error ?"" :" (" , + !__entry->has_error ?"" :__print_symbolic (__entry->error_code, { }), + !__entry->has_error ?"" :")" , __entry->reinjected ?" [reinjected]" :"" ) );
PATCH v3 9/12 KVM: x86: Differentiate Soft vs. Hard IRQs vs. reinjected in tracepoint
In reply to Maciej S. SzmigieroFrom: Sean Christopherson <[email protected]>
In the IRQ injection tracepoint, differentiate between Hard IRQs and Soft "IRQs", i.e. interrupts that are reinjected after incomplete delivery of a software interrupt from an INTn instruction. Tag reinjected interrupts as such, even though the information is usually redundant since soft interrupts are only ever reinjected by KVM. Though rare in practice, a hard IRQ can be reinjected.
--- arch/x86/include/asm/kvm_host.h | 2 +- arch/x86/kvm/svm/svm.c | 5 +++-- arch/x86/kvm/trace.h | 16 +++++++++++----- arch/x86/kvm/vmx/vmx.c | 4 ++-- arch/x86/kvm/x86.c | 4 ++-- 5 files changed, 19 insertions(+), 12 deletions(-)
arch/x86/include/asm/kvm_host.h +1 -1
@@ -1400,7 +1400,7 @@ struct kvm_x86_ops {u32 (*get_interrupt_shadow)(struct kvm_vcpu *vcpu);void (*patch_hypercall)(struct kvm_vcpu *vcpu,unsigned char *hypercall_addr); -void (*inject_irq)(struct kvm_vcpu *vcpu); +void (*inject_irq)(struct kvm_vcpu *vcpu,bool reinjected);void (*inject_nmi)(struct kvm_vcpu *vcpu);void (*queue_exception)(struct kvm_vcpu *vcpu);void (*cancel_injection)(struct kvm_vcpu *vcpu);
arch/x86/kvm/svm/svm.c +3 -2
@@ -3427,7 +3427,7 @@ static void svm_inject_nmi(struct kvm_vcpu *vcpu) ++vcpu->stat.nmi_injections; } -static void svm_inject_irq (struct kvm_vcpu *vcpu) +static void svm_inject_irq (struct kvm_vcpu *vcpu,bool reinjected) {struct vcpu_svm *svm =to_svm (vcpu);u32 type;
@@ -3441,7 +3441,8 @@ static void svm_inject_irq(struct kvm_vcpu *vcpu) type =SVM_EVTINJ_TYPE_INTR ; } -trace_kvm_inj_virq (vcpu->arch.interrupt.nr); +trace_kvm_inj_virq (vcpu->arch.interrupt.nr, + vcpu->arch.interrupt.soft, reinjected); ++vcpu->stat.irq_injections; svm->vmcb->control.event_inj = vcpu->arch.interrupt.nr |
arch/x86/kvm/trace.h +11 -5
@@ -333,18 +333,24 @@ TRACE_EVENT_KVM_EXIT(kvm_exit);* Tracepoint for kvm interrupt injection: */ TRACE_EVENT (kvm_inj_virq, - TP_PROTO(unsigned int irq), -TP_ARGS (irq), + TP_PROTO(unsigned int vector, bool soft, bool reinjected), +TP_ARGS (vector, soft, reinjected),TP_STRUCT__entry ( - __field( unsigned int, irq ) + __field( unsigned int, vector ) + __field( bool, soft ) +__field ( bool, reinjected ) ),TP_fast_assign ( - __entry->irq = irq; + __entry->vector = vector; + __entry->soft = soft; + __entry->reinjected = reinjected; ), -TP_printk ("irq %u" , __entry->irq) +TP_printk ("%s 0x%x%s" , + __entry->soft ?"Soft/INTn" :"IRQ" , __entry->vector, + __entry->reinjected ?" [reinjected]" :"" ) );#define EXS (x) { x##_VECTOR, "#" #x }
arch/x86/kvm/vmx/vmx.c +2 -2
@@ -4566,13 +4566,13 @@ static void vmx_enable_nmi_window(struct kvm_vcpu *vcpu)exec_controls_setbit (to_vmx (vcpu),CPU_BASED_NMI_WINDOW_EXITING ); } -static void vmx_inject_irq (struct kvm_vcpu *vcpu) +static void vmx_inject_irq (struct kvm_vcpu *vcpu,bool reinjected) {struct vcpu_vmx *vmx =to_vmx (vcpu);uint32_t intr;int irq = vcpu->arch.interrupt.nr; -trace_kvm_inj_virq (irq); +trace_kvm_inj_virq (irq, vcpu->arch.interrupt.soft, reinjected); ++vcpu->stat.irq_injections;if (vmx->rmode.vm86_active) {
arch/x86/kvm/x86.c +2 -2
@@ -9433,7 +9433,7 @@ static int inject_pending_event(struct kvm_vcpu *vcpu, bool *req_immediate_exit)static_call (kvm_x86_inject_nmi)(vcpu); can_inject = false; }else if (vcpu->arch.interrupt.injected) { -static_call (kvm_x86_inject_irq)(vcpu); +static_call (kvm_x86_inject_irq)(vcpu, true); can_inject = false; } }
@@ -9524,7 +9524,7 @@ static int inject_pending_event(struct kvm_vcpu *vcpu, bool *req_immediate_exit) goto out;if (r) {kvm_queue_interrupt (vcpu,kvm_cpu_get_interrupt (vcpu), false); -static_call (kvm_x86_inject_irq)(vcpu); +static_call (kvm_x86_inject_irq)(vcpu, false);WARN_ON (static_call (kvm_x86_interrupt_allowed)(vcpu, true) <0 ); }if (kvm_cpu_has_injectable_intr (vcpu))
PATCH v3 10/12 KVM: nSVM: Transparently handle L1 -> L2 NMI re-injection
In reply to Maciej S. SzmigieroFrom: "Maciej S. Szmigiero" <[email protected]>
A NMI that L1 wants to inject into its L2 should be directly re-injected, without causing L0 side effects like engaging NMI blocking for L1.
It's also worth noting that in this case it is L1 responsibility to track the NMI window status for its L2 guest.
--- arch/x86/kvm/svm/nested.c | 12 ++++++++++++ arch/x86/kvm/svm/svm.c | 7 +++++++ arch/x86/kvm/svm/svm.h | 1 + 3 files changed, 20 insertions(+)
arch/x86/kvm/svm/nested.c +12 -0
@@ -623,6 +623,16 @@ static inline bool is_evtinj_soft(u32 evtinj)return type ==SVM_EVTINJ_TYPE_EXEPT &&kvm_exception_is_soft (vector); } +static bool is_evtinj_nmi (u32 evtinj) +{ +u32 type = evtinj &SVM_EVTINJ_TYPE_MASK ; + +if (!(evtinj &SVM_EVTINJ_VALID )) +return false; + +return type ==SVM_EVTINJ_TYPE_NMI ; +} +static void nested_vmcb02_prepare_control (struct vcpu_svm *svm,unsigned long vmcb12_rip) {
@@ -691,6 +701,7 @@ static void nested_vmcb02_prepare_control(struct vcpu_svm *svm,else if (boot_cpu_has (X86_FEATURE_NRIPS )) vmcb02->control.next_rip = vmcb12_rip; + svm->nmi_l1_to_l2 =is_evtinj_nmi (vmcb02->control.event_inj);if (is_evtinj_soft (vmcb02->control.event_inj)) { svm->soft_int_injected = true; svm->soft_int_csbase = svm->vmcb->save.cs.base;
@@ -873,6 +884,7 @@ int nested_svm_vmrun(struct kvm_vcpu *vcpu) out_exit_err: svm->nested.nested_run_pending =0 ; + svm->nmi_l1_to_l2 = false; svm->soft_int_injected = false; svm->vmcb->control.exit_code =SVM_EXIT_ERR ;
arch/x86/kvm/svm/svm.c +7 -0
@@ -3421,6 +3421,10 @@ static void svm_inject_nmi(struct kvm_vcpu *vcpu)struct vcpu_svm *svm =to_svm (vcpu); svm->vmcb->control.event_inj =SVM_EVTINJ_VALID |SVM_EVTINJ_TYPE_NMI ; + +if (svm->nmi_l1_to_l2) +return ; + vcpu->arch.hflags |=HF_NMI_MASK ;if (!sev_es_guest (vcpu->kvm))svm_set_intercept (svm,INTERCEPT_IRET );
@@ -3761,8 +3765,10 @@ static void svm_complete_interrupts(struct kvm_vcpu *vcpu)u8 vector;int type;u32 exitintinfo = svm->vmcb->control.exit_int_info; +bool nmi_l1_to_l2 = svm->nmi_l1_to_l2;bool soft_int_injected = svm->soft_int_injected; + svm->nmi_l1_to_l2 = false; svm->soft_int_injected = false;/*
@@ -3794,6 +3800,7 @@ static void svm_complete_interrupts(struct kvm_vcpu *vcpu)switch (type) {case SVM_EXITINTINFO_TYPE_NMI : vcpu->arch.nmi_injected = true; + svm->nmi_l1_to_l2 = nmi_l1_to_l2;break ;case SVM_EXITINTINFO_TYPE_EXEPT :/*
arch/x86/kvm/svm/svm.h +1 -0
@@ -229,6 +229,7 @@ struct vcpu_svm {bool nmi_singlestep;u64 nmi_singlestep_guest_rflags; +bool nmi_l1_to_l2;unsigned long soft_int_csbase;unsigned long soft_int_old_rip;
PATCH v3 11/12 KVM: selftests: nSVM: Add svm_nested_soft_inject_test
In reply to Maciej S. SzmigieroFrom: "Maciej S. Szmigiero" <[email protected]>
Add a KVM self-test that checks whether a nSVM L1 is able to successfully inject a software interrupt, a soft exception and a NMI into its L2 guest.
In practice, this tests both the next_rip field consistency and L1-injected event with intervening L0 VMEXIT during its delivery:
the first nested VMRUN (that's also trying to inject a software interrupt) will immediately trigger a L0 NPF.
This L0 NPF will have zero in its CPU-returned next_rip field, which if incorrectly reused by KVM will trigger a #PF when trying to return to such address 0 from the interrupt handler.
For NMI injection this tests whether the L1 NMI state isn't getting incorrectly mixed with the L2 NMI state if a L1 -> L2 NMI needs to be re-injected.
--- tools/testing/selftests/kvm/.gitignore | 3 +- tools/testing/selftests/kvm/Makefile | 1 + .../selftests/kvm/include/x86_64/processor.h | 17 ++ .../selftests/kvm/include/x86_64/svm_util.h | 12 + .../kvm/x86_64/svm_nested_soft_inject_test.c | 217 ++++++++++++++++++ 5 files changed, 249 insertions(+), 1 deletion(-) create mode 100644 tools/testing/selftests/kvm/x86_64/svm_nested_soft_inject_test.c
tools/testing/selftests/kvm/.gitignore +2 -1
@@ -35,9 +35,10 @@ /x86_64/state_test /x86_64/svm_vmcall_test /x86_64/svm_int_ctl_test -/x86_64/tsc_scaling_sync +/x86_64/svm_nested_soft_inject_test /x86_64/sync_regs_test /x86_64/tsc_msrs_test +/x86_64/tsc_scaling_sync /x86_64/userspace_io_test /x86_64/userspace_msr_exit_test /x86_64/vmx_apic_access_test
tools/testing/selftests/kvm/Makefile +1 -0
@@ -66,6 +66,7 @@ TEST_GEN_PROGS_x86_64 += x86_64/state_test TEST_GEN_PROGS_x86_64 += x86_64/vmx_preemption_timer_test TEST_GEN_PROGS_x86_64 += x86_64/svm_vmcall_test TEST_GEN_PROGS_x86_64 += x86_64/svm_int_ctl_test +TEST_GEN_PROGS_x86_64 += x86_64/svm_nested_soft_inject_test TEST_GEN_PROGS_x86_64 += x86_64/tsc_scaling_sync TEST_GEN_PROGS_x86_64 += x86_64/sync_regs_test TEST_GEN_PROGS_x86_64 += x86_64/userspace_io_test
tools/testing/selftests/kvm/include/x86_64/processor.h +17 -0
@@ -17,6 +17,8 @@#include "../kvm_util.h" +#define NMI_VECTOR 0x02 +#define X86_EFLAGS_FIXED (1u << 1)#define X86_CR4_VME (1ul << 0)
@@ -368,6 +370,21 @@ static inline void cpu_relax(void) asmvolatile ("rep; nop" :::"memory" ); } +#define vmmcall () \ + __asm__ __volatile__( \ + "vmmcall\n" \ + ) + +#define ud2 () \ + __asm__ __volatile__( \ + "ud2\n" \ + ) + +#define hlt () \ + __asm__ __volatile__( \ + "hlt\n" \ + ) +bool is_intel_cpu (void );bool is_amd_cpu (void );
tools/testing/selftests/kvm/include/x86_64/svm_util.h +12 -0
@@ -16,6 +16,8 @@#define CPUID_SVM_BIT 2#define CPUID_SVM BIT_ULL(CPUID_SVM_BIT) +#define SVM_EXIT_EXCP_BASE 0x040 +#define SVM_EXIT_HLT 0x078#define SVM_EXIT_MSR 0x07c#define SVM_EXIT_VMMCALL 0x081
@@ -36,6 +38,16 @@ struct svm_test_data {uint64_t msr_gpa; }; +#define stgi () \ + __asm__ __volatile__( \ + "stgi\n" \ + ) + +#define clgi () \ + __asm__ __volatile__( \ + "clgi\n" \ + ) +struct svm_test_data *vcpu_alloc_svm (struct kvm_vm *vm,vm_vaddr_t *p_svm_gva);void generic_svm_setup (struct svm_test_data *svm,void *guest_rip,void *guest_rsp);void run_guest (struct vmcb *vmcb,uint64_t vmcb_gpa);
tools/testing/selftests/kvm/x86_64/svm_nested_soft_inject_test.c new file +217 -0
217 lines not on this page · raw message
PATCH v3 12/12 KVM: nSVM: Drop support for CPUs without NRIPS (NextRIP Save) support
In reply to Maciej S. SzmigieroFrom: Sean Christopherson <[email protected]>
Drop nested support for CPUs without NRIPS, as requiring NRIPS simplifies a handful of paths in KVM.
NRIPS was introduced in 2009, i.e. every AMD-based CPU released in the last decade should support NRIPS.
--- arch/x86/kvm/svm/nested.c | 14 +++++--------- arch/x86/kvm/svm/svm.c | 19 +++++++++++-------- 2 files changed, 16 insertions(+), 17 deletions(-)
arch/x86/kvm/svm/nested.c +5 -9
@@ -691,14 +691,13 @@ static void nested_vmcb02_prepare_control(struct vcpu_svm *svm,/* * next_rip is consumed on VMRUN as the return address pushed on the * stack for injected soft exceptions/interrupts. If nrips is exposed -* to L1, take it verbatim from vmcb12. If nrips is supported in -* hardware but not exposed to L1, stuff the actual L2 RIP to emulate -* what a nrips=0 CPU would do (L1 is responsible for advancing RIP -* prior to injecting the event). +* to L1, take it verbatim from vmcb12. If nrips is not exposed to L1, +* stuff the actual L2 RIP to emulate what an nrips=0 CPU would do (L1 +* is responsible for advancing RIP prior to injecting the event). */ if (svm->nrips_enabled) vmcb02->control.next_rip = svm->nested.ctl.next_rip; -else if (boot_cpu_has (X86_FEATURE_NRIPS )) +else vmcb02->control.next_rip = vmcb12_rip; svm->nmi_l1_to_l2 =is_evtinj_nmi (vmcb02->control.event_inj);
@@ -706,10 +705,7 @@ static void nested_vmcb02_prepare_control(struct vcpu_svm *svm, svm->soft_int_injected = true; svm->soft_int_csbase = svm->vmcb->save.cs.base; svm->soft_int_old_rip = vmcb12_rip; -if (svm->nrips_enabled) - svm->soft_int_next_rip = svm->nested.ctl.next_rip; -else - svm->soft_int_next_rip = vmcb12_rip; + svm->soft_int_next_rip = vmcb02->control.next_rip; } vmcb02->control.virt_ext = vmcb01->control.virt_ext &
arch/x86/kvm/svm/svm.c +11 -8
@@ -4330,9 +4330,7 @@ static int svm_check_intercept(struct kvm_vcpu *vcpu,break ; } -/* TODO: Advertise NRIPS to guest hypervisor unconditionally */ -if (static_cpu_has (X86_FEATURE_NRIPS )) - vmcb->control.next_rip = info->next_rip; + vmcb->control.next_rip = info->next_rip; vmcb->control.exit_code = icpt_info.exit_code; vmexit =nested_svm_exit_handled (svm);
@@ -4961,6 +4959,16 @@ static __init int svm_hardware_setup(void) pause_filter_thresh =0 ; } +if (nrips) { +if (!boot_cpu_has (X86_FEATURE_NRIPS )) + nrips = false; + } + +if (!nrips && nested) { +pr_notice ("kvm: Nested Virtualization requires NRIPS (NextRIP Save)\n" ); + nested = false; + } +if (nested) {printk (KERN_INFO "kvm: Nested Virtualization enabled\n" );kvm_enable_efer_bits (EFER_SVME |EFER_LMSLE );
@@ -4995,11 +5003,6 @@ static __init int svm_hardware_setup(void) goto err; } -if (nrips) { -if (!boot_cpu_has (X86_FEATURE_NRIPS )) - nrips = false; - } - enable_apicv = avic = avic && npt_enabled && (boot_cpu_has (X86_FEATURE_AVIC ) || force_avic);if (enable_apicv) {
Sean Christopherson
maintainerQuoted 36 lines · Maciej S. Szmigiero
From: "Maciej S. Szmigiero" <[email protected]>
This series is an updated version of Sean's SVM soft interrupt/exception re-injection fixes patch set, which in turn extended and generalized my nSVM L1 -> L2 event injection fixes series.
Detailed list of changes in this version:
* "Downgraded" the commit affecting !nrips CPUs to just drop nested SVM support for such parts instead of SVM support in general,* Removed the
BUG_ON()fromsvm_inject_irq()completely, instead of replacing it withWARN()- Maxim has pointed out it can still be triggered by userspace viaKVM_SET_VCPU_EVENTS,* Updated the new KVM self-test to switch to an alternate IDT before attempting a second L1 -> L2 injection to cause intervening NPF again,
* Added a fix for L1/L2 NMI state confusion during L1 -> L2 NMI re-injection,
* Updated the new KVM self-test to also check for the NMI injection scenario being fixed (that was found causing issues with a real guest),
* Changed "
kvm_inj_virq" trace event "reinjected" field type to bool,* Integrated the fix from patch 5 for
nested_vmcb02_prepare_control()call argument insvm_set_nested_state()to patch 1,* Collected Maxim's "Reviewed-by:" for tracepoint patches.
Previous versions:
Sean's v2:
https://lore.kernel.org/kvm/[email protected]
Quoted 6 lines
My original series:
https://lore.kernel.org/kvm/[email protected]Maciej S. Szmigiero (4):
KVM: nSVM: Syncnext_ripfield from vmcb12 to vmcb02
KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0
LOL, this should win some kind of award for most ridiculous multi-author patch :-)
Series looks good, thanks!
Quoted 40 lines · Sean Christopherson
Quoted 39 lines · Maciej S. Szmigiero
From: "Maciej S. Szmigiero" <[email protected]>
This series is an updated version of Sean's SVM soft interrupt/exception re-injection fixes patch set, which in turn extended and generalized my nSVM L1 -> L2 event injection fixes series.
Detailed list of changes in this version:
* "Downgraded" the commit affecting !nrips CPUs to just drop nested SVM support for such parts instead of SVM support in general,* Removed the
BUG_ON()fromsvm_inject_irq()completely, instead of replacing it withWARN()- Maxim has pointed out it can still be triggered by userspace viaKVM_SET_VCPU_EVENTS,* Updated the new KVM self-test to switch to an alternate IDT before attempting a second L1 -> L2 injection to cause intervening NPF again,
* Added a fix for L1/L2 NMI state confusion during L1 -> L2 NMI re-injection,
* Updated the new KVM self-test to also check for the NMI injection scenario being fixed (that was found causing issues with a real guest),
* Changed "
kvm_inj_virq" trace event "reinjected" field type to bool,* Integrated the fix from patch 5 for
nested_vmcb02_prepare_control()call argument insvm_set_nested_state()to patch 1,* Collected Maxim's "Reviewed-by:" for tracepoint patches.
Previous versions:
Sean's v2:
https://lore.kernel.org/kvm/[email protected]Sean's v1:
https://lore.kernel.org/kvm/[email protected]My original series:
https://lore.kernel.org/kvm/[email protected]
Quoted 8 lines
Quoted 3 lines
Maciej S. Szmigiero (4):
KVM: nSVM: Syncnext_ripfield from vmcb12 to vmcb02
KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0LOL, this should win some kind of award for most ridiculous multi-author patch :-)
Series looks good, thanks!
Well I think I, Paolo, and you hold the record for this, when we fixed the AVIC inhibition races, remember?
Patch series also looks overall good to me, but I haven't checked everything to be honest.
Best regards,
Maxim Levitsky
Quoted 3 lines · Maciej S. Szmigiero
This series is an updated version of Sean's SVM soft interrupt/exception re-injection fixes patch set, which in turn extended and generalized my nSVM L1 -> L2 event injection fixes series.
@Paolo:
Can't see this series in kvm/queue, do you plan to merge it for 5.19?
Thanks,
Maciej
Paolo Bonzini
maintainerQuoted 7 lines · Maciej S. Szmigiero
Quoted 3 lines · Maciej S. Szmigiero
This series is an updated version of Sean's SVM soft interrupt/exception re-injection fixes patch set, which in turn extended and generalized my nSVM L1 -> L2 event injection fixes series.
@Paolo:
Can't see this series in kvm/queue, do you plan to merge it for 5.19?
Yes, FWIW my list right now is (from most likely to less likely but still doable):
* deadlock (5.18)
* PMU filter patches from alewis (5.18?)
* architectural LBR
* Like's perf HW_EVENT series
* cache refresh
* this one
* nested dirty-log selftest
* x2AVIC
* dirty quota
* CMCI
* pfn functions
* Vitaly's Hyper-V TLB
Quoted 27 lines · Paolo Bonzini
Quoted 7 lines · Maciej S. Szmigiero
Quoted 3 lines · Maciej S. Szmigiero
This series is an updated version of Sean's SVM soft interrupt/exception re-injection fixes patch set, which in turn extended and generalized my nSVM L1 -> L2 event injection fixes series.
@Paolo:
Can't see this series in kvm/queue, do you plan to merge it for 5.19?Yes, FWIW my list right now is (from most likely to less likely but still doable):
* deadlock (5.18)
* PMU filter patches from alewis (5.18?)
* architectural LBR
* Like's perf
HW_EVENTseries* cache refresh
* this one
* nested dirty-log selftest
* x2AVIC
Quoted 8 lines
* dirty quota
* CMCI
* pfn functions
* Vitaly's Hyper-V TLB
Ugh, that's a long TODO list...
Thanks for the update - waiting patiently then.
Thanks,
Maciej