lkml.org 
[lkml]   [2021]   [Apr]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
Subject[PATCH 0/6] Lazily allocate memslot rmaps
From
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.

Ben Gardon (6):
KVM: x86/mmu: Track if shadow MMU active
KVM: x86/mmu: Skip rmap operations if shadow MMU inactive
KVM: x86/mmu: Deduplicate rmap freeing in allocate_memslot_rmap
KVM: x86/mmu: Factor out allocating memslot rmap
KVM: x86/mmu: Protect kvm->memslots with a mutex
KVM: x86/mmu: Lazily allocate memslot rmaps

arch/x86/include/asm/kvm_host.h | 20 +++++
arch/x86/kvm/mmu/mmu.c | 153 +++++++++++++++++++++-----------
arch/x86/kvm/mmu/mmu_internal.h | 2 +
arch/x86/kvm/mmu/tdp_mmu.c | 6 +-
arch/x86/kvm/mmu/tdp_mmu.h | 4 +-
arch/x86/kvm/x86.c | 133 +++++++++++++++++++++++----
include/linux/kvm_host.h | 2 +
virt/kvm/kvm_main.c | 48 +++++++---
8 files changed, 283 insertions(+), 85 deletions(-)

--
2.31.1.498.g6c1eba8ee3d-goog

\
 
 \ /
  Last update: 2021-04-28 00:39    [W:0.092 / U:0.512 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site