Commit 69116e01 authored by Fuad Tabba's avatar Fuad Tabba Committed by Paolo Bonzini
Browse files

KVM: Fix comments that refer to slots_lock 



Fix comments so that they refer to slots_lock instead of slots_locks
(remove trailing s).

Reviewed-by: default avatarDavid Hildenbrand <david@redhat.com>
Reviewed-by: default avatarIra Weiny <ira.weiny@intel.com>
Reviewed-by: default avatarGavin Shan <gshan@redhat.com>
Reviewed-by: default avatarShivank Garg <shivankg@amd.com>
Reviewed-by: default avatarVlastimil Babka <vbabka@suse.cz>
Reviewed-by: default avatarXiaoyao Li <xiaoyao.li@intel.com>
Signed-off-by: default avatarFuad Tabba <tabba@google.com>
Signed-off-by: default avatarSean Christopherson <seanjc@google.com>
Message-ID: <20250729225455.670324-8-seanjc@google.com>
Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
parent 923310be

include/linux/kvm_host.h

+1 −1
Original line number Diff line number Diff line
@@ -860,7 +860,7 @@ struct kvm { 
	struct notifier_block pm_notifier;

#endif

#ifdef CONFIG_KVM_GENERIC_MEMORY_ATTRIBUTES

	/* Protected by slots_locks (for writes) and RCU (for reads) */

	/* Protected by slots_lock (for writes) and RCU (for reads) */

	struct xarray mem_attr_array;

#endif

	char stats_id[KVM_STATS_NAME_SIZE];

virt/kvm/kvm_main.c

+1 −1
Original line number Diff line number Diff line
@@ -331,7 +331,7 @@ void kvm_flush_remote_tlbs_memslot(struct kvm *kvm, 
	 * All current use cases for flushing the TLBs for a specific memslot

	 * are related to dirty logging, and many do the TLB flush out of

	 * mmu_lock. The interaction between the various operations on memslot

	 * must be serialized by slots_locks to ensure the TLB flush from one

	 * must be serialized by slots_lock to ensure the TLB flush from one

	 * operation is observed by any other operation on the same memslot.

	 */

	lockdep_assert_held(&kvm->slots_lock);