[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <169645804510.2820791.2556170665167933788.b4-ty@google.com>
Date: Wed, 4 Oct 2023 18:29:33 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Sean Christopherson <seanjc@...gle.com>,
Paolo Bonzini <pbonzini@...hat.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
Wu Zongyo <wuzongyo@...l.ustc.edu.cn>,
Tom Lendacky <thomas.lendacky@....com>
Subject: Re: [PATCH v2 0/4] KVM: SVM: Fix unexpected #UD on INT3 in SEV guests
On Thu, 24 Aug 2023 18:36:17 -0700, Sean Christopherson wrote:
> Fix a bug where KVM injects a bogus #UD for SEV guests when trying to skip
> an INT3 as part of re-injecting the associated #BP that got kinda sorta
> intercepted due to a #NPF occuring while vectoring/delivering the #BP.
>
> Patch 1 is the main fix. It's a little ugly, but suitable for backporting.
>
> Patch 2 is a tangentially related cleanup to make NRIPS a requirement for
> enabling SEV, e.g. so that we don't ever get "bug" reports of SEV guests
> not working when NRIPS is disabled.
>
> [...]
Applied 3-4 to kvm-x86 svm (1-2 went into v6.6).
[3/4] KVM: x86: Refactor can_emulate_instruction() return to be more expressive
https://github.com/kvm-x86/linux/commit/aeb904f6b9f1
[4/4] KVM: SVM: Treat all "skip" emulation for SEV guests as outright failures
https://github.com/kvm-x86/linux/commit/006829954096
--
https://github.com/kvm-x86/linux/tree/next
Powered by blists - more mailing lists