From: Ackerley Tng Now that the first sentence is already described in more detail in the new section on synchronization while managing guest faults, drop the first sentence. Signed-off-by: Ackerley Tng --- Documentation/virt/kvm/locking.rst | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/Documentation/virt/kvm/locking.rst b/Documentation/virt/kvm/locking.rst index 0663ccfe0633d..f26ea3acd0b70 100644 --- a/Documentation/virt/kvm/locking.rst +++ b/Documentation/virt/kvm/locking.rst @@ -26,11 +26,9 @@ The acquisition orders for mutexes are as follows: - vcpu->mutex is taken outside kvm->slots_lock and kvm->slots_arch_lock -- kvm->mn_active_invalidate_count ensures that pairs of - invalidate_range_start() and invalidate_range_end() callbacks - use the same memslots array. kvm->slots_lock and kvm->slots_arch_lock - are taken on the waiting side when modifying memslots, so MMU notifiers - must not take either kvm->slots_lock or kvm->slots_arch_lock. +- kvm->slots_lock and kvm->slots_arch_lock are taken on the waiting side when + modifying memslots, so MMU notifiers must not take either kvm->slots_lock or + kvm->slots_arch_lock. For SRCU: -- 2.54.0.823.g6e5bcc1fc9-goog