From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <seanjc@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] KVM: x86: Kill off pdptrs_changed()
Date: Thu, 22 Apr 2021 17:06:33 -0700 [thread overview]
Message-ID: <20210423000637.3692951-1-seanjc@google.com> (raw)
Remove pdptrs_changed(), which is mostly dead anyways, and the few bits
that are still thrashing are useless.
This conflicts with Maxim's work to migrate PDPTRs out-of-band, but I
think it will conflict in a good way as the "skip load_pdptrs()"
logic for the out-of-band case won't have to juggle this legacy crud.
Sean Christopherson (4):
KVM: nVMX: Drop obsolete (and pointless) pdptrs_changed() check
KVM: nSVM: Drop pointless pdptrs_changed() check on nested transition
KVM: x86: Always load PDPTRs on CR3 load for SVM w/o NPT and a PAE
guest
KVM: x86: Unexport kvm_read_guest_page_mmu()
arch/x86/include/asm/kvm_host.h | 4 ----
arch/x86/kvm/svm/nested.c | 6 ++---
arch/x86/kvm/vmx/nested.c | 8 +++----
arch/x86/kvm/x86.c | 41 ++++-----------------------------
4 files changed, 10 insertions(+), 49 deletions(-)
--
2.31.1.498.g6c1eba8ee3d-goog
next reply other threads:[~2021-04-23 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 0:06 Sean Christopherson [this message]
2021-04-23 0:06 ` [PATCH 1/4] KVM: nVMX: Drop obsolete (and pointless) pdptrs_changed() check Sean Christopherson
2021-04-23 0:06 ` [PATCH 2/4] KVM: nSVM: Drop pointless pdptrs_changed() check on nested transition Sean Christopherson
2021-04-23 0:06 ` [PATCH 3/4] KVM: x86: Always load PDPTRs on CR3 load for SVM w/o NPT and a PAE guest Sean Christopherson
2021-04-23 0:06 ` [PATCH 4/4] KVM: x86: Unexport kvm_read_guest_page_mmu() Sean Christopherson
2021-04-23 7:04 ` [PATCH 0/4] KVM: x86: Kill off pdptrs_changed() 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=20210423000637.3692951-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
/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
all inboxes | Powered by JetHome®