From: Paolo Bonzini <pbonzini@redhat.com>
To: Maxim Levitsky <mlevitsk@redhat.com>, kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Jim Mattson <jmattson@google.com>,
Wanpeng Li <wanpengli@tencent.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Sean Christopherson <seanjc@google.com>,
Borislav Petkov <bp@alien8.de>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, Joerg Roedel <joro@8bytes.org>
Subject: Re: [PATCH v3 0/7] KVM: few more SMM fixes
Date: Wed, 22 Sep 2021 16:35:56 +0200 [thread overview]
Message-ID: <22916f0c-2e3a-1fd6-905e-5d647c15c45b@redhat.com> (raw)
In-Reply-To: <20210913140954.165665-1-mlevitsk@redhat.com>
On 13/09/21 16:09, Maxim Levitsky wrote:
> These are few SMM fixes I was working on last week.
>
> * Patch 1,2 fixes a minor issue that remained after
> commit 37be407b2ce8 ("KVM: nSVM: Fix L1 state corruption upon return from SMM")
>
> While now, returns to guest mode from SMM work due to restored state from HSAVE
> area, the guest entry still sees incorrect HSAVE state.
>
> This for example breaks return from SMM when the guest is 32 bit, due to PDPTRs
> loading which are done using incorrect MMU state which is incorrect,
> because it was setup with incorrect L1 HSAVE state.
>
> V3: updated with review feedback from Sean.
>
> * Patch 3 fixes a theoretical issue that I introduced with my SREGS2 patchset,
> which Sean Christopherson pointed out.
>
> The issue is that KVM_REQ_GET_NESTED_STATE_PAGES request is not only used
> for completing the load of the nested state, but it is also used to complete
> exit from SMM to guest mode, and my compatibility hack of pdptrs_from_userspace
> was done assuming that this is not done.
>
> V3: I moved the reset of pdptrs_from_userspace to common x86 code.
>
> * Patch 4 makes SVM SMM exit to be a bit more similar to how VMX does it
> by also raising KVM_REQ_GET_NESTED_STATE_PAGES requests.
>
> I do have doubts about why we need to do this on VMX though. The initial
> justification for this comes from
>
> 7f7f1ba33cf2 ("KVM: x86: do not load vmcs12 pages while still in SMM")
>
> With all the MMU changes, I am not sure that we can still have a case
> of not up to date MMU when we enter the nested guest from SMM.
> On SVM it does seem to work anyway without this.
>
> * Patch 5 fixes guest emulation failure when unrestricted_guest=0 and we reach
> handle_exception_nmi_irqoff.
> That function takes stale values from current vmcs and fails not taking into account
> the fact that we are emulating invalid guest state now, and thus no VM exit happened.
>
> * Patch 6 fixed a corner case where return from SMM is slightly corrupting
> the L2 segment register state when unrestricted_guest=0 due to real mode segement
> caching register logic, but later it restores it correctly from SMMRAM.
> Fix this by not failing nested_vmx_enter_non_root_mode and delaying this
> failure to the next nested VM entry.
>
> * Patch 7 fixes another corner case where emulation_required was not updated
> correctly on nested VMexit when restoring the L1 segement registers.
>
> I still track 2 SMM issues:
>
> 1. When HyperV guest is running nested, and uses SMM enabled OVMF, it crashes and
> reboots during the boot process.
>
> 2. Nested migration on VMX is still broken when L1 floods itself with SMIs.
>
> Best regards,
> Maxim Levitsky
>
> Maxim Levitsky (7):
> KVM: x86: nSVM: refactor svm_leave_smm and smm_enter_smm
> KVM: x86: nSVM: restore the L1 host state prior to resuming nested
> guest on SMM exit
> KVM: x86: reset pdptrs_from_userspace when exiting smm
> KVM: x86: SVM: call KVM_REQ_GET_NESTED_STATE_PAGES on exit from SMM
> mode
> KVM: x86: VMX: synthesize invalid VM exit when emulating invalid guest
> state
> KVM: x86: nVMX: don't fail nested VM entry on invalid guest state if
> !from_vmentry
> KVM: x86: nVMX: re-evaluate emulation_required on nested VM exit
>
> arch/x86/kvm/svm/nested.c | 9 ++-
> arch/x86/kvm/svm/svm.c | 131 ++++++++++++++++++++------------------
> arch/x86/kvm/svm/svm.h | 3 +-
> arch/x86/kvm/vmx/nested.c | 9 ++-
> arch/x86/kvm/vmx/vmx.c | 28 ++++++--
> arch/x86/kvm/vmx/vmx.h | 1 +
> arch/x86/kvm/x86.c | 7 ++
> 7 files changed, 113 insertions(+), 75 deletions(-)
>
Queued, thanks. However, I'm keeping patch 1 for 5.16 only.
Paolo
next prev parent reply other threads:[~2021-09-22 14:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 14:09 [PATCH v3 0/7] KVM: few more SMM fixes Maxim Levitsky
2021-09-13 14:09 ` [PATCH v3 1/7] KVM: x86: nSVM: refactor svm_leave_smm and smm_enter_smm Maxim Levitsky
2021-09-13 14:09 ` [PATCH v3 2/7] KVM: x86: nSVM: restore the L1 host state prior to resuming nested guest on SMM exit Maxim Levitsky
2021-09-13 14:09 ` [PATCH v3 3/7] KVM: x86: reset pdptrs_from_userspace when exiting smm Maxim Levitsky
2021-09-13 14:09 ` [PATCH v3 4/7] KVM: x86: SVM: call KVM_REQ_GET_NESTED_STATE_PAGES on exit from SMM mode Maxim Levitsky
2021-09-13 14:09 ` [PATCH v3 5/7] KVM: x86: VMX: synthesize invalid VM exit when emulating invalid guest state Maxim Levitsky
2021-09-13 14:09 ` [PATCH v3 6/7] KVM: x86: nVMX: don't fail nested VM entry on invalid guest state if !from_vmentry Maxim Levitsky
2021-09-13 14:09 ` [PATCH v3 7/7] KVM: x86: nVMX: re-evaluate emulation_required on nested VM exit Maxim Levitsky
2021-09-22 14:35 ` Paolo Bonzini [this message]
2021-09-22 14:46 ` [PATCH v3 0/7] KVM: few more SMM fixes Sean Christopherson
2021-09-22 15:45 ` Paolo Bonzini
2021-09-22 15:52 ` Sean Christopherson
2021-09-22 18:17 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22916f0c-2e3a-1fd6-905e-5d647c15c45b@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).