kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jike Song <jike.song@intel.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: pbonzini@redhat.com, guangrong.xiao@linux.intel.com,
	kwankhede@nvidia.com, cjia@nvidia.com, kevin.tian@intel.com,
	kvm@vger.kernel.org
Subject: Re: [v6 1/3] vfio: vfio_register_notifier: classify iommu notifier
Date: Sat, 19 Nov 2016 11:32:31 +0800	[thread overview]
Message-ID: <582FC7CF.305@intel.com> (raw)
In-Reply-To: <20161118105553.635ec83e@t450s.home>

On 11/19/2016 01:55 AM, Alex Williamson wrote:
> On Fri, 18 Nov 2016 19:01:47 +0800
> Jike Song <jike.song@intel.com> wrote:
> 
>> Currently vfio_register_notifier assumes that there is only one
>> notifier chain, which is in vfio_iommu. However, the user might
>> also be interested in events other than vfio_iommu, for example,
>> vfio_group. Refactor vfio_{un}register_notifier implementation
>> to make it feasible.
>>
>> Cc: Alex Williamson <alex.williamson@redhat.com>
>> Cc: Kirti Wankhede <kwankhede@nvidia.com>
>> Cc: Paolo Bonzini <pbonzini@redhat.com>
>> Cc: Xiao Guangrong <guangrong.xiao@linux.intel.com>
>> Signed-off-by: Jike Song <jike.song@intel.com>
>> ---
>>  drivers/vfio/vfio.c  | 87 +++++++++++++++++++++++++++++++++++++++-------------
>>  include/linux/vfio.h | 16 ++++++++--
>>  2 files changed, 78 insertions(+), 25 deletions(-)
>>
>> diff --git a/drivers/vfio/vfio.c b/drivers/vfio/vfio.c
>> index c815067..ec62bec 100644
>> --- a/drivers/vfio/vfio.c
>> +++ b/drivers/vfio/vfio.c
>> @@ -2007,23 +2007,24 @@ int vfio_unpin_pages(struct device *dev, unsigned long *user_pfn, int npage)
>>  }
>>  EXPORT_SYMBOL(vfio_unpin_pages);
>>  
>> -int vfio_register_notifier(struct device *dev, struct notifier_block *nb)
>> +static int vfio_register_iommu_notifier(struct vfio_group *group,
>> +					unsigned long *events,
>> +					struct notifier_block *nb)
>>  {
>>  	struct vfio_container *container;
>> -	struct vfio_group *group;
>>  	struct vfio_iommu_driver *driver;
>>  	int ret;
>>  
>> -	if (!dev || !nb)
>> -		return -EINVAL;
>> +	/* clear known events */
>> +	*events &= ~VFIO_IOMMU_NOTIFY_DMA_UNMAP;
>>  
>> -	group = vfio_group_get_from_dev(dev);
>> -	if (IS_ERR(group))
>> -		return PTR_ERR(group);
>> +	/* refuse to register if still events remaining */
>> +	if (*events)
>> +		return -EINVAL;
>>  
>>  	ret = vfio_group_add_container_user(group);
>>  	if (ret)
>> -		goto err_register_nb;
>> +		return -EINVAL;
>>  
>>  	container = group->container;
>>  	down_read(&container->group_lock);
>> @@ -2037,29 +2038,19 @@ int vfio_register_notifier(struct device *dev, struct notifier_block *nb)
>>  	up_read(&container->group_lock);
>>  	vfio_group_try_dissolve_container(group);
>>  
>> -err_register_nb:
>> -	vfio_group_put(group);
>>  	return ret;
>>  }
>> -EXPORT_SYMBOL(vfio_register_notifier);
>>  
>> -int vfio_unregister_notifier(struct device *dev, struct notifier_block *nb)
>> +static int vfio_unregister_iommu_notifier(struct vfio_group *group,
>> +					  struct notifier_block *nb)
>>  {
>>  	struct vfio_container *container;
>> -	struct vfio_group *group;
>>  	struct vfio_iommu_driver *driver;
>>  	int ret;
>>  
>> -	if (!dev || !nb)
>> -		return -EINVAL;
>> -
>> -	group = vfio_group_get_from_dev(dev);
>> -	if (IS_ERR(group))
>> -		return PTR_ERR(group);
>> -
>>  	ret = vfio_group_add_container_user(group);
>>  	if (ret)
>> -		goto err_unregister_nb;
>> +		return -EINVAL;
>>  
>>  	container = group->container;
>>  	down_read(&container->group_lock);
>> @@ -2074,7 +2065,59 @@ int vfio_unregister_notifier(struct device *dev, struct notifier_block *nb)
>>  	up_read(&container->group_lock);
>>  	vfio_group_try_dissolve_container(group);
>>  
>> -err_unregister_nb:
>> +	return ret;
>> +}
>> +
>> +int vfio_register_notifier(struct device *dev, vfio_notify_type_t type,
>> +			   unsigned long *events,
>> +			   struct notifier_block *nb)
>> +{
>> +	struct vfio_group *group;
>> +	int ret;
>> +
>> +	if (!dev || !nb)
>> +		return -EINVAL;
>> +	if (!events || *events == 0)
>> +		return -EINVAL;
> 
> nit, we could test all these within a single if()
> 

Will do that in next version.

>> +
>> +	group = vfio_group_get_from_dev(dev);
>> +	if (IS_ERR(group))
>> +		return PTR_ERR(group);
>> +
>> +	switch (type) {
>> +	case VFIO_IOMMU_NOTIFY:
>> +		ret = vfio_register_iommu_notifier(group, events, nb);
>> +		break;
>> +	default:
>> +		ret = EINVAL;
> 
> -EINVAL
> ^
> 

Ough, sorry .. will fix it in next version.

--
Thanks,
Jike
>> +	}
>> +
>> +	vfio_group_put(group);
>> +	return ret;
>> +}
>> +EXPORT_SYMBOL(vfio_register_notifier);
>> +
>> +int vfio_unregister_notifier(struct device *dev, vfio_notify_type_t type,
>> +			     struct notifier_block *nb)
>> +{
>> +	struct vfio_group *group;
>> +	int ret;
>> +
>> +	if (!dev || !nb)
>> +		return -EINVAL;
>> +
>> +	group = vfio_group_get_from_dev(dev);
>> +	if (IS_ERR(group))
>> +		return PTR_ERR(group);
>> +
>> +	switch (type) {
>> +	case VFIO_IOMMU_NOTIFY:
>> +		ret = vfio_unregister_iommu_notifier(group, nb);
>> +		break;
>> +	default:
>> +		ret = -EINVAL;
>> +	}
>> +
>>  	vfio_group_put(group);
>>  	return ret;
>>  }
>> diff --git a/include/linux/vfio.h b/include/linux/vfio.h
>> index 15ff042..6f3ff31 100644
>> --- a/include/linux/vfio.h
>> +++ b/include/linux/vfio.h
>> @@ -107,14 +107,24 @@ extern int vfio_pin_pages(struct device *dev, unsigned long *user_pfn,
>>  extern int vfio_unpin_pages(struct device *dev, unsigned long *user_pfn,
>>  			    int npage);
>>  
>> -#define VFIO_IOMMU_NOTIFY_DMA_UNMAP	(1)
>> -
>> +typedef unsigned short vfio_notify_type_t;
>>  extern int vfio_register_notifier(struct device *dev,
>> +				  vfio_notify_type_t type,
>> +				  unsigned long *required_events,
>>  				  struct notifier_block *nb);
>> -
>>  extern int vfio_unregister_notifier(struct device *dev,
>> +				    vfio_notify_type_t type,
>>  				    struct notifier_block *nb);
>>  
>> +/* each type has independent events */
>> +enum vfio_notify_type {
>> +	VFIO_IOMMU_NOTIFY = (__force vfio_notify_type_t)0,
>> +};
>> +
>> +/* events for VFIO_IOMMU_NOTIFY */
>> +#define VFIO_IOMMU_NOTIFY_DMA_UNMAP	BIT(0)
>> +
>> +
>>  /*
>>   * Sub-module helpers
>>   */
> 

  reply	other threads:[~2016-11-19  3:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18 11:01 [v6 0/3] plumb kvm/vfio to notify kvm:group attach/detach Jike Song
2016-11-18 11:01 ` [v6 1/3] vfio: vfio_register_notifier: classify iommu notifier Jike Song
2016-11-18 17:55   ` Alex Williamson
2016-11-19  3:32     ` Jike Song [this message]
2016-11-18 11:01 ` [v6 2/3] vfio: support notifier chain in vfio_group Jike Song
2016-11-18 17:55   ` Alex Williamson
2016-11-19  4:14     ` Jike Song
2016-11-21 16:56       ` Alex Williamson
2016-11-22  6:21         ` Jike Song
2016-11-18 11:01 ` [v6 3/3] kvm: set/clear kvm to/from vfio_group when group add/delete Jike Song

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=582FC7CF.305@intel.com \
    --to=jike.song@intel.com \
    --cc=alex.williamson@redhat.com \
    --cc=cjia@nvidia.com \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=pbonzini@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).