From: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
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>,
David Hildenbrand <david@redhat.com>,
David Matlack <dmatlack@google.com>,
Ben Gardon <bgardon@google.com>,
Mingwei Zhang <mizhang@google.com>
Subject: Re: [PATCH v4 00/30] KVM: x86/mmu: Overhaul TDP MMU zapping and flushing
Date: Tue, 8 Mar 2022 18:25:52 +0100 [thread overview]
Message-ID: <d5b7d8f0-0f71-b6e5-5acd-d953486ee918@redhat.com> (raw)
In-Reply-To: <20220303193842.370645-1-pbonzini@redhat.com>
On 3/3/22 20:38, Paolo Bonzini wrote:
>
> Overhaul TDP MMU's handling of zapping and TLB flushing to reduce the
> number of TLB flushes, fix soft lockups and RCU stalls, avoid blocking
> vCPUs for long durations while zapping paging structure, and to clean up
> the zapping code.
>
> The largest cleanup is to separate the flows for zapping roots (zap
> _everything_), zapping leaf SPTEs (zap guest mappings for whatever reason),
> and zapping a specific SP (NX recovery). They're currently smushed into a
> single zap_gfn_range(), which was a good idea at the time, but became a
> mess when trying to handle the different rules, e.g. TLB flushes aren't
> needed when zapping a root because KVM can safely zap a root if and only
> if it's unreachable.
>
> To solve the soft lockups, stalls, and vCPU performance issues:
>
> - Defer remote TLB flushes to the caller when zapping TDP MMU shadow
> pages by relying on RCU to ensure the paging structure isn't freed
> until all vCPUs have exited the guest.
>
> - Allowing yielding when zapping TDP MMU roots in response to the root's
> last reference being put. This requires a bit of trickery to ensure
> the root is reachable via mmu_notifier, but it's not too gross.
>
> - Zap roots in two passes to avoid holding RCU for potential hundreds of
> seconds when zapping guest with terabytes of memory that is backed
> entirely by 4kb SPTEs.
>
> - Zap defunct roots asynchronously via the common work_queue so that a
> vCPU doesn't get stuck doing the work if the vCPU happens to drop the
> last reference to a root.
>
> The selftest at the end allows populating a guest with the max amount of
> memory allowed by the underlying architecture. The most I've tested is
> ~64tb (MAXPHYADDR=46) as I don't have easy access to a system with
> MAXPHYADDR=52. The selftest compiles on arm64 and s390x, but otherwise
> hasn't been tested outside of x86-64. It will hopefully do something
> useful as is, but there's a non-zero chance it won't get past init with
> a high max memory. Running on x86 without the TDP MMU is comically slow.
>
> Testing: passes kvm-unit-tests and guest installation tests on Intel.
> Haven't yet run AMD or selftests.
>
> Thanks,
>
> Paolo
>
> v4:
> - collected reviews and typo fixes (plus some typo fixes of my own)
>
> - new patches to simplify reader invariants: they are not allowed to
> acquire references to invalid roots
>
> - new version of "Allow yielding when zapping GFNs for defunct TDP MMU
> root", simplifying the atomic a bit by 1) using xchg and relying on
> its implicit memory barriers 2) relying on readers to have the same
> behavior for the three stats refcount=0/valid, refcount=0/invalid,
> refcount=1/invalid (see previous point)
>
> - switch zapping of invalidated roots to asynchronous workers on a
> per-VM workqueue, fixing a bug in v3 where the extra reference added
> by kvm_tdp_mmu_put_root could be given back twice. This also replaces
> "KVM: x86/mmu: Use common iterator for walking invalid TDP MMU roots"
> in v3, since it gets rid of next_invalidated_root() in a different way.
>
> - because of the previous point, most of the logic in v3's "KVM: x86/mmu:
> Zap defunct roots via asynchronous worker" moves to the earlier patch
> "KVM: x86/mmu: Zap invalidated roots via asynchronous worker"
>
>
> v3:
> - Drop patches that were applied.
> - Rebase to latest kvm/queue.
> - Collect a review. [David]
> - Use helper instead of goto to zap roots in two passes. [David]
> - Add patches to disallow REMOVED "old" SPTE when atomically
> setting SPTE.
>
> Paolo Bonzini (5):
> KVM: x86/mmu: only perform eager page splitting on valid roots
> KVM: x86/mmu: do not allow readers to acquire references to invalid roots
> KVM: x86/mmu: Zap invalidated roots via asynchronous worker
> KVM: x86/mmu: Allow yielding when zapping GFNs for defunct TDP MMU root
> KVM: x86/mmu: Zap defunct roots via asynchronous worker
>
> Sean Christopherson (25):
> KVM: x86/mmu: Check for present SPTE when clearing dirty bit in TDP MMU
> KVM: x86/mmu: Fix wrong/misleading comments in TDP MMU fast zap
> KVM: x86/mmu: Formalize TDP MMU's (unintended?) deferred TLB flush logic
> KVM: x86/mmu: Document that zapping invalidated roots doesn't need to flush
> KVM: x86/mmu: Require mmu_lock be held for write in unyielding root iter
> KVM: x86/mmu: Check for !leaf=>leaf, not PFN change, in TDP MMU SP removal
> KVM: x86/mmu: Batch TLB flushes from TDP MMU for MMU notifier change_spte
> KVM: x86/mmu: Drop RCU after processing each root in MMU notifier hooks
> KVM: x86/mmu: Add helpers to read/write TDP MMU SPTEs and document RCU
> KVM: x86/mmu: WARN if old _or_ new SPTE is REMOVED in non-atomic path
> KVM: x86/mmu: Refactor low-level TDP MMU set SPTE helper to take raw values
> KVM: x86/mmu: Zap only the target TDP MMU shadow page in NX recovery
> KVM: x86/mmu: Skip remote TLB flush when zapping all of TDP MMU
> KVM: x86/mmu: Add dedicated helper to zap TDP MMU root shadow page
> KVM: x86/mmu: Require mmu_lock be held for write to zap TDP MMU range
> KVM: x86/mmu: Zap only TDP MMU leafs in kvm_zap_gfn_range()
> KVM: x86/mmu: Do remote TLB flush before dropping RCU in TDP MMU resched
> KVM: x86/mmu: Defer TLB flush to caller when freeing TDP MMU shadow pages
> KVM: x86/mmu: Zap roots in two passes to avoid inducing RCU stalls
> KVM: x86/mmu: Check for a REMOVED leaf SPTE before making the SPTE
> KVM: x86/mmu: WARN on any attempt to atomically update REMOVED SPTE
> KVM: selftests: Move raw KVM_SET_USER_MEMORY_REGION helper to utils
> KVM: selftests: Split out helper to allocate guest mem via memfd
> KVM: selftests: Define cpu_relax() helpers for s390 and x86
> KVM: selftests: Add test to populate a VM with the max possible guest mem
>
> arch/x86/include/asm/kvm_host.h | 2 +
> arch/x86/kvm/mmu/mmu.c | 49 +-
> arch/x86/kvm/mmu/mmu_internal.h | 15 +-
> arch/x86/kvm/mmu/tdp_iter.c | 6 +-
> arch/x86/kvm/mmu/tdp_iter.h | 15 +-
> arch/x86/kvm/mmu/tdp_mmu.c | 559 +++++++++++-------
> arch/x86/kvm/mmu/tdp_mmu.h | 26 +-
> tools/testing/selftests/kvm/.gitignore | 1 +
> tools/testing/selftests/kvm/Makefile | 3 +
> .../selftests/kvm/include/kvm_util_base.h | 5 +
> .../selftests/kvm/include/s390x/processor.h | 8 +
> .../selftests/kvm/include/x86_64/processor.h | 5 +
> tools/testing/selftests/kvm/lib/kvm_util.c | 66 ++-
> .../selftests/kvm/max_guest_memory_test.c | 292 +++++++++
> .../selftests/kvm/set_memory_region_test.c | 35 +-
> 15 files changed, 794 insertions(+), 293 deletions(-)
> create mode 100644 tools/testing/selftests/kvm/max_guest_memory_test.c
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2022-03-08 17:26 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 19:38 [PATCH v4 00/30] KVM: x86/mmu: Overhaul TDP MMU zapping and flushing Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 01/30] KVM: x86/mmu: Check for present SPTE when clearing dirty bit in TDP MMU Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 02/30] KVM: x86/mmu: Fix wrong/misleading comments in TDP MMU fast zap Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 03/30] KVM: x86/mmu: Formalize TDP MMU's (unintended?) deferred TLB flush logic Paolo Bonzini
2022-03-03 23:39 ` Mingwei Zhang
2022-03-03 19:38 ` [PATCH v4 04/30] KVM: x86/mmu: Document that zapping invalidated roots doesn't need to flush Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 05/30] KVM: x86/mmu: Require mmu_lock be held for write in unyielding root iter Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 06/30] KVM: x86/mmu: only perform eager page splitting on valid roots Paolo Bonzini
2022-03-03 20:03 ` Sean Christopherson
2022-03-03 19:38 ` [PATCH v4 07/30] KVM: x86/mmu: do not allow readers to acquire references to invalid roots Paolo Bonzini
2022-03-03 20:12 ` Sean Christopherson
2022-03-03 19:38 ` [PATCH v4 08/30] KVM: x86/mmu: Check for !leaf=>leaf, not PFN change, in TDP MMU SP removal Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 09/30] KVM: x86/mmu: Batch TLB flushes from TDP MMU for MMU notifier change_spte Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 10/30] KVM: x86/mmu: Drop RCU after processing each root in MMU notifier hooks Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 11/30] KVM: x86/mmu: Add helpers to read/write TDP MMU SPTEs and document RCU Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 12/30] KVM: x86/mmu: WARN if old _or_ new SPTE is REMOVED in non-atomic path Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 13/30] KVM: x86/mmu: Refactor low-level TDP MMU set SPTE helper to take raw values Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 14/30] KVM: x86/mmu: Zap only the target TDP MMU shadow page in NX recovery Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 15/30] KVM: x86/mmu: Skip remote TLB flush when zapping all of TDP MMU Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 16/30] KVM: x86/mmu: Add dedicated helper to zap TDP MMU root shadow page Paolo Bonzini
2022-03-04 0:07 ` Mingwei Zhang
2022-03-03 19:38 ` [PATCH v4 17/30] KVM: x86/mmu: Require mmu_lock be held for write to zap TDP MMU range Paolo Bonzini
2022-03-04 0:14 ` Mingwei Zhang
2022-03-03 19:38 ` [PATCH v4 18/30] KVM: x86/mmu: Zap only TDP MMU leafs in kvm_zap_gfn_range() Paolo Bonzini
2022-03-04 1:16 ` Mingwei Zhang
2022-03-04 16:11 ` Sean Christopherson
2022-03-04 18:00 ` Mingwei Zhang
2022-03-04 18:42 ` Sean Christopherson
2022-03-11 15:09 ` Vitaly Kuznetsov
2022-03-13 18:40 ` Mingwei Zhang
2022-03-25 15:13 ` Sean Christopherson
2022-03-26 18:10 ` Mingwei Zhang
2022-03-28 15:06 ` Sean Christopherson
2022-03-03 19:38 ` [PATCH v4 19/30] KVM: x86/mmu: Do remote TLB flush before dropping RCU in TDP MMU resched Paolo Bonzini
2022-03-04 1:19 ` Mingwei Zhang
2022-03-03 19:38 ` [PATCH v4 20/30] KVM: x86/mmu: Defer TLB flush to caller when freeing TDP MMU shadow pages Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 21/30] KVM: x86/mmu: Zap invalidated roots via asynchronous worker Paolo Bonzini
2022-03-03 20:54 ` Sean Christopherson
2022-03-03 21:06 ` Sean Christopherson
2022-03-03 21:20 ` Sean Christopherson
2022-03-03 21:32 ` Sean Christopherson
2022-03-04 6:48 ` Paolo Bonzini
2022-03-04 16:02 ` Sean Christopherson
2022-03-04 18:11 ` Paolo Bonzini
2022-03-05 0:34 ` Sean Christopherson
2022-03-05 19:53 ` Paolo Bonzini
2022-03-08 21:29 ` Sean Christopherson
2022-03-11 17:50 ` Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 22/30] KVM: x86/mmu: Allow yielding when zapping GFNs for defunct TDP MMU root Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 23/30] KVM: x86/mmu: Zap roots in two passes to avoid inducing RCU stalls Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 24/30] KVM: x86/mmu: Zap defunct roots via asynchronous worker Paolo Bonzini
2022-03-03 22:08 ` Sean Christopherson
2022-03-03 19:38 ` [PATCH v4 25/30] KVM: x86/mmu: Check for a REMOVED leaf SPTE before making the SPTE Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 26/30] KVM: x86/mmu: WARN on any attempt to atomically update REMOVED SPTE Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 27/30] KVM: selftests: Move raw KVM_SET_USER_MEMORY_REGION helper to utils Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 28/30] KVM: selftests: Split out helper to allocate guest mem via memfd Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 29/30] KVM: selftests: Define cpu_relax() helpers for s390 and x86 Paolo Bonzini
2022-03-03 19:38 ` [PATCH v4 30/30] KVM: selftests: Add test to populate a VM with the max possible guest mem Paolo Bonzini
2022-03-08 14:47 ` Paolo Bonzini
2022-03-08 15:36 ` Christian Borntraeger
2022-03-08 21:09 ` Sean Christopherson
2022-03-08 17:25 ` Paolo Bonzini [this message]
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=d5b7d8f0-0f71-b6e5-5acd-d953486ee918@redhat.com \
--to=pbonzini@redhat.com \
--cc=bgardon@google.com \
--cc=david@redhat.com \
--cc=dmatlack@google.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mizhang@google.com \
--cc=seanjc@google.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;
as well as URLs for NNTP newsgroup(s).