summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2024-09-27 17:45:45 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2024-09-27 17:45:50 +0200
commitefbc6bd090f48ccf64f7a8dd5daea775821d57ec (patch)
tree724f1544e8421a8d4385e3ae18da2eda4dd6fb6b
parentMerge tag 'kvm-x86-vmx-6.12' of https://github.com/kvm-x86/linux into HEAD (diff)
downloadlinux-efbc6bd090f48ccf64f7a8dd5daea775821d57ec.tar.xz
linux-efbc6bd090f48ccf64f7a8dd5daea775821d57ec.zip
Documentation: KVM: fix warning in "make htmldocs"
The warning Documentation/virt/kvm/locking.rst:31: ERROR: Unexpected indentation. is caused by incorrectly treating a line as the continuation of a paragraph, rather than as the first line in a bullet list. Fixed: 44d174596260 ("KVM: Use dedicated mutex to protect kvm_usage_count to avoid deadlock") Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
-rw-r--r--Documentation/virt/kvm/locking.rst1
1 files changed, 1 insertions, 0 deletions
diff --git a/Documentation/virt/kvm/locking.rst b/Documentation/virt/kvm/locking.rst
index be3c323888b1..20a9a37d1cdd 100644
--- a/Documentation/virt/kvm/locking.rst
+++ b/Documentation/virt/kvm/locking.rst
@@ -27,6 +27,7 @@ The acquisition orders for mutexes are as follows:
must not take either kvm->slots_lock or kvm->slots_arch_lock.
cpus_read_lock() vs kvm_lock:
+
- Taking cpus_read_lock() outside of kvm_lock is problematic, despite that
being the official ordering, as it is quite easy to unknowingly trigger
cpus_read_lock() while holding kvm_lock. Use caution when walking vm_list,