linux

iv/linux

History

Sean Christopherson acbda82a81 KVM: x86/mmu: Require mmu_lock be held for write to zap TDP MMU range

Now that all callers of zap_gfn_range() hold mmu_lock for write, drop
support for zapping with mmu_lock held for read.  That all callers hold
mmu_lock for write isn't a random coincidence; now that the paths that
need to zap _everything_ have their own path, the only callers left are
those that need to zap for functional correctness.  And when zapping is
required for functional correctness, mmu_lock must be held for write,
otherwise the caller has no guarantees about the state of the TDP MMU
page tables after it has run, e.g. the SPTE(s) it zapped can be
immediately replaced by a vCPU faulting in a page.

Signed-off-by: Sean Christopherson <seanjc@google.com>
Reviewed-by: Ben Gardon <bgardon@google.com>
Message-Id: <20220226001546.360188-17-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

2022-03-08 09:31:55 -05:00

alpha

bitmap patches for 5.17-rc1

2022-01-23 06:20:44 +02:00

arc

bitmap patches for 5.17-rc1

2022-01-23 06:20:44 +02:00

arm

lib/crypto: blake2s: avoid indirect calls to compression function for Clang CFI

2022-02-04 19:22:32 +01:00

arm64

KVM/arm64 fixes for 5.17, take #4