1
linux/arch
Sean Christopherson 58a20a9435 KVM: x86/mmu: Zap only SPs that shadow gPTEs when deleting memslot
When performing a targeted zap on memslot removal, zap only MMU pages that
shadow guest PTEs, as zapping all SPs that "match" the gfn is inexact and
unnecessary.  Furthermore, for_each_gfn_valid_sp() arguably shouldn't
exist, because it doesn't do what most people would it expect it to do.
The "round gfn for level" adjustment that is done for direct SPs (no gPTE)
means that the exact gfn comparison will not get a match, even when a SP
does "cover" a gfn, or was even created specifically for a gfn.

For memslot deletion specifically, KVM's behavior will vary significantly
based on the size and alignment of a memslot, and in weird ways.  E.g. for
a 4KiB memslot, KVM will zap more SPs if the slot is 1GiB aligned than if
it's only 4KiB aligned.  And as described below, zapping SPs in the
aligned case overzaps for direct MMUs, as odds are good the upper-level
SPs are serving other memslots.

To iterate over all potentially-relevant gfns, KVM would need to make a
pass over the hash table for each level, with the gfn used for lookup
rounded for said level.  And then check that the SP is of the correct
level, too, e.g. to avoid over-zapping.

But even then, KVM would massively overzap, as processing every level is
all but guaranteed to zap SPs that serve other memslots, especially if the
memslot being removed is relatively small.  KVM could mitigate that issue
by processing only levels that can be possible guest huge pages, i.e. are
less likely to be re-used for other memslot, but while somewhat logical,
that's quite arbitrary and would be a bit of a mess to implement.

So, zap only SPs with gPTEs, as the resulting behavior is easy to describe,
is predictable, and is explicitly minimal, i.e. KVM only zaps SPs that
absolutely must be zapped.

Cc: Yan Zhao <yan.y.zhao@intel.com>
Signed-off-by: Sean Christopherson <seanjc@google.com>
Reviewed-by: Yan Zhao <yan.y.zhao@intel.com>
Tested-by: Yan Zhao <yan.y.zhao@intel.com>
Message-ID: <20241009192345.1148353-2-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2024-10-20 07:08:17 -04:00
..
alpha asm-generic updates for 6.12 2024-09-26 11:54:40 -07:00
arc Kbuild updates for v6.12 2024-09-24 13:02:06 -07:00
arm soc: convert ep93xx to devicetree 2024-09-26 12:00:25 -07:00
arm64 KVM: arm64: Fix kvm_has_feat*() handling of negative features 2024-10-03 19:35:27 +01:00
csky
hexagon hexagon: vdso: Fix build failure 2024-09-23 08:17:50 -07:00
loongarch x86: 2024-09-28 09:20:14 -07:00
m68k m68knommu: updates and fixes for v6.12 2024-09-24 10:48:44 -07:00
microblaze
mips x86: 2024-09-28 09:20:14 -07:00
nios2
openrisc
parisc [tree-wide] finally take no_llseek out 2024-09-27 08:18:43 -07:00
powerpc powerpc fixes for 6.12 #2 2024-09-25 11:17:25 -07:00
riscv x86: 2024-09-28 09:20:14 -07:00
s390 x86: 2024-09-28 09:20:14 -07:00
sh sh updates for v6.12 2024-09-27 10:10:21 -07:00
sparc This includes the following changes related to sparc for v6.12: 2024-09-25 11:21:06 -07:00
um This pull request contains the following changes for UML: 2024-09-27 12:48:48 -07:00
x86 KVM: x86/mmu: Zap only SPs that shadow gPTEs when deleting memslot 2024-10-20 07:08:17 -04:00
xtensa ALong with the usual shower of singleton patches, notable patch series in 2024-09-21 07:29:05 -07:00
.gitignore
Kconfig Rust changes for v6.12 2024-09-25 10:25:40 -07:00