From: Jason Gunthorpe <jgg@nvidia.com>
To: "Liu, Yi L" <yi.l.liu@intel.com>
Cc: "mjrosato@linux.ibm.com" <mjrosato@linux.ibm.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"Hao, Xudong" <xudong.hao@intel.com>,
"peterx@redhat.com" <peterx@redhat.com>,
"Xu, Terrence" <terrence.xu@intel.com>,
"chao.p.peng@linux.intel.com" <chao.p.peng@linux.intel.com>,
"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"lulu@redhat.com" <lulu@redhat.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"nicolinc@nvidia.com" <nicolinc@nvidia.com>,
"Zhao, Yan Y" <yan.y.zhao@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"eric.auger@redhat.com" <eric.auger@redhat.com>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
"yi.y.sun@linux.intel.com" <yi.y.sun@linux.intel.com>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"shameerali.kolothum.thodi@huawei.com"
<shameerali.kolothum.thodi@huawei.com>,
"suravee.suthikulpanit@amd.com" <suravee.suthikulpanit@amd.com>,
"robin.murphy@arm.com" <robin.murphy@arm.com>
Subject: Re: [Intel-gfx] [PATCH v5 17/19] vfio: Add VFIO_DEVICE_AT[DE]TACH_IOMMUFD_PT
Date: Wed, 1 Mar 2023 13:49:23 -0400 [thread overview]
Message-ID: <Y/+QIz3VT7iD0jZ5@nvidia.com> (raw)
In-Reply-To: <DS0PR11MB7529E456C277723146A09E2FC3AD9@DS0PR11MB7529.namprd11.prod.outlook.com>
On Wed, Mar 01, 2023 at 02:04:00PM +0000, Liu, Yi L wrote:
> diff --git a/drivers/vfio/group.c b/drivers/vfio/group.c
> index 2a13442add43..ed3ffe7ceb3f 100644
> --- a/drivers/vfio/group.c
> +++ b/drivers/vfio/group.c
> @@ -777,6 +777,11 @@ void vfio_device_group_unregister(struct vfio_device *device)
> mutex_unlock(&device->group->device_lock);
> }
>
> +bool vfio_device_group_uses_container(struct vfio_device *device)
> +{
> + return READ_ONCE(device->group->container);
> +}
As I said this should take in the vfio_device_file because as long as
a vfio_device_file exists then group->contianer is required to be stable.
> diff --git a/drivers/vfio/vfio_main.c b/drivers/vfio/vfio_main.c
> index 121a75fadceb..4b5b17e8aaa1 100644
> --- a/drivers/vfio/vfio_main.c
> +++ b/drivers/vfio/vfio_main.c
> @@ -422,9 +422,22 @@ static int vfio_device_first_open(struct vfio_device_file *df)
> if (!try_module_get(device->dev->driver->owner))
> return -ENODEV;
>
> + /*
> + * The handling here depends on what the user is using.
> + *
> + * If user uses iommufd in the group compat mode or the
> + * cdev path, call vfio_iommufd_bind().
> + *
> + * If user uses container in the group legacy mode, call
> + * vfio_device_group_use_iommu().
> + *
> + * If user doesn't use iommufd nor container, this is
> + * the noiommufd mode in the cdev path, nothing needs
> + * to be done here just go ahead to open device.
> + */
> if (iommufd)
> ret = vfio_iommufd_bind(device, iommufd);
> - else
> + else if (vfio_device_group_uses_container(device))
> ret = vfio_device_group_use_iommu(device);
But yes, this makes alot more sense..
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: "Liu, Yi L" <yi.l.liu@intel.com>
Cc: "alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"eric.auger@redhat.com" <eric.auger@redhat.com>,
"nicolinc@nvidia.com" <nicolinc@nvidia.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"mjrosato@linux.ibm.com" <mjrosato@linux.ibm.com>,
"chao.p.peng@linux.intel.com" <chao.p.peng@linux.intel.com>,
"yi.y.sun@linux.intel.com" <yi.y.sun@linux.intel.com>,
"peterx@redhat.com" <peterx@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"shameerali.kolothum.thodi@huawei.com"
<shameerali.kolothum.thodi@huawei.com>,
"lulu@redhat.com" <lulu@redhat.com>,
"suravee.suthikulpanit@amd.com" <suravee.suthikulpanit@amd.com>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
"Hao, Xudong" <xudong.hao@intel.com>,
"Zhao, Yan Y" <yan.y.zhao@intel.com>,
"Xu, Terrence" <terrence.xu@intel.com>
Subject: Re: [PATCH v5 17/19] vfio: Add VFIO_DEVICE_AT[DE]TACH_IOMMUFD_PT
Date: Wed, 1 Mar 2023 13:49:23 -0400 [thread overview]
Message-ID: <Y/+QIz3VT7iD0jZ5@nvidia.com> (raw)
In-Reply-To: <DS0PR11MB7529E456C277723146A09E2FC3AD9@DS0PR11MB7529.namprd11.prod.outlook.com>
On Wed, Mar 01, 2023 at 02:04:00PM +0000, Liu, Yi L wrote:
> diff --git a/drivers/vfio/group.c b/drivers/vfio/group.c
> index 2a13442add43..ed3ffe7ceb3f 100644
> --- a/drivers/vfio/group.c
> +++ b/drivers/vfio/group.c
> @@ -777,6 +777,11 @@ void vfio_device_group_unregister(struct vfio_device *device)
> mutex_unlock(&device->group->device_lock);
> }
>
> +bool vfio_device_group_uses_container(struct vfio_device *device)
> +{
> + return READ_ONCE(device->group->container);
> +}
As I said this should take in the vfio_device_file because as long as
a vfio_device_file exists then group->contianer is required to be stable.
> diff --git a/drivers/vfio/vfio_main.c b/drivers/vfio/vfio_main.c
> index 121a75fadceb..4b5b17e8aaa1 100644
> --- a/drivers/vfio/vfio_main.c
> +++ b/drivers/vfio/vfio_main.c
> @@ -422,9 +422,22 @@ static int vfio_device_first_open(struct vfio_device_file *df)
> if (!try_module_get(device->dev->driver->owner))
> return -ENODEV;
>
> + /*
> + * The handling here depends on what the user is using.
> + *
> + * If user uses iommufd in the group compat mode or the
> + * cdev path, call vfio_iommufd_bind().
> + *
> + * If user uses container in the group legacy mode, call
> + * vfio_device_group_use_iommu().
> + *
> + * If user doesn't use iommufd nor container, this is
> + * the noiommufd mode in the cdev path, nothing needs
> + * to be done here just go ahead to open device.
> + */
> if (iommufd)
> ret = vfio_iommufd_bind(device, iommufd);
> - else
> + else if (vfio_device_group_uses_container(device))
> ret = vfio_device_group_use_iommu(device);
But yes, this makes alot more sense..
Jason
next prev parent reply other threads:[~2023-03-01 17:49 UTC|newest]
Thread overview: 259+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 11:11 [Intel-gfx] [PATCH v5 00/19] Add vfio_device cdev for iommufd support Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 11:11 ` [Intel-gfx] [PATCH v5 01/19] vfio: Allocate per device file structure Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 18:46 ` [Intel-gfx] " Jason Gunthorpe
2023-02-27 18:46 ` Jason Gunthorpe
2023-02-27 11:11 ` [Intel-gfx] [PATCH v5 02/19] vfio: Refine vfio file kAPIs for KVM Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 18:46 ` [Intel-gfx] " Jason Gunthorpe
2023-02-27 18:46 ` Jason Gunthorpe
2023-02-27 11:11 ` [Intel-gfx] [PATCH v5 03/19] vfio: Accept vfio device file in the KVM facing kAPI Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 18:46 ` [Intel-gfx] " Jason Gunthorpe
2023-02-27 18:46 ` Jason Gunthorpe
2023-02-27 11:11 ` [Intel-gfx] [PATCH v5 04/19] kvm/vfio: Rename kvm_vfio_group to prepare for accepting vfio device fd Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 18:47 ` [Intel-gfx] " Jason Gunthorpe
2023-02-27 18:47 ` Jason Gunthorpe
2023-02-27 11:11 ` [Intel-gfx] [PATCH v5 05/19] kvm/vfio: Accept vfio device file from userspace Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 18:47 ` [Intel-gfx] " Jason Gunthorpe
2023-02-27 18:47 ` Jason Gunthorpe
2023-02-27 11:11 ` [Intel-gfx] [PATCH v5 06/19] vfio: Pass struct vfio_device_file * to vfio_device_open/close() Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 18:47 ` [Intel-gfx] " Jason Gunthorpe
2023-02-27 18:47 ` Jason Gunthorpe
2023-02-27 11:11 ` [Intel-gfx] [PATCH v5 07/19] vfio: Block device access via device fd until device is opened Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 18:48 ` [Intel-gfx] " Jason Gunthorpe
2023-02-27 18:48 ` Jason Gunthorpe
2023-03-01 9:22 ` [Intel-gfx] " Liu, Yi L
2023-03-01 9:22 ` Liu, Yi L
2023-02-27 11:11 ` [Intel-gfx] [PATCH v5 08/19] vfio/pci: Update comment around group_fd get in vfio_pci_ioctl_pci_hot_reset() Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 18:48 ` [Intel-gfx] " Jason Gunthorpe
2023-02-27 18:48 ` Jason Gunthorpe
2023-02-27 11:11 ` [Intel-gfx] [PATCH v5 09/19] vfio/pci: Allow passing zero-length fd array in VFIO_DEVICE_PCI_HOT_RESET Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 18:22 ` [Intel-gfx] " Jason Gunthorpe
2023-02-27 18:22 ` Jason Gunthorpe
2023-02-28 2:31 ` [Intel-gfx] " Liu, Yi L
2023-02-28 2:31 ` Liu, Yi L
2023-03-02 6:07 ` [Intel-gfx] " Liu, Yi L
2023-03-02 6:07 ` Liu, Yi L
2023-03-02 9:55 ` [Intel-gfx] " Tian, Kevin
2023-03-02 9:55 ` Tian, Kevin
2023-03-02 12:35 ` [Intel-gfx] " Jason Gunthorpe
2023-03-02 12:35 ` Jason Gunthorpe
2023-03-02 14:20 ` [Intel-gfx] " Liu, Yi L
2023-03-02 14:20 ` Liu, Yi L
2023-03-03 6:36 ` [Intel-gfx] " Tian, Kevin
2023-03-03 6:36 ` Tian, Kevin
2023-03-03 16:55 ` [Intel-gfx] " Alex Williamson
2023-03-03 16:55 ` Alex Williamson
2023-03-05 14:48 ` [Intel-gfx] " Liu, Yi L
2023-03-05 14:48 ` Liu, Yi L
2023-03-06 8:16 ` [Intel-gfx] " Tian, Kevin
2023-03-06 8:16 ` Tian, Kevin
2023-03-06 8:23 ` [Intel-gfx] " Tian, Kevin
2023-03-06 8:23 ` Tian, Kevin
2023-03-06 8:33 ` [Intel-gfx] " Liu, Yi L
2023-03-06 8:33 ` Liu, Yi L
2023-03-06 9:59 ` [Intel-gfx] " Liu, Yi L
2023-03-06 9:59 ` Liu, Yi L
2023-03-06 13:16 ` [Intel-gfx] " Jason Gunthorpe
2023-03-06 13:16 ` Jason Gunthorpe
2023-03-07 2:31 ` [Intel-gfx] " Tian, Kevin
2023-03-07 2:31 ` Tian, Kevin
2023-03-07 2:35 ` [Intel-gfx] " Liu, Yi L
2023-03-07 2:35 ` Liu, Yi L
2023-03-07 12:36 ` [Intel-gfx] " Jason Gunthorpe
2023-03-07 12:36 ` Jason Gunthorpe
2023-03-07 13:28 ` [Intel-gfx] " Liu, Yi L
2023-03-07 13:28 ` Liu, Yi L
2023-03-08 7:26 ` [Intel-gfx] " Tian, Kevin
2023-03-08 7:26 ` Tian, Kevin
2023-03-08 7:47 ` [Intel-gfx] " Liu, Yi L
2023-03-08 7:47 ` Liu, Yi L
2023-03-08 7:55 ` [Intel-gfx] " Tian, Kevin
2023-03-08 7:55 ` Tian, Kevin
2023-03-08 8:00 ` [Intel-gfx] " Liu, Yi L
2023-03-08 8:00 ` Liu, Yi L
2023-03-08 8:14 ` [Intel-gfx] " Tian, Kevin
2023-03-08 8:14 ` Tian, Kevin
2023-03-08 8:15 ` [Intel-gfx] " Liu, Yi L
2023-03-08 8:15 ` Liu, Yi L
2023-03-08 15:08 ` [Intel-gfx] " Jason Gunthorpe
2023-03-08 15:08 ` Jason Gunthorpe
2023-03-02 21:04 ` [Intel-gfx] " Alex Williamson
2023-03-02 21:04 ` Alex Williamson
2023-02-27 11:11 ` [Intel-gfx] [PATCH v5 10/19] vfio: Add infrastructure for bind_iommufd from userspace Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 18:29 ` [Intel-gfx] " Jason Gunthorpe
2023-02-27 18:29 ` Jason Gunthorpe
2023-02-28 2:35 ` [Intel-gfx] " Liu, Yi L
2023-02-28 2:35 ` Liu, Yi L
2023-02-28 6:58 ` [Intel-gfx] " Liu, Yi L
2023-02-28 6:58 ` Liu, Yi L
2023-02-28 12:31 ` [Intel-gfx] " Jason Gunthorpe
2023-02-28 12:31 ` Jason Gunthorpe
2023-02-28 12:45 ` [Intel-gfx] " Liu, Yi L
2023-02-28 12:45 ` Liu, Yi L
2023-02-28 12:52 ` [Intel-gfx] " Jason Gunthorpe
2023-02-28 12:52 ` Jason Gunthorpe
2023-02-28 12:56 ` [Intel-gfx] " Liu, Yi L
2023-02-28 12:56 ` Liu, Yi L
2023-02-28 12:58 ` [Intel-gfx] " Jason Gunthorpe
2023-02-28 12:58 ` Jason Gunthorpe
2023-02-28 12:29 ` [Intel-gfx] " Jason Gunthorpe
2023-02-28 12:29 ` Jason Gunthorpe
2023-02-28 12:48 ` [Intel-gfx] " Liu, Yi L
2023-02-28 12:48 ` Liu, Yi L
2023-02-28 12:52 ` [Intel-gfx] " Jason Gunthorpe
2023-02-28 12:52 ` Jason Gunthorpe
2023-02-28 13:24 ` [Intel-gfx] " Liu, Yi L
2023-02-28 13:24 ` Liu, Yi L
2023-02-27 11:11 ` [Intel-gfx] [PATCH v5 11/19] vfio-iommufd: Add detach_ioas support for physical VFIO devices Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 18:44 ` [Intel-gfx] " Jason Gunthorpe
2023-02-27 18:44 ` Jason Gunthorpe
2023-02-28 2:57 ` [Intel-gfx] " Liu, Yi L
2023-02-28 2:57 ` Liu, Yi L
2023-02-28 12:33 ` [Intel-gfx] " Jason Gunthorpe
2023-02-28 12:33 ` Jason Gunthorpe
2023-02-28 12:43 ` [Intel-gfx] " Liu, Yi L
2023-02-28 12:43 ` Liu, Yi L
2023-02-27 11:11 ` [Intel-gfx] [PATCH v5 12/19] vfio-iommufd: Add detach_ioas for emulated " Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 18:45 ` [Intel-gfx] " Jason Gunthorpe
2023-02-27 18:45 ` Jason Gunthorpe
2023-02-27 11:11 ` [Intel-gfx] [PATCH v5 13/19] vfio: Add cdev_device_open_cnt to vfio_group Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 19:20 ` [Intel-gfx] " Jason Gunthorpe
2023-02-27 19:20 ` Jason Gunthorpe
2023-02-27 11:11 ` [Intel-gfx] [PATCH v5 14/19] vfio: Make vfio_device_open() single open for device cdev path Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 18:52 ` [Intel-gfx] " Jason Gunthorpe
2023-02-27 18:52 ` Jason Gunthorpe
2023-02-28 3:11 ` [Intel-gfx] " Liu, Yi L
2023-02-28 3:11 ` Liu, Yi L
2023-02-28 12:33 ` [Intel-gfx] " Jason Gunthorpe
2023-02-28 12:33 ` Jason Gunthorpe
2023-03-01 13:58 ` [Intel-gfx] " Liu, Yi L
2023-03-01 13:58 ` Liu, Yi L
2023-02-27 11:11 ` [Intel-gfx] [PATCH v5 15/19] vfio: Add cdev for vfio_device Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 18:55 ` [Intel-gfx] " Jason Gunthorpe
2023-02-27 18:55 ` Jason Gunthorpe
2023-02-28 3:47 ` [Intel-gfx] " Liu, Yi L
2023-02-28 3:47 ` Liu, Yi L
2023-02-27 19:06 ` [Intel-gfx] " Jason Gunthorpe
2023-02-27 19:06 ` Jason Gunthorpe
2023-02-28 3:59 ` [Intel-gfx] " Liu, Yi L
2023-02-28 3:59 ` Liu, Yi L
2023-02-27 11:11 ` [Intel-gfx] [PATCH v5 16/19] vfio: Add VFIO_DEVICE_BIND_IOMMUFD Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 19:19 ` [Intel-gfx] " Jason Gunthorpe
2023-02-27 19:19 ` Jason Gunthorpe
2023-02-28 4:08 ` [Intel-gfx] " Liu, Yi L
2023-02-28 4:08 ` Liu, Yi L
2023-03-01 9:19 ` [Intel-gfx] " Liu, Yi L
2023-03-01 9:19 ` Liu, Yi L
2023-03-01 17:46 ` [Intel-gfx] " Jason Gunthorpe
2023-03-01 17:46 ` Jason Gunthorpe
2023-03-02 4:09 ` [Intel-gfx] " Liu, Yi L
2023-03-02 4:09 ` Liu, Yi L
2023-03-03 6:57 ` [Intel-gfx] " Liu, Yi L
2023-03-03 6:57 ` Liu, Yi L
2023-03-03 7:23 ` [Intel-gfx] " Liu, Yi L
2023-03-03 7:23 ` Liu, Yi L
2023-03-07 6:38 ` [Intel-gfx] " Tian, Kevin
2023-03-07 6:38 ` Tian, Kevin
2023-03-07 12:37 ` [Intel-gfx] " Jason Gunthorpe
2023-03-07 12:37 ` Jason Gunthorpe
2023-03-07 13:03 ` [Intel-gfx] " Liu, Yi L
2023-03-07 13:03 ` Liu, Yi L
2023-03-08 7:17 ` [Intel-gfx] " Tian, Kevin
2023-03-08 7:17 ` Tian, Kevin
2023-03-10 2:39 ` [Intel-gfx] " Alexey Kardashevskiy
2023-03-10 2:39 ` Alexey Kardashevskiy
2023-03-10 5:49 ` [Intel-gfx] " Liu, Yi L
2023-03-10 5:49 ` Liu, Yi L
2023-02-27 11:11 ` [Intel-gfx] [PATCH v5 17/19] vfio: Add VFIO_DEVICE_AT[DE]TACH_IOMMUFD_PT Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 18:39 ` [Intel-gfx] " Jason Gunthorpe
2023-02-27 18:39 ` Jason Gunthorpe
2023-02-28 2:51 ` [Intel-gfx] " Liu, Yi L
2023-02-28 2:51 ` Liu, Yi L
2023-02-28 12:32 ` [Intel-gfx] " Jason Gunthorpe
2023-02-28 12:32 ` Jason Gunthorpe
2023-02-28 12:42 ` [Intel-gfx] " Liu, Yi L
2023-02-28 12:42 ` Liu, Yi L
2023-02-28 12:53 ` [Intel-gfx] " Jason Gunthorpe
2023-02-28 12:53 ` Jason Gunthorpe
2023-02-28 13:22 ` [Intel-gfx] " Liu, Yi L
2023-02-28 13:22 ` Liu, Yi L
2023-02-28 13:25 ` [Intel-gfx] " Jason Gunthorpe
2023-02-28 13:25 ` Jason Gunthorpe
2023-02-28 13:36 ` [Intel-gfx] " Liu, Yi L
2023-02-28 13:36 ` Liu, Yi L
2023-02-28 13:43 ` [Intel-gfx] " Jason Gunthorpe
2023-02-28 13:43 ` Jason Gunthorpe
2023-02-28 14:01 ` [Intel-gfx] " Liu, Yi L
2023-02-28 14:01 ` Liu, Yi L
2023-02-28 14:38 ` [Intel-gfx] " Jason Gunthorpe
2023-02-28 14:38 ` Jason Gunthorpe
2023-03-01 14:04 ` [Intel-gfx] " Liu, Yi L
2023-03-01 14:04 ` Liu, Yi L
2023-03-01 17:49 ` Jason Gunthorpe [this message]
2023-03-01 17:49 ` Jason Gunthorpe
2023-03-02 3:24 ` [Intel-gfx] " Liu, Yi L
2023-03-02 3:24 ` Liu, Yi L
2023-02-27 11:11 ` [Intel-gfx] [PATCH v5 18/19] vfio: Compile group optionally Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 19:20 ` [Intel-gfx] " Jason Gunthorpe
2023-02-27 19:20 ` Jason Gunthorpe
2023-02-28 3:14 ` [Intel-gfx] " Liu, Yi L
2023-02-28 3:14 ` Liu, Yi L
2023-02-28 6:00 ` [Intel-gfx] " Liu, Yi L
2023-02-28 6:00 ` Liu, Yi L
2023-02-28 12:36 ` [Intel-gfx] " Jason Gunthorpe
2023-02-28 12:36 ` Jason Gunthorpe
2023-03-01 13:59 ` [Intel-gfx] " Liu, Yi L
2023-03-01 13:59 ` Liu, Yi L
2023-02-27 11:11 ` [Intel-gfx] [PATCH v5 19/19] docs: vfio: Add vfio device cdev description Yi Liu
2023-02-27 11:11 ` Yi Liu
2023-02-27 11:31 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Add vfio_device cdev for iommufd support (rev5) Patchwork
2023-02-27 19:21 ` [Intel-gfx] [PATCH v5 00/19] Add vfio_device cdev for iommufd support Jason Gunthorpe
2023-02-27 19:21 ` Jason Gunthorpe
2023-02-28 3:03 ` [Intel-gfx] " Liu, Yi L
2023-02-28 3:03 ` Liu, Yi L
2023-02-28 16:58 ` [Intel-gfx] " Xu, Terrence
2023-02-28 16:58 ` Xu, Terrence
2023-03-01 2:29 ` [Intel-gfx] " Nicolin Chen
2023-03-01 2:29 ` Nicolin Chen
2023-03-01 3:44 ` [Intel-gfx] " Liu, Yi L
2023-03-01 3:44 ` Liu, Yi L
2023-03-02 9:43 ` [Intel-gfx] " Shameerali Kolothum Thodi
2023-03-02 9:43 ` Shameerali Kolothum Thodi
2023-03-02 23:51 ` [Intel-gfx] " Nicolin Chen
2023-03-02 23:51 ` Nicolin Chen
2023-03-03 15:01 ` [Intel-gfx] " Shameerali Kolothum Thodi
2023-03-03 15:01 ` Shameerali Kolothum Thodi
2023-03-04 7:00 ` [Intel-gfx] " Nicolin Chen
2023-03-04 7:00 ` Nicolin Chen
2023-03-04 8:22 ` [Intel-gfx] " Liu, Yi L
2023-03-04 8:22 ` Liu, Yi L
2023-03-08 15:54 ` [Intel-gfx] " Shameerali Kolothum Thodi
2023-03-08 15:54 ` Shameerali Kolothum Thodi
2023-03-14 11:38 ` [Intel-gfx] " Shameerali Kolothum Thodi
2023-03-14 11:38 ` Shameerali Kolothum Thodi
2023-03-15 23:22 ` [Intel-gfx] " Nicolin Chen
2023-03-15 23:22 ` Nicolin Chen
2023-03-16 7:39 ` [Intel-gfx] " Liu, Yi L
2023-03-16 7:39 ` Liu, Yi L
2023-03-03 21:29 ` [Intel-gfx] " Matthew Rosato
2023-03-03 21:29 ` Matthew Rosato
2023-03-01 21:01 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Add vfio_device cdev for iommufd support (rev6) Patchwork
2023-03-03 7:00 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Add vfio_device cdev for iommufd support (rev7) Patchwork
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=Y/+QIz3VT7iD0jZ5@nvidia.com \
--to=jgg@nvidia.com \
--cc=chao.p.peng@linux.intel.com \
--cc=cohuck@redhat.com \
--cc=eric.auger@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jasowang@redhat.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=mjrosato@linux.ibm.com \
--cc=nicolinc@nvidia.com \
--cc=peterx@redhat.com \
--cc=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=terrence.xu@intel.com \
--cc=xudong.hao@intel.com \
--cc=yan.y.zhao@intel.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.