From: "Liu, Yi L" <yi.l.liu@intel.com> To: Alex Williamson <alex.williamson@redhat.com> Cc: "jgg@nvidia.com" <jgg@nvidia.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>, "Jiang, Yanting" <yanting.jiang@intel.com> Subject: RE: [PATCH v8 08/24] vfio: Block device access via device fd until device is opened Date: Wed, 29 Mar 2023 02:23:46 +0000 [thread overview] Message-ID: <DS0PR11MB75290A2ADD9EA54E7F79893BC3899@DS0PR11MB7529.namprd11.prod.outlook.com> (raw) In-Reply-To: <20230328153352.6c1e2088.alex.williamson@redhat.com> > From: Alex Williamson <alex.williamson@redhat.com> > Sent: Wednesday, March 29, 2023 5:34 AM > > On Mon, 27 Mar 2023 02:40:31 -0700 > Yi Liu <yi.l.liu@intel.com> wrote: > > > 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> > > Tested-by: Terrence Xu <terrence.xu@intel.com> > > Tested-by: Nicolin Chen <nicolinc@nvidia.com> > > Tested-by: Matthew Rosato <mjrosato@linux.ibm.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 | 41 ++++++++++++++++++++++++++++++++++--- > --- > > 3 files changed, 46 insertions(+), 7 deletions(-) > > > > diff --git a/drivers/vfio/group.c b/drivers/vfio/group.c > > index 9a7b2765eef6..4f267ae7bebc 100644 > > --- a/drivers/vfio/group.c > > +++ b/drivers/vfio/group.c > > @@ -194,9 +194,18 @@ static int vfio_device_group_open(struct > vfio_device_file *df) > > df->iommufd = device->group->iommufd; > > > > ret = vfio_device_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 > > + */ > > + 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 cffc08f5a6f1..854f2c97cb9a 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 2ea6cb6d03c7..b515bbda4c74 100644 > > --- a/drivers/vfio/vfio_main.c > > +++ b/drivers/vfio/vfio_main.c > > @@ -1114,6 +1114,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_device_open() */ > > + if (!smp_load_acquire(&df->access_granted)) > > + return -EINVAL; > > + > > ret = vfio_device_pm_runtime_get(device); > > if (ret) > > return ret; > > @@ -1141,6 +1145,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_device_open() */ > > + if (!smp_load_acquire(&df->access_granted)) > > + return -EINVAL; > > + > > if (unlikely(!device->ops->read)) > > return -EINVAL; > > > > @@ -1154,6 +1162,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_device_open() */ > > + if (!smp_load_acquire(&df->access_granted)) > > + return -EINVAL; > > + > > if (unlikely(!device->ops->write)) > > return -EINVAL; > > > > @@ -1165,6 +1177,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_device_open() */ > > + if (!smp_load_acquire(&df->access_granted)) > > + return -EINVAL; > > + > > if (unlikely(!device->ops->mmap)) > > return -EINVAL; > > > > @@ -1201,6 +1217,24 @@ bool vfio_file_is_valid(struct file *file) > > } > > EXPORT_SYMBOL_GPL(vfio_file_is_valid); > > > > +/* > > + * Return true if the input file is a vfio device file and has opened > > + * the input device. Otherwise, return false. > > + */ > > +static bool vfio_file_has_device_access(struct file *file, > > + struct vfio_device *device) > > +{ > > + struct vfio_device *vdev = vfio_device_from_file(file); > > + struct vfio_device_file *df; > > + > > + if (!vdev || vdev != device) > > + return false; > > + > > + df = file->private_data; > > + > > + return READ_ONCE(df->access_granted); > > Why did we change from smp_load_acquire() to READ_ONCE() here? > Thanks, It should still use smp_load_acquire(). When this is added, its major usage is under the dev_set->lock, so it is functionally ok since the writer of the df->access_granted is also under the dev_set->lock. However, as an helper in vfio_core, it should use smp_load_acquire() otherwise needs to add lockdep to check if dev_set->lock is held. Thanks, Yi Liu > > > +} > > + > > /** > > * vfio_file_has_dev - True if the VFIO file is a handle for device > > * @file: VFIO file to check > > @@ -1211,17 +1245,12 @@ EXPORT_SYMBOL_GPL(vfio_file_is_valid); > > bool vfio_file_has_dev(struct file *file, struct vfio_device *device) > > { > > struct vfio_group *group; > > - struct vfio_device *vdev; > > > > group = vfio_group_from_file(file); > > if (group) > > return vfio_group_has_dev(group, device); > > > > - vdev = vfio_device_from_file(file); > > - if (vdev) > > - return vdev == device; > > - > > - return false; > > + return vfio_file_has_device_access(file, device); > > } > > EXPORT_SYMBOL_GPL(vfio_file_has_dev); > >
WARNING: multiple messages have this Message-ID (diff)
From: "Liu, Yi L" <yi.l.liu@intel.com> To: Alex Williamson <alex.williamson@redhat.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>, "Jiang, Yanting" <yanting.jiang@intel.com>, "joro@8bytes.org" <joro@8bytes.org>, "nicolinc@nvidia.com" <nicolinc@nvidia.com>, "jgg@nvidia.com" <jgg@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 v8 08/24] vfio: Block device access via device fd until device is opened Date: Wed, 29 Mar 2023 02:23:46 +0000 [thread overview] Message-ID: <DS0PR11MB75290A2ADD9EA54E7F79893BC3899@DS0PR11MB7529.namprd11.prod.outlook.com> (raw) In-Reply-To: <20230328153352.6c1e2088.alex.williamson@redhat.com> > From: Alex Williamson <alex.williamson@redhat.com> > Sent: Wednesday, March 29, 2023 5:34 AM > > On Mon, 27 Mar 2023 02:40:31 -0700 > Yi Liu <yi.l.liu@intel.com> wrote: > > > 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> > > Tested-by: Terrence Xu <terrence.xu@intel.com> > > Tested-by: Nicolin Chen <nicolinc@nvidia.com> > > Tested-by: Matthew Rosato <mjrosato@linux.ibm.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 | 41 ++++++++++++++++++++++++++++++++++--- > --- > > 3 files changed, 46 insertions(+), 7 deletions(-) > > > > diff --git a/drivers/vfio/group.c b/drivers/vfio/group.c > > index 9a7b2765eef6..4f267ae7bebc 100644 > > --- a/drivers/vfio/group.c > > +++ b/drivers/vfio/group.c > > @@ -194,9 +194,18 @@ static int vfio_device_group_open(struct > vfio_device_file *df) > > df->iommufd = device->group->iommufd; > > > > ret = vfio_device_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 > > + */ > > + 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 cffc08f5a6f1..854f2c97cb9a 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 2ea6cb6d03c7..b515bbda4c74 100644 > > --- a/drivers/vfio/vfio_main.c > > +++ b/drivers/vfio/vfio_main.c > > @@ -1114,6 +1114,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_device_open() */ > > + if (!smp_load_acquire(&df->access_granted)) > > + return -EINVAL; > > + > > ret = vfio_device_pm_runtime_get(device); > > if (ret) > > return ret; > > @@ -1141,6 +1145,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_device_open() */ > > + if (!smp_load_acquire(&df->access_granted)) > > + return -EINVAL; > > + > > if (unlikely(!device->ops->read)) > > return -EINVAL; > > > > @@ -1154,6 +1162,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_device_open() */ > > + if (!smp_load_acquire(&df->access_granted)) > > + return -EINVAL; > > + > > if (unlikely(!device->ops->write)) > > return -EINVAL; > > > > @@ -1165,6 +1177,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_device_open() */ > > + if (!smp_load_acquire(&df->access_granted)) > > + return -EINVAL; > > + > > if (unlikely(!device->ops->mmap)) > > return -EINVAL; > > > > @@ -1201,6 +1217,24 @@ bool vfio_file_is_valid(struct file *file) > > } > > EXPORT_SYMBOL_GPL(vfio_file_is_valid); > > > > +/* > > + * Return true if the input file is a vfio device file and has opened > > + * the input device. Otherwise, return false. > > + */ > > +static bool vfio_file_has_device_access(struct file *file, > > + struct vfio_device *device) > > +{ > > + struct vfio_device *vdev = vfio_device_from_file(file); > > + struct vfio_device_file *df; > > + > > + if (!vdev || vdev != device) > > + return false; > > + > > + df = file->private_data; > > + > > + return READ_ONCE(df->access_granted); > > Why did we change from smp_load_acquire() to READ_ONCE() here? > Thanks, It should still use smp_load_acquire(). When this is added, its major usage is under the dev_set->lock, so it is functionally ok since the writer of the df->access_granted is also under the dev_set->lock. However, as an helper in vfio_core, it should use smp_load_acquire() otherwise needs to add lockdep to check if dev_set->lock is held. Thanks, Yi Liu > > > +} > > + > > /** > > * vfio_file_has_dev - True if the VFIO file is a handle for device > > * @file: VFIO file to check > > @@ -1211,17 +1245,12 @@ EXPORT_SYMBOL_GPL(vfio_file_is_valid); > > bool vfio_file_has_dev(struct file *file, struct vfio_device *device) > > { > > struct vfio_group *group; > > - struct vfio_device *vdev; > > > > group = vfio_group_from_file(file); > > if (group) > > return vfio_group_has_dev(group, device); > > > > - vdev = vfio_device_from_file(file); > > - if (vdev) > > - return vdev == device; > > - > > - return false; > > + return vfio_file_has_device_access(file, device); > > } > > EXPORT_SYMBOL_GPL(vfio_file_has_dev); > >
next prev parent reply other threads:[~2023-03-29 2:23 UTC|newest] Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-27 9:40 [PATCH v8 00/24] Add vfio_device cdev for iommufd support Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-27 9:40 ` [PATCH v8 01/24] vfio: Allocate per device file structure Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-27 9:40 ` [PATCH v8 02/24] vfio: Refine vfio file kAPIs for KVM Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-27 9:40 ` [PATCH v8 03/24] vfio: Remove vfio_file_is_group() Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-30 23:50 ` Jason Gunthorpe 2023-03-30 23:50 ` [Intel-gfx] " Jason Gunthorpe 2023-03-27 9:40 ` [PATCH v8 04/24] vfio: Accept vfio device file in the KVM facing kAPI Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-27 9:40 ` [PATCH v8 05/24] kvm/vfio: Rename kvm_vfio_group to prepare for accepting vfio device fd Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-27 9:40 ` [PATCH v8 06/24] kvm/vfio: Accept vfio device file from userspace Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-27 9:40 ` [PATCH v8 07/24] vfio: Pass struct vfio_device_file * to vfio_device_open/close() Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-27 9:40 ` [PATCH v8 08/24] vfio: Block device access via device fd until device is opened Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-28 21:33 ` Alex Williamson 2023-03-28 21:33 ` Alex Williamson 2023-03-29 2:23 ` Liu, Yi L [this message] 2023-03-29 2:23 ` [Intel-gfx] " Liu, Yi L 2023-03-27 9:40 ` [PATCH v8 09/24] vfio: Add cdev_device_open_cnt to vfio_group Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-27 9:40 ` [PATCH v8 10/24] vfio: Make vfio_device_open() single open for device cdev path Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-30 23:52 ` Jason Gunthorpe 2023-03-30 23:52 ` [Intel-gfx] " Jason Gunthorpe 2023-03-27 9:40 ` [PATCH v8 11/24] vfio: Make vfio_device_first_open() to accept NULL iommufd for noiommu Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-30 23:56 ` Jason Gunthorpe 2023-03-30 23:56 ` [Intel-gfx] " Jason Gunthorpe 2023-03-27 9:40 ` [PATCH v8 12/24] vfio-iommufd: Move noiommu support out of vfio_iommufd_bind() Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-27 9:40 ` [PATCH v8 13/24] vfio-iommufd: Split bind/attach into two steps Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-27 9:40 ` [PATCH v8 14/24] vfio: Record devid in vfio_device_file Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-27 9:40 ` [PATCH v8 15/24] vfio-iommufd: Add detach_ioas support for physical VFIO devices Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-27 9:40 ` [PATCH v8 16/24] iommufd/device: Add iommufd_access_detach() API Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-28 2:23 ` Jon Pan-Doh 2023-03-28 2:23 ` [Intel-gfx] " Jon Pan-Doh 2023-03-28 15:54 ` Nicolin Chen 2023-03-28 15:54 ` [Intel-gfx] " Nicolin Chen 2023-03-29 2:24 ` Liu, Yi L 2023-03-29 2:24 ` [Intel-gfx] " Liu, Yi L 2023-03-27 9:40 ` [PATCH v8 17/24] vfio-iommufd: Add detach_ioas support for emulated VFIO devices Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-27 9:40 ` [PATCH v8 18/24] vfio: Determine noiommu in vfio_device registration Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-28 6:36 ` Tian, Kevin 2023-03-28 6:36 ` [Intel-gfx] " Tian, Kevin 2023-03-27 9:40 ` [PATCH v8 19/24] vfio: Name noiommu vfio_device with "noiommu-" prefix Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-28 6:37 ` Tian, Kevin 2023-03-28 6:37 ` [Intel-gfx] " Tian, Kevin 2023-03-27 9:40 ` [PATCH v8 20/24] vfio: Add cdev for vfio_device Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-29 19:57 ` Alex Williamson 2023-03-29 19:57 ` [Intel-gfx] " Alex Williamson 2023-03-30 5:35 ` Liu, Yi L 2023-03-30 5:35 ` [Intel-gfx] " Liu, Yi L 2023-03-27 9:40 ` [PATCH v8 21/24] vfio: Add VFIO_DEVICE_BIND_IOMMUFD Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-29 21:00 ` Alex Williamson 2023-03-29 21:00 ` Alex Williamson 2023-03-29 23:22 ` Jason Gunthorpe 2023-03-29 23:22 ` [Intel-gfx] " Jason Gunthorpe 2023-03-30 12:52 ` Liu, Yi L 2023-03-30 12:52 ` [Intel-gfx] " Liu, Yi L 2023-03-30 12:59 ` Jason Gunthorpe 2023-03-30 12:59 ` [Intel-gfx] " Jason Gunthorpe 2023-03-30 7:09 ` Liu, Yi L 2023-03-30 7:09 ` [Intel-gfx] " Liu, Yi L 2023-03-30 11:52 ` Jason Gunthorpe 2023-03-30 11:52 ` Jason Gunthorpe 2023-03-30 12:53 ` Liu, Yi L 2023-03-30 12:53 ` [Intel-gfx] " Liu, Yi L 2023-03-27 9:40 ` [PATCH v8 22/24] vfio: Add VFIO_DEVICE_AT[DE]TACH_IOMMUFD_PT Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-29 21:19 ` Alex Williamson 2023-03-29 21:19 ` [Intel-gfx] " Alex Williamson 2023-03-30 13:02 ` Liu, Yi L 2023-03-30 13:02 ` Liu, Yi L 2023-03-27 9:40 ` [PATCH v8 23/24] vfio: Compile group optionally Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-29 21:51 ` Alex Williamson 2023-03-29 21:51 ` Alex Williamson 2023-03-30 13:06 ` Liu, Yi L 2023-03-30 13:06 ` [Intel-gfx] " Liu, Yi L 2023-03-27 9:40 ` [PATCH v8 24/24] docs: vfio: Add vfio device cdev description Yi Liu 2023-03-27 9:40 ` [Intel-gfx] " Yi Liu 2023-03-29 22:47 ` Alex Williamson 2023-03-29 22:47 ` Alex Williamson 2023-03-29 22:57 ` Alex Williamson 2023-03-29 22:57 ` [Intel-gfx] " Alex Williamson 2023-03-30 13:11 ` Liu, Yi L 2023-03-30 13:11 ` [Intel-gfx] " Liu, Yi L 2023-03-27 12:03 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Add vfio_device cdev for iommufd support (rev9) Patchwork 2023-03-27 17:48 ` [Intel-gfx] [PATCH v8 00/24] Add vfio_device cdev for iommufd support Nicolin Chen 2023-03-27 17:48 ` Nicolin Chen 2023-03-28 23:16 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Add vfio_device cdev for iommufd support (rev10) Patchwork 2023-03-31 3:10 ` [PATCH v8 00/24] Add vfio_device cdev for iommufd support Jiang, Yanting 2023-03-31 3:10 ` [Intel-gfx] " Jiang, Yanting 2023-03-31 5:01 ` Jiang, Yanting 2023-03-31 5:01 ` [Intel-gfx] " Jiang, Yanting
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=DS0PR11MB75290A2ADD9EA54E7F79893BC3899@DS0PR11MB7529.namprd11.prod.outlook.com \ --to=yi.l.liu@intel.com \ --cc=alex.williamson@redhat.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=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 \ /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: linkBe 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.