summaryrefslogtreecommitdiff
path: root/Documentation/virtual/kvm/locking.txt
diff options
context:
space:
mode:
authorJunaid Shahid <junaids@google.com>2019-01-03 17:14:28 -0800
committerPaolo Bonzini <pbonzini@redhat.com>2019-06-05 14:14:50 +0200
commit0d9ce162cf46c99628cc5da9510b959c7976735b (patch)
treecb7670bedf8c614aa20313b95456f942fd16b6d4 /Documentation/virtual/kvm/locking.txt
parent1ae4de23eddef465104277e79fa669bec7b3d288 (diff)
kvm: Convert kvm_lock to a mutex
It doesn't seem as if there is any particular need for kvm_lock to be a spinlock, so convert the lock to a mutex so that sleepable functions (in particular cond_resched()) can be called while holding it. Signed-off-by: Junaid Shahid <junaids@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'Documentation/virtual/kvm/locking.txt')
-rw-r--r--Documentation/virtual/kvm/locking.txt4
1 files changed, 1 insertions, 3 deletions
diff --git a/Documentation/virtual/kvm/locking.txt b/Documentation/virtual/kvm/locking.txt
index 1bb8bcaf8497..635cd6eaf714 100644
--- a/Documentation/virtual/kvm/locking.txt
+++ b/Documentation/virtual/kvm/locking.txt
@@ -15,8 +15,6 @@ The acquisition orders for mutexes are as follows:
On x86, vcpu->mutex is taken outside kvm->arch.hyperv.hv_lock.
-For spinlocks, kvm_lock is taken outside kvm->mmu_lock.
-
Everything else is a leaf: no other lock is taken inside the critical
sections.
@@ -169,7 +167,7 @@ which time it will be set using the Dirty tracking mechanism described above.
------------
Name: kvm_lock
-Type: spinlock_t
+Type: mutex
Arch: any
Protects: - vm_list