All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Yi Liu <yi.l.liu@intel.com>
Cc: alex.williamson@redhat.com, kevin.tian@intel.com,
	cohuck@redhat.com, eric.auger@redhat.com, nicolinc@nvidia.com,
	kvm@vger.kernel.org, mjrosato@linux.ibm.com,
	chao.p.peng@linux.intel.com, yi.y.sun@linux.intel.com,
	peterx@redhat.com, jasowang@redhat.com,
	suravee.suthikulpanit@amd.com,
	Joao Martins <joao.m.martins@oracle.com>
Subject: Re: [PATCH 11/13] vfio: Add cdev for vfio_device
Date: Tue, 24 Jan 2023 16:44:40 -0400	[thread overview]
Message-ID: <Y9BDOCA7qlbuIMMg@nvidia.com> (raw)
In-Reply-To: <20230117134942.101112-12-yi.l.liu@intel.com>

On Tue, Jan 17, 2023 at 05:49:40AM -0800, Yi Liu wrote:
> This allows user to directly open a vfio device w/o using the legacy
> container/group interface, as a prerequisite for supporting new iommu
> features like nested translation.
> 
> The device fd opened in this manner doesn't have the capability to access
> the device as the fops open() doesn't open the device until the successful
> BIND_IOMMUFD which be added in next patch.
> 
> With this patch, devices registered to vfio core have both group and device
> interface created.
> 
> - group interface : /dev/vfio/$groupID
> - device interface: /dev/vfio/devices/vfioX  (X is the minor number and
> 					      is unique across devices)
> 
> Given a vfio device the user can identify the matching vfioX by checking
> the sysfs path of the device. Take PCI device (0000:6a:01.0) for example,
> /sys/bus/pci/devices/0000\:6a\:01.0/vfio-dev/vfio0/dev contains the
> major:minor of the matching vfioX.
> 
> Userspace then opens the /dev/vfio/devices/vfioX and checks with fstat
> that the major:minor matches.
> 
> The vfio_device cdev logic in this patch:
> *) __vfio_register_dev() path ends up doing cdev_device_add() for each
>    vfio_device;
> *) vfio_unregister_group_dev() path does cdev_device_del();
> 
> Signed-off-by: Yi Liu <yi.l.liu@intel.com>
> Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
> ---
>  drivers/vfio/vfio_main.c | 103 ++++++++++++++++++++++++++++++++++++---
>  include/linux/vfio.h     |   7 ++-
>  2 files changed, 102 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/vfio/vfio_main.c b/drivers/vfio/vfio_main.c
> index 78725c28b933..6068ffb7c6b7 100644
> --- a/drivers/vfio/vfio_main.c
> +++ b/drivers/vfio/vfio_main.c
> @@ -43,6 +43,9 @@
>  static struct vfio {
>  	struct class			*device_class;
>  	struct ida			device_ida;
> +#if IS_ENABLED(CONFIG_IOMMUFD)
> +	dev_t                           device_devt;
> +#endif

It is a bit strange to see this called CONFIG_IOMMUFD, maybe we should
have a CONFIG_VFIO_DEVICE_FILE that depends on IOMMUFD?

Please try to use a plain 'if (IS_ENABLED())' for more of these

It probably isn't worth saving a few bytes in memory to complicate all
the code, so maybe just always include things like this.

> @@ -156,7 +159,11 @@ static void vfio_device_release(struct device *dev)
>  			container_of(dev, struct vfio_device, device);
>  
>  	vfio_release_device_set(device);
> +#if IS_ENABLED(CONFIG_IOMMUFD)
> +	ida_free(&vfio.device_ida, MINOR(device->device.devt));
> +#else
>  	ida_free(&vfio.device_ida, device->index);
> +#endif

A vfio_device_get_index() would help this

Jason

  parent reply	other threads:[~2023-01-24 20:44 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 13:49 [PATCH 00/13] Add vfio_device cdev for iommufd support Yi Liu
2023-01-17 13:49 ` [PATCH 01/13] vfio: Allocate per device file structure Yi Liu
2023-01-18  8:37   ` Tian, Kevin
2023-01-18 13:28   ` Eric Auger
2023-01-17 13:49 ` [PATCH 02/13] vfio: Refine vfio file kAPIs Yi Liu
2023-01-18  8:42   ` Tian, Kevin
2023-01-18 14:37   ` Eric Auger
2023-01-29 13:32     ` Liu, Yi L
2023-01-17 13:49 ` [PATCH 03/13] vfio: Accept vfio device file in the driver facing kAPI Yi Liu
2023-01-18  8:45   ` Tian, Kevin
2023-01-18 16:11   ` Eric Auger
2023-01-30  9:47     ` Liu, Yi L
2023-01-30 18:02       ` Jason Gunthorpe
2023-01-17 13:49 ` [PATCH 04/13] kvm/vfio: Rename kvm_vfio_group to prepare for accepting vfio device fd Yi Liu
2023-01-18  8:47   ` Tian, Kevin
2023-01-18 16:33   ` Eric Auger
2023-01-17 13:49 ` [PATCH 05/13] kvm/vfio: Provide struct kvm_device_ops::release() insted of ::destroy() Yi Liu
2023-01-18  8:56   ` Tian, Kevin
2023-01-19  9:12   ` Eric Auger
2023-01-19  9:30     ` Tian, Kevin
2023-01-20  3:52       ` Liu, Yi L
2023-01-19 19:07   ` Jason Gunthorpe
2023-01-19 20:04     ` Alex Williamson
2023-01-20 13:03     ` Liu, Yi L
2023-01-20 14:00     ` Liu, Yi L
2023-01-20 14:33       ` Jason Gunthorpe
2023-01-20 15:09         ` Liu, Yi L
2023-01-20 15:11           ` Liu, Yi L
2023-01-17 13:49 ` [PATCH 06/13] kvm/vfio: Accept vfio device file from userspace Yi Liu
2023-01-18  9:18   ` Tian, Kevin
2023-01-19  9:35   ` Eric Auger
2023-01-30  7:36     ` Liu, Yi L
2023-01-17 13:49 ` [PATCH 07/13] vfio: Pass struct vfio_device_file * to vfio_device_open/close() Yi Liu
2023-01-18  9:27   ` Tian, Kevin
2023-01-19 11:01   ` Eric Auger
2023-01-19 20:35     ` Alex Williamson
2023-01-30  9:38       ` Liu, Yi L
2023-01-30  9:38     ` Liu, Yi L
2023-01-17 13:49 ` [PATCH 08/13] vfio: Block device access via device fd until device is opened Yi Liu
2023-01-18  9:35   ` Tian, Kevin
2023-01-18 13:52     ` Jason Gunthorpe
2023-01-19  3:42       ` Tian, Kevin
2023-01-19  3:43         ` Liu, Yi L
2023-01-19 14:00   ` Eric Auger
2023-01-30 10:41     ` Liu, Yi L
2023-01-19 20:47   ` Alex Williamson
2023-01-30 10:48     ` Liu, Yi L
2023-01-17 13:49 ` [PATCH 09/13] vfio: Add infrastructure for bind_iommufd and attach Yi Liu
2023-01-19  9:45   ` Tian, Kevin
2023-01-30 13:52     ` Liu, Yi L
2023-01-19 23:05   ` Alex Williamson
2023-01-30 13:55     ` Liu, Yi L
2023-01-17 13:49 ` [PATCH 10/13] vfio: Make vfio_device_open() exclusive between group path and device cdev path Yi Liu
2023-01-19  9:55   ` Tian, Kevin
2023-01-30 11:59     ` Liu, Yi L
2023-01-19 23:51   ` Alex Williamson
2023-01-30 12:14     ` Liu, Yi L
2023-02-02  5:34       ` Liu, Yi L
2023-02-03 17:41         ` Jason Gunthorpe
2023-02-06  4:30           ` Liu, Yi L
2023-02-06 10:09             ` Tian, Kevin
2023-02-06 15:10               ` Jason Gunthorpe
2023-02-06 15:51                 ` Liu, Yi L
2023-02-07  0:35                   ` Tian, Kevin
2023-02-07 13:12                     ` Jason Gunthorpe
2023-02-07 13:19                       ` Liu, Yi L
2023-02-07 13:20                         ` Jason Gunthorpe
2023-02-07 13:23                           ` Liu, Yi L
2023-02-07 13:27                             ` Jason Gunthorpe
2023-02-07 13:55                               ` Liu, Yi L
2023-02-08  4:23                               ` Tian, Kevin
2023-02-08 12:41                                 ` Jason Gunthorpe
2023-01-17 13:49 ` [PATCH 11/13] vfio: Add cdev for vfio_device Yi Liu
2023-01-20  7:26   ` Tian, Kevin
2023-01-31  6:17     ` Liu, Yi L
2023-01-24 20:44   ` Jason Gunthorpe [this message]
2023-01-17 13:49 ` [PATCH 12/13] vfio: Add ioctls for device cdev iommufd Yi Liu
2023-01-20  8:03   ` Tian, Kevin
2023-02-06  9:07     ` Liu, Yi L
2023-01-17 13:49 ` [PATCH 13/13] vfio: Compile group optionally Yi Liu

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=Y9BDOCA7qlbuIMMg@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=alex.williamson@redhat.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=cohuck@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=joao.m.martins@oracle.com \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=mjrosato@linux.ibm.com \
    --cc=nicolinc@nvidia.com \
    --cc=peterx@redhat.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=yi.l.liu@intel.com \
    --cc=yi.y.sun@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.