[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <813695b1-bcfc-73ea-f9fe-76ffd42044cd@redhat.com>
Date: Wed, 3 Feb 2021 12:26:50 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Ben Gardon <bgardon@...gle.com>, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org
Cc: Peter Xu <peterx@...hat.com>,
Sean Christopherson <seanjc@...gle.com>,
Peter Shier <pshier@...gle.com>,
Peter Feiner <pfeiner@...gle.com>,
Junaid Shahid <junaids@...gle.com>,
Jim Mattson <jmattson@...gle.com>,
Yulei Zhang <yulei.kernel@...il.com>,
Wanpeng Li <kernellwp@...il.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Xiao Guangrong <xiaoguangrong.eric@...il.com>
Subject: Re: [PATCH v2 24/28] KVM: x86/mmu: Allow zap gfn range to operate
under the mmu read lock
On 02/02/21 19:57, Ben Gardon wrote:
> +#ifdef CONFIG_LOCKDEP
> + if (shared)
> + lockdep_assert_held_read(&kvm->mmu_lock);
> + else
> + lockdep_assert_held_write(&kvm->mmu_lock);
> +#endif /* CONFIG_LOCKDEP */
Also, there's no need for the #ifdef here. Do we want a helper
kvm_lockdep_assert_mmu_lock_held(struct kvm *kvm, bool shared)?
Paolo
Powered by blists - more mailing lists