From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xiao Guangrong Subject: Re: [v3 4/5] vfio: implement APIs to set/put kvm to/from vfio group Date: Wed, 9 Nov 2016 21:06:23 +0800 Message-ID: <3e5299bc-e08e-f072-1001-7e0432cb1ca8@linux.intel.com> References: <1477895706-22824-1-git-send-email-jike.song@intel.com> <1477895706-22824-5-git-send-email-jike.song@intel.com> <20161107110412.5db26fd4@t450s.home> <20161107112834.2aa971df@t450s.home> <9e83a26f-e5dc-ed91-a1b5-c6f165eed7ed@redhat.com> <58231B5C.3010506@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Alex Williamson , kwankhede@nvidia.com, cjia@nvidia.com, kevin.tian@intel.com, kvm@vger.kernel.org To: Jike Song , Paolo Bonzini Return-path: Received: from mga11.intel.com ([192.55.52.93]:33239 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932185AbcKINNx (ORCPT ); Wed, 9 Nov 2016 08:13:53 -0500 In-Reply-To: <58231B5C.3010506@intel.com> Sender: kvm-owner@vger.kernel.org List-ID: On 11/09/2016 08:49 PM, Jike Song wrote: > +void vfio_group_attach_kvm(struct vfio_group *group, struct kvm *kvm, > + void (*fn)(struct kvm *)) > +{ > + mutex_lock(&group->udata.lock); This lock is needed, please see below. > + > + fn(kvm); > + blocking_notifier_call_chain(&group->udata.notifier, > + VFIO_GROUP_NOTIFY_ATTACH_KVM, kvm); As this is a callback before KVM releases its last refcount, i do not think vendor driver need to get additional KVM refcount.