All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yi Liu <yi.l.liu@intel.com>
To: alex.williamson@redhat.com, jgg@nvidia.com, kevin.tian@intel.com
Cc: joro@8bytes.org, robin.murphy@arm.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.l.liu@intel.com, yi.y.sun@linux.intel.com, peterx@redhat.com,
	jasowang@redhat.com, shameerali.kolothum.thodi@huawei.com,
	lulu@redhat.com, suravee.suthikulpanit@amd.com,
	intel-gvt-dev@lists.freedesktop.org,
	intel-gfx@lists.freedesktop.org, linux-s390@vger.kernel.org,
	xudong.hao@intel.com, yan.y.zhao@intel.com,
	terrence.xu@intel.com, yanting.jiang@intel.com,
	zhenzhong.duan@intel.com, clegoate@redhat.com
Subject: [PATCH v12 07/24] vfio: Block device access via device fd until device is opened
Date: Fri,  2 Jun 2023 05:16:36 -0700	[thread overview]
Message-ID: <20230602121653.80017-8-yi.l.liu@intel.com> (raw)
In-Reply-To: <20230602121653.80017-1-yi.l.liu@intel.com>

Allow the vfio_device file to be in a state where the device FD is
opened but the device cannot be used by userspace (i.e. its .open_device()
hasn't been called). This inbetween state is not used when the device
FD is spawned from the group FD, however when we create the device FD
directly by opening a cdev it will be opened in the blocked state.

The reason for the inbetween state is that userspace only gets a FD but
doesn't gain access permission until binding the FD to an iommufd. So in
the blocked state, only the bind operation is allowed. Completing bind
will allow user to further access the device.

This is implemented by adding a flag in struct vfio_device_file to mark
the blocked state and using a simple smp_load_acquire() to obtain the
flag value and serialize all the device setup with the thread accessing
this device.

Following this lockless scheme, it can safely handle the device FD
unbound->bound but it cannot handle bound->unbound. To allow this we'd
need to add a lock on all the vfio ioctls which seems costly. So once
device FD is bound, it remains bound until the FD is closed.

Suggested-by: Jason Gunthorpe <jgg@nvidia.com>
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Tested-by: Terrence Xu <terrence.xu@intel.com>
Tested-by: Nicolin Chen <nicolinc@nvidia.com>
Tested-by: Matthew Rosato <mjrosato@linux.ibm.com>
Tested-by: Yanting Jiang <yanting.jiang@intel.com>
Tested-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
Signed-off-by: Yi Liu <yi.l.liu@intel.com>
---
 drivers/vfio/group.c     | 11 ++++++++++-
 drivers/vfio/vfio.h      |  1 +
 drivers/vfio/vfio_main.c | 16 ++++++++++++++++
 3 files changed, 27 insertions(+), 1 deletion(-)

diff --git a/drivers/vfio/group.c b/drivers/vfio/group.c
index caf53716ddb2..088dd34c8931 100644
--- a/drivers/vfio/group.c
+++ b/drivers/vfio/group.c
@@ -194,9 +194,18 @@ static int vfio_df_group_open(struct vfio_device_file *df)
 	df->iommufd = device->group->iommufd;
 
 	ret = vfio_df_open(df);
-	if (ret)
+	if (ret) {
 		df->iommufd = NULL;
+		goto out_put_kvm;
+	}
+
+	/*
+	 * Paired with smp_load_acquire() in vfio_device_fops::ioctl/
+	 * read/write/mmap and vfio_file_has_device_access()
+	 */
+	smp_store_release(&df->access_granted, true);
 
+out_put_kvm:
 	if (device->open_count == 0)
 		vfio_device_put_kvm(device);
 
diff --git a/drivers/vfio/vfio.h b/drivers/vfio/vfio.h
index f9eb52eb9ed7..fdf2fc73f880 100644
--- a/drivers/vfio/vfio.h
+++ b/drivers/vfio/vfio.h
@@ -18,6 +18,7 @@ struct vfio_container;
 
 struct vfio_device_file {
 	struct vfio_device *device;
+	bool access_granted;
 	spinlock_t kvm_ref_lock; /* protect kvm field */
 	struct kvm *kvm;
 	struct iommufd_ctx *iommufd; /* protected by struct vfio_device_set::lock */
diff --git a/drivers/vfio/vfio_main.c b/drivers/vfio/vfio_main.c
index a3c5817fc545..4c8b7713dc3d 100644
--- a/drivers/vfio/vfio_main.c
+++ b/drivers/vfio/vfio_main.c
@@ -1129,6 +1129,10 @@ static long vfio_device_fops_unl_ioctl(struct file *filep,
 	struct vfio_device *device = df->device;
 	int ret;
 
+	/* Paired with smp_store_release() following vfio_df_open() */
+	if (!smp_load_acquire(&df->access_granted))
+		return -EINVAL;
+
 	ret = vfio_device_pm_runtime_get(device);
 	if (ret)
 		return ret;
@@ -1156,6 +1160,10 @@ static ssize_t vfio_device_fops_read(struct file *filep, char __user *buf,
 	struct vfio_device_file *df = filep->private_data;
 	struct vfio_device *device = df->device;
 
+	/* Paired with smp_store_release() following vfio_df_open() */
+	if (!smp_load_acquire(&df->access_granted))
+		return -EINVAL;
+
 	if (unlikely(!device->ops->read))
 		return -EINVAL;
 
@@ -1169,6 +1177,10 @@ static ssize_t vfio_device_fops_write(struct file *filep,
 	struct vfio_device_file *df = filep->private_data;
 	struct vfio_device *device = df->device;
 
+	/* Paired with smp_store_release() following vfio_df_open() */
+	if (!smp_load_acquire(&df->access_granted))
+		return -EINVAL;
+
 	if (unlikely(!device->ops->write))
 		return -EINVAL;
 
@@ -1180,6 +1192,10 @@ static int vfio_device_fops_mmap(struct file *filep, struct vm_area_struct *vma)
 	struct vfio_device_file *df = filep->private_data;
 	struct vfio_device *device = df->device;
 
+	/* Paired with smp_store_release() following vfio_df_open() */
+	if (!smp_load_acquire(&df->access_granted))
+		return -EINVAL;
+
 	if (unlikely(!device->ops->mmap))
 		return -EINVAL;
 
-- 
2.34.1


WARNING: multiple messages have this Message-ID (diff)
From: Yi Liu <yi.l.liu@intel.com>
To: alex.williamson@redhat.com, jgg@nvidia.com, kevin.tian@intel.com
Cc: mjrosato@linux.ibm.com, jasowang@redhat.com,
	xudong.hao@intel.com, zhenzhong.duan@intel.com,
	peterx@redhat.com, terrence.xu@intel.com,
	chao.p.peng@linux.intel.com, linux-s390@vger.kernel.org,
	yi.l.liu@intel.com, kvm@vger.kernel.org, lulu@redhat.com,
	yanting.jiang@intel.com, joro@8bytes.org, nicolinc@nvidia.com,
	yan.y.zhao@intel.com, intel-gfx@lists.freedesktop.org,
	eric.auger@redhat.com, intel-gvt-dev@lists.freedesktop.org,
	yi.y.sun@linux.intel.com, clegoate@redhat.com, cohuck@redhat.com,
	shameerali.kolothum.thodi@huawei.com,
	suravee.suthikulpanit@amd.com, robin.murphy@arm.com
Subject: [Intel-gfx] [PATCH v12 07/24] vfio: Block device access via device fd until device is opened
Date: Fri,  2 Jun 2023 05:16:36 -0700	[thread overview]
Message-ID: <20230602121653.80017-8-yi.l.liu@intel.com> (raw)
In-Reply-To: <20230602121653.80017-1-yi.l.liu@intel.com>

Allow the vfio_device file to be in a state where the device FD is
opened but the device cannot be used by userspace (i.e. its .open_device()
hasn't been called). This inbetween state is not used when the device
FD is spawned from the group FD, however when we create the device FD
directly by opening a cdev it will be opened in the blocked state.

The reason for the inbetween state is that userspace only gets a FD but
doesn't gain access permission until binding the FD to an iommufd. So in
the blocked state, only the bind operation is allowed. Completing bind
will allow user to further access the device.

This is implemented by adding a flag in struct vfio_device_file to mark
the blocked state and using a simple smp_load_acquire() to obtain the
flag value and serialize all the device setup with the thread accessing
this device.

Following this lockless scheme, it can safely handle the device FD
unbound->bound but it cannot handle bound->unbound. To allow this we'd
need to add a lock on all the vfio ioctls which seems costly. So once
device FD is bound, it remains bound until the FD is closed.

Suggested-by: Jason Gunthorpe <jgg@nvidia.com>
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Tested-by: Terrence Xu <terrence.xu@intel.com>
Tested-by: Nicolin Chen <nicolinc@nvidia.com>
Tested-by: Matthew Rosato <mjrosato@linux.ibm.com>
Tested-by: Yanting Jiang <yanting.jiang@intel.com>
Tested-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
Signed-off-by: Yi Liu <yi.l.liu@intel.com>
---
 drivers/vfio/group.c     | 11 ++++++++++-
 drivers/vfio/vfio.h      |  1 +
 drivers/vfio/vfio_main.c | 16 ++++++++++++++++
 3 files changed, 27 insertions(+), 1 deletion(-)

diff --git a/drivers/vfio/group.c b/drivers/vfio/group.c
index caf53716ddb2..088dd34c8931 100644
--- a/drivers/vfio/group.c
+++ b/drivers/vfio/group.c
@@ -194,9 +194,18 @@ static int vfio_df_group_open(struct vfio_device_file *df)
 	df->iommufd = device->group->iommufd;
 
 	ret = vfio_df_open(df);
-	if (ret)
+	if (ret) {
 		df->iommufd = NULL;
+		goto out_put_kvm;
+	}
+
+	/*
+	 * Paired with smp_load_acquire() in vfio_device_fops::ioctl/
+	 * read/write/mmap and vfio_file_has_device_access()
+	 */
+	smp_store_release(&df->access_granted, true);
 
+out_put_kvm:
 	if (device->open_count == 0)
 		vfio_device_put_kvm(device);
 
diff --git a/drivers/vfio/vfio.h b/drivers/vfio/vfio.h
index f9eb52eb9ed7..fdf2fc73f880 100644
--- a/drivers/vfio/vfio.h
+++ b/drivers/vfio/vfio.h
@@ -18,6 +18,7 @@ struct vfio_container;
 
 struct vfio_device_file {
 	struct vfio_device *device;
+	bool access_granted;
 	spinlock_t kvm_ref_lock; /* protect kvm field */
 	struct kvm *kvm;
 	struct iommufd_ctx *iommufd; /* protected by struct vfio_device_set::lock */
diff --git a/drivers/vfio/vfio_main.c b/drivers/vfio/vfio_main.c
index a3c5817fc545..4c8b7713dc3d 100644
--- a/drivers/vfio/vfio_main.c
+++ b/drivers/vfio/vfio_main.c
@@ -1129,6 +1129,10 @@ static long vfio_device_fops_unl_ioctl(struct file *filep,
 	struct vfio_device *device = df->device;
 	int ret;
 
+	/* Paired with smp_store_release() following vfio_df_open() */
+	if (!smp_load_acquire(&df->access_granted))
+		return -EINVAL;
+
 	ret = vfio_device_pm_runtime_get(device);
 	if (ret)
 		return ret;
@@ -1156,6 +1160,10 @@ static ssize_t vfio_device_fops_read(struct file *filep, char __user *buf,
 	struct vfio_device_file *df = filep->private_data;
 	struct vfio_device *device = df->device;
 
+	/* Paired with smp_store_release() following vfio_df_open() */
+	if (!smp_load_acquire(&df->access_granted))
+		return -EINVAL;
+
 	if (unlikely(!device->ops->read))
 		return -EINVAL;
 
@@ -1169,6 +1177,10 @@ static ssize_t vfio_device_fops_write(struct file *filep,
 	struct vfio_device_file *df = filep->private_data;
 	struct vfio_device *device = df->device;
 
+	/* Paired with smp_store_release() following vfio_df_open() */
+	if (!smp_load_acquire(&df->access_granted))
+		return -EINVAL;
+
 	if (unlikely(!device->ops->write))
 		return -EINVAL;
 
@@ -1180,6 +1192,10 @@ static int vfio_device_fops_mmap(struct file *filep, struct vm_area_struct *vma)
 	struct vfio_device_file *df = filep->private_data;
 	struct vfio_device *device = df->device;
 
+	/* Paired with smp_store_release() following vfio_df_open() */
+	if (!smp_load_acquire(&df->access_granted))
+		return -EINVAL;
+
 	if (unlikely(!device->ops->mmap))
 		return -EINVAL;
 
-- 
2.34.1


  parent reply	other threads:[~2023-06-02 12:17 UTC|newest]

Thread overview: 180+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 12:16 [PATCH v12 00/24] Add vfio_device cdev for iommufd support Yi Liu
2023-06-02 12:16 ` [Intel-gfx] " Yi Liu
2023-06-02 12:16 ` [PATCH v12 01/24] vfio: Allocate per device file structure Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-02 12:16 ` [PATCH v12 02/24] vfio: Refine vfio file kAPIs for KVM Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-02 12:16 ` [PATCH v12 03/24] vfio: Accept vfio device file in the KVM facing kAPI Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-02 12:16 ` [PATCH v12 04/24] kvm/vfio: Prepare for accepting vfio device fd Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-02 12:16 ` [PATCH v12 05/24] kvm/vfio: Accept vfio device file from userspace Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-02 12:16 ` [PATCH v12 06/24] vfio: Pass struct vfio_device_file * to vfio_device_open/close() Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-12 21:52   ` Alex Williamson
2023-06-12 21:52     ` Alex Williamson
2023-06-13  5:24     ` Liu, Yi L
2023-06-13  5:24       ` [Intel-gfx] " Liu, Yi L
2023-06-02 12:16 ` Yi Liu [this message]
2023-06-02 12:16   ` [Intel-gfx] [PATCH v12 07/24] vfio: Block device access via device fd until device is opened Yi Liu
2023-06-12 21:52   ` Alex Williamson
2023-06-12 21:52     ` [Intel-gfx] " Alex Williamson
2023-06-13  5:46     ` Liu, Yi L
2023-06-13  5:46       ` [Intel-gfx] " Liu, Yi L
2023-06-13 14:16       ` Alex Williamson
2023-06-13 14:16         ` Alex Williamson
2023-06-13 14:36         ` Liu, Yi L
2023-06-13 14:36           ` [Intel-gfx] " Liu, Yi L
2023-06-13 14:42           ` Alex Williamson
2023-06-13 14:42             ` Alex Williamson
2023-06-13 14:44             ` Liu, Yi L
2023-06-13 14:44               ` [Intel-gfx] " Liu, Yi L
2023-06-13 17:19         ` Jason Gunthorpe
2023-06-13 17:19           ` [Intel-gfx] " Jason Gunthorpe
2023-06-13 17:31           ` Alex Williamson
2023-06-13 17:31             ` Alex Williamson
2023-06-02 12:16 ` [PATCH v12 08/24] vfio: Add cdev_device_open_cnt to vfio_group Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-02 12:16 ` [PATCH v12 09/24] vfio: Make vfio_df_open() single open for device cdev path Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-02 12:16 ` [PATCH v12 10/24] vfio-iommufd: Move noiommu compat validation out of vfio_iommufd_bind() Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-22 17:59   ` Jason Gunthorpe
2023-06-22 17:59     ` [Intel-gfx] " Jason Gunthorpe
2023-06-02 12:16 ` [PATCH v12 11/24] vfio-iommufd: Split bind/attach into two steps Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-22 17:59   ` Jason Gunthorpe
2023-06-22 17:59     ` [Intel-gfx] " Jason Gunthorpe
2023-06-02 12:16 ` [PATCH v12 12/24] vfio: Record devid in vfio_device_file Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-22 18:00   ` Jason Gunthorpe
2023-06-22 18:00     ` Jason Gunthorpe
2023-06-02 12:16 ` [PATCH v12 13/24] vfio-iommufd: Add detach_ioas support for physical VFIO devices Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-23 14:04   ` Jason Gunthorpe
2023-06-23 14:04     ` [Intel-gfx] " Jason Gunthorpe
2023-06-02 12:16 ` [PATCH v12 14/24] iommufd/device: Add iommufd_access_detach() API Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-23 14:15   ` Jason Gunthorpe
2023-06-23 14:15     ` [Intel-gfx] " Jason Gunthorpe
2023-06-25 18:26     ` Nicolin Chen
2023-06-25 18:26       ` [Intel-gfx] " Nicolin Chen
2023-06-02 12:16 ` [PATCH v12 15/24] vfio-iommufd: Add detach_ioas support for emulated VFIO devices Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-23 14:16   ` Jason Gunthorpe
2023-06-23 14:16     ` [Intel-gfx] " Jason Gunthorpe
2023-06-02 12:16 ` [PATCH v12 16/24] vfio: Move vfio_device_group_unregister() to be the first operation in unregister Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-23 14:22   ` Jason Gunthorpe
2023-06-23 14:22     ` [Intel-gfx] " Jason Gunthorpe
2023-06-02 12:16 ` [PATCH v12 17/24] vfio: Add cdev for vfio_device Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-23 15:58   ` Jason Gunthorpe
2023-06-23 15:58     ` [Intel-gfx] " Jason Gunthorpe
2023-06-02 12:16 ` [PATCH v12 18/24] vfio: Add VFIO_DEVICE_BIND_IOMMUFD Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-12 22:27   ` Alex Williamson
2023-06-12 22:27     ` Alex Williamson
2023-06-13  5:48     ` Liu, Yi L
2023-06-13  5:48       ` [Intel-gfx] " Liu, Yi L
2023-06-13 14:18       ` Alex Williamson
2023-06-13 14:18         ` Alex Williamson
2023-06-13 14:28         ` Liu, Yi L
2023-06-13 14:28           ` [Intel-gfx] " Liu, Yi L
2023-06-13 14:39           ` Alex Williamson
2023-06-13 14:39             ` Alex Williamson
2023-06-13 14:42             ` [Intel-gfx] " Liu, Yi L
2023-06-13 14:42               ` Liu, Yi L
2023-06-13 14:59               ` Alex Williamson
2023-06-13 14:59                 ` [Intel-gfx] " Alex Williamson
2023-06-23 16:15   ` Jason Gunthorpe
2023-06-23 16:15     ` [Intel-gfx] " Jason Gunthorpe
2023-06-26  8:34     ` Liu, Yi L
2023-06-26  8:34       ` [Intel-gfx] " Liu, Yi L
2023-06-26 12:56       ` Jason Gunthorpe
2023-06-26 12:56         ` [Intel-gfx] " Jason Gunthorpe
2023-06-26 13:35         ` Liu, Yi L
2023-06-26 13:35           ` [Intel-gfx] " Liu, Yi L
2023-06-26 14:51           ` Liu, Yi L
2023-06-26 14:51             ` [Intel-gfx] " Liu, Yi L
2023-06-28 14:34             ` Jason Gunthorpe
2023-06-28 14:34               ` [Intel-gfx] " Jason Gunthorpe
2023-06-28 14:41               ` Liu, Yi L
2023-06-28 14:41                 ` [Intel-gfx] " Liu, Yi L
2023-06-02 12:16 ` [PATCH v12 19/24] vfio: Add VFIO_DEVICE_[AT|DE]TACH_IOMMUFD_PT Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-23 16:21   ` Jason Gunthorpe
2023-06-23 16:21     ` [Intel-gfx] " Jason Gunthorpe
2023-06-02 12:16 ` [PATCH v12 20/24] vfio: Only check group->type for noiommu test Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-12 22:37   ` Alex Williamson
2023-06-12 22:37     ` [Intel-gfx] " Alex Williamson
2023-06-13  9:20     ` Liu, Yi L
2023-06-13  9:20       ` [Intel-gfx] " Liu, Yi L
2023-06-02 12:16 ` [PATCH v12 21/24] vfio: Determine noiommu device in __vfio_register_dev() Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-12 22:42   ` Alex Williamson
2023-06-12 22:42     ` Alex Williamson
2023-06-13  5:53     ` Liu, Yi L
2023-06-13  5:53       ` [Intel-gfx] " Liu, Yi L
2023-06-13 14:19       ` Alex Williamson
2023-06-13 14:19         ` Alex Williamson
2023-06-13 14:33         ` Liu, Yi L
2023-06-13 14:33           ` [Intel-gfx] " Liu, Yi L
2023-06-13 14:48           ` Alex Williamson
2023-06-13 14:48             ` Alex Williamson
2023-06-13 15:01             ` Liu, Yi L
2023-06-13 15:01               ` [Intel-gfx] " Liu, Yi L
2023-06-13 15:13               ` Alex Williamson
2023-06-13 17:15                 ` Alex Williamson
2023-06-13 17:35                   ` Jason Gunthorpe
2023-06-13 17:35                     ` [Intel-gfx] " Jason Gunthorpe
2023-06-13 20:10                     ` Alex Williamson
2023-06-13 20:10                       ` Alex Williamson
2023-06-14  3:24                       ` Liu, Yi L
2023-06-14  3:24                         ` [Intel-gfx] " Liu, Yi L
2023-06-14  5:42                         ` Tian, Kevin
2023-06-14  5:42                           ` [Intel-gfx] " Tian, Kevin
2023-06-14  6:14                           ` Liu, Yi L
2023-06-14  6:14                             ` [Intel-gfx] " Liu, Yi L
2023-06-14  6:20                             ` Tian, Kevin
2023-06-14  6:20                               ` [Intel-gfx] " Tian, Kevin
2023-06-14 12:23                               ` Jason Gunthorpe
2023-06-14 12:23                                 ` Jason Gunthorpe
2023-06-14 13:12                                 ` [Intel-gfx] " Liu, Yi L
2023-06-14 13:12                                   ` Liu, Yi L
2023-06-14 17:30                                   ` Jason Gunthorpe
2023-06-14 17:30                                     ` [Intel-gfx] " Jason Gunthorpe
2023-06-02 12:16 ` [PATCH v12 22/24] vfio: Remove vfio_device_is_noiommu() Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-12 22:46   ` Alex Williamson
2023-06-12 22:46     ` Alex Williamson
2023-06-02 12:16 ` [PATCH v12 23/24] vfio: Compile vfio_group infrastructure optionally Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-23 16:35   ` Jason Gunthorpe
2023-06-23 16:35     ` [Intel-gfx] " Jason Gunthorpe
2023-06-02 12:16 ` [PATCH v12 24/24] docs: vfio: Add vfio device cdev description Yi Liu
2023-06-02 12:16   ` [Intel-gfx] " Yi Liu
2023-06-12 23:06   ` Alex Williamson
2023-06-12 23:06     ` Alex Williamson
2023-06-13 12:01     ` Liu, Yi L
2023-06-13 12:01       ` [Intel-gfx] " Liu, Yi L
2023-06-13 14:24       ` Alex Williamson
2023-06-13 14:24         ` Alex Williamson
2023-06-13 14:48         ` Liu, Yi L
2023-06-13 14:48           ` [Intel-gfx] " Liu, Yi L
2023-06-13 15:04           ` Alex Williamson
2023-06-13 15:04             ` Alex Williamson
2023-06-13 15:11             ` Liu, Yi L
2023-06-13 15:11               ` [Intel-gfx] " Liu, Yi L
2023-06-13 17:30               ` Alex Williamson
2023-06-13 17:30                 ` Alex Williamson
2023-06-02 16:19 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Add vfio_device cdev for iommufd support (rev15) Patchwork
2023-06-07  8:27 ` [PATCH v12 00/24] Add vfio_device cdev for iommufd support Nicolin Chen
2023-06-07  8:27   ` [Intel-gfx] " Nicolin Chen
2023-06-08  6:58 ` Jiang, Yanting
2023-06-08  6:58   ` [Intel-gfx] " Jiang, Yanting
2023-06-09 16:47 ` Matthew Rosato
2023-06-09 16:47   ` [Intel-gfx] " Matthew Rosato
2023-06-14 15:47 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Add vfio_device cdev for iommufd support (rev16) 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=20230602121653.80017-8-yi.l.liu@intel.com \
    --to=yi.l.liu@intel.com \
    --cc=alex.williamson@redhat.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=clegoate@redhat.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=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --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=yanting.jiang@intel.com \
    --cc=yi.y.sun@linux.intel.com \
    --cc=zhenzhong.duan@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.