From: Paolo Bonzini <pbonzini@redhat.com>
To: Ben Gardon <bgardon@google.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: Peter Xu <peterx@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Peter Shier <pshier@google.com>,
Yulei Zhang <yulei.kernel@gmail.com>,
Wanpeng Li <kernellwp@gmail.com>,
Xiao Guangrong <xiaoguangrong.eric@gmail.com>,
Kai Huang <kai.huang@intel.com>,
Keqian Zhu <zhukeqian1@huawei.com>,
David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH v5 0/7] Lazily allocate memslot rmaps
Date: Mon, 24 May 2021 14:43:56 +0200 [thread overview]
Message-ID: <85bdd768-d7a3-100c-aade-ef5910b6e729@redhat.com> (raw)
In-Reply-To: <20210518173414.450044-1-bgardon@google.com>
On 18/05/21 19:34, Ben Gardon wrote:
> This series enables KVM to save memory when using the TDP MMU by waiting
> to allocate memslot rmaps until they are needed. To do this, KVM tracks
> whether or not a shadow root has been allocated. In order to get away
> with not allocating the rmaps, KVM must also be sure to skip operations
> which iterate over the rmaps. If the TDP MMU is in use and we have not
> allocated a shadow root, these operations would essentially be op-ops
> anyway. Skipping the rmap operations has a secondary benefit of avoiding
> acquiring the MMU lock in write mode in many cases, substantially
> reducing MMU lock contention.
>
> This series was tested on an Intel Skylake machine. With the TDP MMU off
> and on, this introduced no new failures on kvm-unit-tests or KVM selftests.
>
> Changelog:
> v2:
> Incorporated feedback from Paolo and Sean
> Replaced the memslot_assignment_lock with slots_arch_lock, which
> has a larger critical section.
>
> v3:
> Removed shadow_mmu_active as suggested by Sean
> Removed everything except adding a return value to
> kvm_mmu_init_tdp_mmu from patch 1 of v2
> Added RCU protection and better memory ordering for installing the
> memslot rmaps as suggested by Paolo
> Reordered most of the patches
>
> v4:
> Renamed functions to allocate and free memslots based on feedback
> from David.
> Eliminated the goto in memslot_rmap_alloc, as David suggested.
> Eliminated kvm_memslots_have_rmaps and updated comments on uses of
> memslots_have_rmaps. Suggested by Paolo.
> Changed the description on patch 7 to one Paolo suggested.
> Collected Reviewed-by tags from David.
> Dropped the patch to add RCU notations to rmap accesses.
>
> v5:
> Responding to comments from Sean.
> Improved comments
> Swapped args to kvm_copy_memslots to match memcpy
> Fixed some line wrap and declaration style issues
> No longer check if memslots have rmaps before operations which
> iterate through active_mmu_pages
> Re-added the kvm_memslots_have_rmaps helper
> Fixed a couple missing unlocks for the slots_arch_lock
Queued (with minor conflicts), thanks!
Paolo
prev parent reply other threads:[~2021-05-24 12:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 17:34 Ben Gardon
2021-05-18 17:34 ` [PATCH v5 1/7] KVM: x86/mmu: Deduplicate rmap freeing Ben Gardon
2021-05-18 17:34 ` [PATCH v5 2/7] KVM: x86/mmu: Factor out allocating memslot rmap Ben Gardon
2021-05-18 17:34 ` [PATCH v5 3/7] KVM: mmu: Refactor memslot copy Ben Gardon
2021-05-18 17:34 ` [PATCH v5 4/7] KVM: mmu: Add slots_arch_lock for memslot arch fields Ben Gardon
2021-05-18 17:34 ` [PATCH v5 5/7] KVM: x86/mmu: Add a field to control memslot rmap allocation Ben Gardon
2021-05-18 17:34 ` [PATCH v5 6/7] KVM: x86/mmu: Skip rmap operations if rmaps not allocated Ben Gardon
2021-05-18 17:34 ` [PATCH v5 7/7] KVM: x86/mmu: Lazily allocate memslot rmaps Ben Gardon
2021-05-24 12:43 ` 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=85bdd768-d7a3-100c-aade-ef5910b6e729@redhat.com \
--to=pbonzini@redhat.com \
--cc=bgardon@google.com \
--cc=david@redhat.com \
--cc=kai.huang@intel.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=pshier@google.com \
--cc=seanjc@google.com \
--cc=xiaoguangrong.eric@gmail.com \
--cc=yulei.kernel@gmail.com \
--cc=zhukeqian1@huawei.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®