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,
Ben Gardon <bgardon@google.com>
Subject: [PATCH v2 0/2] KVM: x86/mmu: Fix a TDP MMU leak and optimize zap all
Date: Thu, 12 Aug 2021 11:14:12 -0700 [thread overview]
Message-ID: <20210812181414.3376143-1-seanjc@google.com> (raw)
Patch 1 fixes a leak of root-1 shadow pages, patch 2 is a minor
optimization to the zap all flow that avoids re-reading and re-checking
the root-1 SPTEs after they've been zapped by "zap all" flows.
I'm still somewhat on the fence for patch 2, feel free to drop it.
v2:
- Replaced magic number silliness with Paolo's much more clever suggestion.
- Elaborated on the benefits of the optimization.
- Add Ben's somewhat reluctant review for the optimization.
v1: https://lkml.kernel.org/r/20210812050717.3176478-1-seanjc@google.com
Sean Christopherson (2):
KVM: x86/mmu: Don't leak non-leaf SPTEs when zapping all SPTEs
KVM: x86/mmu: Don't step down in the TDP iterator when zapping all
SPTEs
arch/x86/kvm/mmu/tdp_mmu.c | 35 ++++++++++++++++++++++++-----------
1 file changed, 24 insertions(+), 11 deletions(-)
--
2.33.0.rc1.237.g0d66db33f3-goog
next reply other threads:[~2021-08-12 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 18:14 Sean Christopherson [this message]
2021-08-12 18:14 ` [PATCH v2 1/2] KVM: x86/mmu: Don't leak non-leaf SPTEs when zapping all SPTEs Sean Christopherson
2021-08-12 18:14 ` [PATCH v2 2/2] KVM: x86/mmu: Don't step down in the TDP iterator " Sean Christopherson
2021-08-13 7:36 ` [PATCH v2 0/2] KVM: x86/mmu: Fix a TDP MMU leak and optimize zap all 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=20210812181414.3376143-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=bgardon@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®