Messages in this thread | | | Date | Mon, 7 Feb 2022 17:44:43 +0100 | Subject | Re: [PATCH 01/11] Revert "svm: Add warning message for AVIC IPI invalid target" | From | Paolo Bonzini <> |
| |
On 2/4/22 22:41, Sean Christopherson wrote: > Remove a WARN on an "AVIC IPI invalid target" exit, the WARN is trivial > to trigger from guest as it will fail on any destination APIC ID that > doesn't exist from the guest's perspective. > > Don't bother recording anything in the kernel log, the common tracepoint > for kvm_avic_incomplete_ipi() is sufficient for debugging. > > This reverts commit 37ef0c4414c9743ba7f1af4392f0a27a99649f2a. > > Cc: stable@vger.kernel.org > Signed-off-by: Sean Christopherson <seanjc@google.com> > --- > arch/x86/kvm/svm/avic.c | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/arch/x86/kvm/svm/avic.c b/arch/x86/kvm/svm/avic.c > index 90364d02f22a..ecc81c48c0ca 100644 > --- a/arch/x86/kvm/svm/avic.c > +++ b/arch/x86/kvm/svm/avic.c > @@ -345,8 +345,6 @@ int avic_incomplete_ipi_interception(struct kvm_vcpu *vcpu) > avic_kick_target_vcpus(vcpu->kvm, apic, icrl, icrh); > break; > case AVIC_IPI_FAILURE_INVALID_TARGET: > - WARN_ONCE(1, "Invalid IPI target: index=%u, vcpu=%d, icr=%#0x:%#0x\n", > - index, vcpu->vcpu_id, icrh, icrl); > break; > case AVIC_IPI_FAILURE_INVALID_BACKING_PAGE: > WARN_ONCE(1, "Invalid backing page\n");
Queued for 5.17, thanks.
Paolo
| |