From: Maxim Levitsky <mlevitsk@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, Jim Mattson <jmattson@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Joerg Roedel <joro@8bytes.org>, "H. Peter Anvin" <hpa@zytor.com>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jonathan Corbet <corbet@lwn.net>, Borislav Petkov <bp@alien8.de>,
Ingo Molnar <mingo@redhat.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH 5/6] KVM: nSVM: avoid loading PDPTRs after migration when possible
Date: Tue, 06 Apr 2021 13:12:13 +0300 [thread overview]
Message-ID: <8ffa121b8be00cd30c93830c476a448cee895abc.camel@redhat.com> (raw)
In-Reply-To: <YGtCeiyzUrRbbNKG@google.com>
On Mon, 2021-04-05 at 17:01 +0000, Sean Christopherson wrote:
> On Thu, Apr 01, 2021, Maxim Levitsky wrote:
> > if new KVM_*_SREGS2 ioctls are used, the PDPTRs are
> > part of the migration state and thus are loaded
> > by those ioctls.
> >
> > Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
> > ---
> > arch/x86/kvm/svm/nested.c | 15 +++++++++++++--
> > 1 file changed, 13 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/x86/kvm/svm/nested.c b/arch/x86/kvm/svm/nested.c
> > index ac5e3e17bda4..b94916548cfa 100644
> > --- a/arch/x86/kvm/svm/nested.c
> > +++ b/arch/x86/kvm/svm/nested.c
> > @@ -373,10 +373,9 @@ static int nested_svm_load_cr3(struct kvm_vcpu *vcpu, unsigned long cr3,
> > return -EINVAL;
> >
> > if (!nested_npt && is_pae_paging(vcpu) &&
> > - (cr3 != kvm_read_cr3(vcpu) || pdptrs_changed(vcpu))) {
> > + (cr3 != kvm_read_cr3(vcpu) || !kvm_register_is_available(vcpu, VCPU_EXREG_PDPTR)))
> > if (CC(!load_pdptrs(vcpu, vcpu->arch.walk_mmu, cr3)))
>
> What if we ditch the optimizations[*] altogether and just do:
>
> if (!nested_npt && is_pae_paging(vcpu) &&
> CC(!load_pdptrs(vcpu, vcpu->arch.walk_mmu, cr3))
> return -EINVAL;
>
> Won't that obviate the need for KVM_{GET|SET}_SREGS2 since KVM will always load
> the PDPTRs from memory? IMO, nested migration with shadowing paging doesn't
> warrant this level of optimization complexity.
Its not an optimization, it was done to be 100% within the X86 spec.
PDPTRs are internal cpu registers which are loaded only when
CR3/CR0/CR4 are written by the guest, guest entry loads CR3, or
when guest exit loads CR3 (I checked both Intel and AMD manuals).
In addition to that when NPT is enabled, AMD drops this siliness and
just treats PDPTRs as normal paging entries, while on Intel side
when EPT is enabled, PDPTRs are stored in VMCS.
Nested migration is neither of these cases, thus PDPTRs should be
stored out of band.
Same for non nested migration.
This was requested by Jim Mattson, and I went ahead and
implemented it, even though I do understand that no sane OS
relies on PDPTRs to be unsync v.s the actual page
table containing them.
Best regards,
Maxim Levitsky
>
> [*] For some definitions of "optimization", since the extra pdptrs_changed()
> check in the existing code is likely a net negative.
>
> > return -EINVAL;
> > - }
> >
> > /*
> > * TODO: optimize unconditional TLB flush/MMU sync here and in
next prev parent reply other threads:[~2021-04-06 10:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 14:18 [PATCH 0/6] Introduce KVM_{GET|SET}_SREGS2 and fix PDPTR migration Maxim Levitsky
2021-04-01 14:18 ` [PATCH 1/6] KVM: nVMX: delay loading of PDPTRs to KVM_REQ_GET_NESTED_STATE_PAGES Maxim Levitsky
2021-04-01 14:31 ` Paolo Bonzini
2021-04-02 17:27 ` Sean Christopherson
2021-04-06 10:22 ` Maxim Levitsky
2021-04-01 14:18 ` [PATCH 2/6] KVM: nSVM: call nested_svm_load_cr3 on nested state load Maxim Levitsky
2021-04-01 14:31 ` Paolo Bonzini
2021-04-01 14:18 ` [PATCH 3/6] KVM: x86: introduce kvm_register_clear_available Maxim Levitsky
2021-04-01 14:31 ` Paolo Bonzini
2021-04-05 17:03 ` Sean Christopherson
2021-04-01 14:18 ` [PATCH 4/6] KVM: x86: Introduce KVM_GET_SREGS2 / KVM_SET_SREGS2 Maxim Levitsky
2021-04-01 14:44 ` Paolo Bonzini
2021-04-01 17:10 ` Maxim Levitsky
2021-04-01 17:33 ` Paolo Bonzini
2021-04-01 14:18 ` [PATCH 5/6] KVM: nSVM: avoid loading PDPTRs after migration when possible Maxim Levitsky
2021-04-05 17:01 ` Sean Christopherson
2021-04-06 10:12 ` Maxim Levitsky [this message]
2021-04-01 14:18 ` [PATCH 6/6] KVM: nVMX: " Maxim Levitsky
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=8ffa121b8be00cd30c93830c476a448cee895abc.camel@redhat.com \
--to=mlevitsk@redhat.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.