All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: David Airlie <airlied@linux.ie>,
	Tony Krowiak <akrowiak@linux.ibm.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Cornelia Huck <cohuck@redhat.com>,
	Jonathan Corbet <corbet@lwn.net>, Daniel Vetter <daniel@ffwll.ch>,
	Diana Craciun <diana.craciun@oss.nxp.com>,
	dri-devel@lists.freedesktop.org,
	Eric Auger <eric.auger@redhat.com>,
	Eric Farman <farman@linux.ibm.com>,
	Harald Freudenberger <freude@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	intel-gfx@lists.freedesktop.org,
	intel-gvt-dev@lists.freedesktop.org,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Jason Herne <jjherne@linux.ibm.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	kvm@vger.kernel.org, Kirti Wankhede <kwankhede@nvidia.com>,
	linux-doc@vger.kernel.org, linux-s390@vger.kernel.org,
	Matthew Rosato <mjrosato@linux.ibm.com>,
	Peter Oberparleiter <oberpar@linux.ibm.com>,
	Halil Pasic <pasic@linux.ibm.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Vineeth Vijayan <vneethv@linux.ibm.com>,
	Zhi Wang <zhi.a.wang@intel.com>,
	"Raj, Ashok" <ashok.raj@intel.com>,
	Christoph Hellwig <hch@lst.de>,
	Leon Romanovsky <leonro@nvidia.com>,
	Max Gurtovoy <mgurtovoy@nvidia.com>,
	Yishai Hadas <yishaih@nvidia.com>,
	Zhenyu Wang <zhenyuw@linux.intel.com>
Subject: Re: [PATCH v2 09/14] vfio/pci: Change vfio_pci_try_bus_reset() to use the dev_set
Date: Fri, 23 Jul 2021 10:05:43 +0200	[thread overview]
Message-ID: <20210723080543.GD2795@lst.de> (raw)
In-Reply-To: <9-v2-b6a5582525c9+ff96-vfio_reflck_jgg@nvidia.com>

On Tue, Jul 20, 2021 at 02:42:55PM -0300, Jason Gunthorpe wrote:
> Keep track of all the vfio_devices that have been added to the device set
> and use this list in vfio_pci_try_bus_reset() instead of trying to work
> backwards from the pci_device.
> 
> The dev_set->lock directly prevents devices from joining/leaving the set,
> which further implies the pci_device cannot change drivers or that the
> vfio_device be freed, eliminating the need for get/put's.
> 
> Completeness of the device set can be directly measured by checking if
> every PCI device in the reset group is also in the device set - which
> proves that VFIO drivers are attached to everything.
> 
> This restructuring corrects a call to pci_dev_driver() without holding the
> device_lock() and removes a hard wiring to &vfio_pci_driver.
> 
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

I think the addition of the list to the dev_set should be a different
patch.  Or maybe even go into the one adding the dev_set concept.

> +static int vfio_pci_check_all_devices_bound(struct pci_dev *pdev, void *data)
>  {
> +	struct vfio_device_set *dev_set = data;
> +	struct vfio_device *cur;
>  
> +	lockdep_assert_held(&dev_set->lock);
>  
> +	list_for_each_entry(cur, &dev_set->device_list, dev_set_list)
> +		if (cur->dev == &pdev->dev)
> +			return 0;
> +	return -EBUSY;

I don't understand this logic.  If there is any device in the set that
does now have the same struct device we're in trouble?  Please clearly
document what this is trying to do.  If the bound in the name makes sense
you probably want to check the driver instead.

>  static void vfio_pci_try_bus_reset(struct vfio_pci_device *vdev)
>  {
> +	/* All VFIO devices have a closed FD */
> +	list_for_each_entry(cur, &dev_set->device_list, vdev.dev_set_list)
> +		if (cur->vdev.open_count)
> +			return;
> +
> +	/* All devices in the group to be reset need VFIO devices */
> +	if (vfio_pci_for_each_slot_or_bus(
> +		    vdev->pdev, vfio_pci_check_all_devices_bound, dev_set,
> +		    !pci_probe_reset_slot(vdev->pdev->slot)))
> +		return;
>  
>  	/* Does at least one need a reset? */

These checks look a little strange, and the comments don't make much
sense.  What about an incremental patch like this?

diff --git a/drivers/vfio/pci/vfio_pci.c b/drivers/vfio/pci/vfio_pci.c
index fbc20f6d2dd412..d8375a5e77e07c 100644
--- a/drivers/vfio/pci/vfio_pci.c
+++ b/drivers/vfio/pci/vfio_pci.c
@@ -2188,10 +2188,34 @@ static int vfio_pci_try_zap_and_vma_lock_cb(struct pci_dev *pdev, void *data)
 	return 0;
 }
 
+static struct pci_dev *vfio_pci_reset_target(struct vfio_pci_device *vdev)
+{
+	struct vfio_device_set *dev_set = vdev->vdev.dev_set;
+	struct vfio_pci_device *cur;
+
+	/* none of the device is allowed to be currently open: */
+	list_for_each_entry(cur, &dev_set->device_list, vdev.dev_set_list)
+		if (cur->vdev.open_count)
+			return NULL;
+
+	/* all devices in the group to be reset need to be VFIO devices: */
+	if (vfio_pci_for_each_slot_or_bus(vdev->pdev,
+			vfio_pci_check_all_devices_bound, dev_set,
+			!pci_probe_reset_slot(vdev->pdev->slot)))
+		return NULL;
+
+	/* Does at least one need a reset? */
+	list_for_each_entry(cur, &dev_set->device_list, vdev.dev_set_list)
+		if (cur->needs_reset)
+			return cur->pdev;
+
+	return NULL;
+}
+
 /*
  * If a bus or slot reset is available for the provided device and:
  *  - All of the devices affected by that bus or slot reset are unused
- *    (!refcnt)
+ *    (!open_count)
  *  - At least one of the affected devices is marked dirty via
  *    needs_reset (such as by lack of FLR support)
  * Then attempt to perform that bus or slot reset.  Callers are required
@@ -2206,8 +2230,8 @@ static int vfio_pci_try_zap_and_vma_lock_cb(struct pci_dev *pdev, void *data)
 static void vfio_pci_try_bus_reset(struct vfio_pci_device *vdev)
 {
 	struct vfio_device_set *dev_set = vdev->vdev.dev_set;
-	struct vfio_pci_device *to_reset = NULL;
 	struct vfio_pci_device *cur;
+	struct pci_dev *to_reset;
 	int ret;
 
 	if (pci_probe_reset_slot(vdev->pdev->slot) &&
@@ -2216,35 +2240,18 @@ static void vfio_pci_try_bus_reset(struct vfio_pci_device *vdev)
 
 	lockdep_assert_held(&vdev->vdev.dev_set->lock);
 
-	/* All VFIO devices have a closed FD */
-	list_for_each_entry(cur, &dev_set->device_list, vdev.dev_set_list)
-		if (cur->vdev.open_count)
-			return;
-
-	/* All devices in the group to be reset need VFIO devices */
-	if (vfio_pci_for_each_slot_or_bus(
-		    vdev->pdev, vfio_pci_check_all_devices_bound, dev_set,
-		    !pci_probe_reset_slot(vdev->pdev->slot)))
-		return;
-
-	/* Does at least one need a reset? */
-	list_for_each_entry(cur, &dev_set->device_list, vdev.dev_set_list) {
-		if (cur->needs_reset) {
-			to_reset = cur;
-			break;
-		}
-	}
+	to_reset = vfio_pci_reset_target(vdev);
 	if (!to_reset)
 		return;
 
-	ret = pci_reset_bus(to_reset->pdev);
+	ret = pci_reset_bus(to_reset);
 	if (ret)
 		return;
 
 	list_for_each_entry(cur, &dev_set->device_list, vdev.dev_set_list) {
 		cur->needs_reset = false;
 
-		if (cur != to_reset && !disable_idle_d3)
+		if (cur->pdev != to_reset && !disable_idle_d3)
 			vfio_pci_set_power_state(cur, PCI_D3hot);
 	}
 }

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: kvm@vger.kernel.org, linux-doc@vger.kernel.org,
	David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org,
	Kirti Wankhede <kwankhede@nvidia.com>,
	Max Gurtovoy <mgurtovoy@nvidia.com>,
	Vineeth Vijayan <vneethv@linux.ibm.com>,
	Diana Craciun <diana.craciun@oss.nxp.com>,
	Leon Romanovsky <leonro@nvidia.com>,
	Christoph Hellwig <hch@lst.de>,
	linux-s390@vger.kernel.org,
	Matthew Rosato <mjrosato@linux.ibm.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Halil Pasic <pasic@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	intel-gfx@lists.freedesktop.org,
	Jason Herne <jjherne@linux.ibm.com>,
	Eric Farman <farman@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	Eric Auger <eric.auger@redhat.com>,
	Harald Freudenberger <freude@linux.ibm.com>,
	intel-gvt-dev@lists.freedesktop.org, "Raj,
	Ashok" <ashok.raj@intel.com>,
	Tony Krowiak <akrowiak@linux.ibm.com>,
	Yishai Hadas <yishaih@nvidia.com>,
	Cornelia Huck <cohuck@redhat.com>,
	Peter Oberparleiter <oberpar@linux.ibm.com>
Subject: Re: [Intel-gfx] [PATCH v2 09/14] vfio/pci: Change vfio_pci_try_bus_reset() to use the dev_set
Date: Fri, 23 Jul 2021 10:05:43 +0200	[thread overview]
Message-ID: <20210723080543.GD2795@lst.de> (raw)
In-Reply-To: <9-v2-b6a5582525c9+ff96-vfio_reflck_jgg@nvidia.com>

On Tue, Jul 20, 2021 at 02:42:55PM -0300, Jason Gunthorpe wrote:
> Keep track of all the vfio_devices that have been added to the device set
> and use this list in vfio_pci_try_bus_reset() instead of trying to work
> backwards from the pci_device.
> 
> The dev_set->lock directly prevents devices from joining/leaving the set,
> which further implies the pci_device cannot change drivers or that the
> vfio_device be freed, eliminating the need for get/put's.
> 
> Completeness of the device set can be directly measured by checking if
> every PCI device in the reset group is also in the device set - which
> proves that VFIO drivers are attached to everything.
> 
> This restructuring corrects a call to pci_dev_driver() without holding the
> device_lock() and removes a hard wiring to &vfio_pci_driver.
> 
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

I think the addition of the list to the dev_set should be a different
patch.  Or maybe even go into the one adding the dev_set concept.

> +static int vfio_pci_check_all_devices_bound(struct pci_dev *pdev, void *data)
>  {
> +	struct vfio_device_set *dev_set = data;
> +	struct vfio_device *cur;
>  
> +	lockdep_assert_held(&dev_set->lock);
>  
> +	list_for_each_entry(cur, &dev_set->device_list, dev_set_list)
> +		if (cur->dev == &pdev->dev)
> +			return 0;
> +	return -EBUSY;

I don't understand this logic.  If there is any device in the set that
does now have the same struct device we're in trouble?  Please clearly
document what this is trying to do.  If the bound in the name makes sense
you probably want to check the driver instead.

>  static void vfio_pci_try_bus_reset(struct vfio_pci_device *vdev)
>  {
> +	/* All VFIO devices have a closed FD */
> +	list_for_each_entry(cur, &dev_set->device_list, vdev.dev_set_list)
> +		if (cur->vdev.open_count)
> +			return;
> +
> +	/* All devices in the group to be reset need VFIO devices */
> +	if (vfio_pci_for_each_slot_or_bus(
> +		    vdev->pdev, vfio_pci_check_all_devices_bound, dev_set,
> +		    !pci_probe_reset_slot(vdev->pdev->slot)))
> +		return;
>  
>  	/* Does at least one need a reset? */

These checks look a little strange, and the comments don't make much
sense.  What about an incremental patch like this?

diff --git a/drivers/vfio/pci/vfio_pci.c b/drivers/vfio/pci/vfio_pci.c
index fbc20f6d2dd412..d8375a5e77e07c 100644
--- a/drivers/vfio/pci/vfio_pci.c
+++ b/drivers/vfio/pci/vfio_pci.c
@@ -2188,10 +2188,34 @@ static int vfio_pci_try_zap_and_vma_lock_cb(struct pci_dev *pdev, void *data)
 	return 0;
 }
 
+static struct pci_dev *vfio_pci_reset_target(struct vfio_pci_device *vdev)
+{
+	struct vfio_device_set *dev_set = vdev->vdev.dev_set;
+	struct vfio_pci_device *cur;
+
+	/* none of the device is allowed to be currently open: */
+	list_for_each_entry(cur, &dev_set->device_list, vdev.dev_set_list)
+		if (cur->vdev.open_count)
+			return NULL;
+
+	/* all devices in the group to be reset need to be VFIO devices: */
+	if (vfio_pci_for_each_slot_or_bus(vdev->pdev,
+			vfio_pci_check_all_devices_bound, dev_set,
+			!pci_probe_reset_slot(vdev->pdev->slot)))
+		return NULL;
+
+	/* Does at least one need a reset? */
+	list_for_each_entry(cur, &dev_set->device_list, vdev.dev_set_list)
+		if (cur->needs_reset)
+			return cur->pdev;
+
+	return NULL;
+}
+
 /*
  * If a bus or slot reset is available for the provided device and:
  *  - All of the devices affected by that bus or slot reset are unused
- *    (!refcnt)
+ *    (!open_count)
  *  - At least one of the affected devices is marked dirty via
  *    needs_reset (such as by lack of FLR support)
  * Then attempt to perform that bus or slot reset.  Callers are required
@@ -2206,8 +2230,8 @@ static int vfio_pci_try_zap_and_vma_lock_cb(struct pci_dev *pdev, void *data)
 static void vfio_pci_try_bus_reset(struct vfio_pci_device *vdev)
 {
 	struct vfio_device_set *dev_set = vdev->vdev.dev_set;
-	struct vfio_pci_device *to_reset = NULL;
 	struct vfio_pci_device *cur;
+	struct pci_dev *to_reset;
 	int ret;
 
 	if (pci_probe_reset_slot(vdev->pdev->slot) &&
@@ -2216,35 +2240,18 @@ static void vfio_pci_try_bus_reset(struct vfio_pci_device *vdev)
 
 	lockdep_assert_held(&vdev->vdev.dev_set->lock);
 
-	/* All VFIO devices have a closed FD */
-	list_for_each_entry(cur, &dev_set->device_list, vdev.dev_set_list)
-		if (cur->vdev.open_count)
-			return;
-
-	/* All devices in the group to be reset need VFIO devices */
-	if (vfio_pci_for_each_slot_or_bus(
-		    vdev->pdev, vfio_pci_check_all_devices_bound, dev_set,
-		    !pci_probe_reset_slot(vdev->pdev->slot)))
-		return;
-
-	/* Does at least one need a reset? */
-	list_for_each_entry(cur, &dev_set->device_list, vdev.dev_set_list) {
-		if (cur->needs_reset) {
-			to_reset = cur;
-			break;
-		}
-	}
+	to_reset = vfio_pci_reset_target(vdev);
 	if (!to_reset)
 		return;
 
-	ret = pci_reset_bus(to_reset->pdev);
+	ret = pci_reset_bus(to_reset);
 	if (ret)
 		return;
 
 	list_for_each_entry(cur, &dev_set->device_list, vdev.dev_set_list) {
 		cur->needs_reset = false;
 
-		if (cur != to_reset && !disable_idle_d3)
+		if (cur->pdev != to_reset && !disable_idle_d3)
 			vfio_pci_set_power_state(cur, PCI_D3hot);
 	}
 }
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2021-07-23  8:05 UTC|newest]

Thread overview: 122+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 17:42 [PATCH v2 00/14] Provide core infrastructure for managing open/release Jason Gunthorpe
2021-07-20 17:42 ` [Intel-gfx] " Jason Gunthorpe
2021-07-20 17:42 ` Jason Gunthorpe
2021-07-20 17:42 ` [PATCH v2 01/14] vfio/samples: Remove module get/put Jason Gunthorpe
2021-07-20 17:42   ` [Intel-gfx] " Jason Gunthorpe
2021-07-20 17:42   ` Jason Gunthorpe
2021-07-23  7:18   ` Christoph Hellwig
2021-07-23  7:18     ` [Intel-gfx] " Christoph Hellwig
2021-07-20 17:42 ` [PATCH v2 02/14] vfio/mbochs: Fix missing error unwind in mbochs_probe() Jason Gunthorpe
2021-07-20 17:42   ` [Intel-gfx] " Jason Gunthorpe
2021-07-20 17:42   ` Jason Gunthorpe
2021-07-20 22:01   ` Alex Williamson
2021-07-20 22:01     ` [Intel-gfx] " Alex Williamson
2021-07-20 22:01     ` Alex Williamson
2021-07-20 22:49     ` Jason Gunthorpe
2021-07-20 22:49       ` [Intel-gfx] " Jason Gunthorpe
2021-07-20 22:49       ` Jason Gunthorpe
2021-07-20 22:54       ` Alex Williamson
2021-07-20 22:54         ` [Intel-gfx] " Alex Williamson
2021-07-20 22:54         ` Alex Williamson
2021-07-21  9:18       ` Cornelia Huck
2021-07-21  9:18         ` [Intel-gfx] " Cornelia Huck
2021-07-21  9:18         ` Cornelia Huck
2021-07-21  9:16   ` Cornelia Huck
2021-07-21  9:16     ` [Intel-gfx] " Cornelia Huck
2021-07-21  9:16     ` Cornelia Huck
2021-07-20 17:42 ` [PATCH v2 03/14] vfio: Introduce a vfio_uninit_group_dev() API call Jason Gunthorpe
2021-07-20 17:42   ` [Intel-gfx] " Jason Gunthorpe
2021-07-20 17:42   ` Jason Gunthorpe
2021-07-21 11:33   ` Cornelia Huck
2021-07-21 11:33     ` [Intel-gfx] " Cornelia Huck
2021-07-21 11:33     ` Cornelia Huck
2021-07-23  7:18   ` Christoph Hellwig
2021-07-23  7:18     ` [Intel-gfx] " Christoph Hellwig
2021-07-20 17:42 ` [PATCH v2 04/14] vfio: Provide better generic support for open/release vfio_device_ops Jason Gunthorpe
2021-07-20 17:42   ` [Intel-gfx] " Jason Gunthorpe
2021-07-20 17:42   ` Jason Gunthorpe
2021-07-22 14:42   ` Cornelia Huck
2021-07-22 14:42     ` [Intel-gfx] " Cornelia Huck
2021-07-22 14:42     ` Cornelia Huck
2021-07-23  7:39   ` Christoph Hellwig
2021-07-23  7:39     ` [Intel-gfx] " Christoph Hellwig
2021-07-23 14:38     ` Jason Gunthorpe
2021-07-23 14:38       ` [Intel-gfx] " Jason Gunthorpe
2021-07-23 14:38       ` Jason Gunthorpe
2021-07-20 17:42 ` [PATCH v2 05/14] vfio/samples: Delete useless open/close Jason Gunthorpe
2021-07-20 17:42   ` [Intel-gfx] " Jason Gunthorpe
2021-07-20 17:42   ` Jason Gunthorpe
2021-07-23  7:39   ` Christoph Hellwig
2021-07-23  7:39     ` [Intel-gfx] " Christoph Hellwig
2021-07-20 17:42 ` [PATCH v2 06/14] vfio/fsl: Move to the device set infrastructure Jason Gunthorpe
2021-07-20 17:42   ` [Intel-gfx] " Jason Gunthorpe
2021-07-20 17:42   ` Jason Gunthorpe
2021-07-23  7:44   ` Christoph Hellwig
2021-07-23  7:44     ` [Intel-gfx] " Christoph Hellwig
2021-07-23 12:22     ` Jason Gunthorpe
2021-07-23 12:22       ` [Intel-gfx] " Jason Gunthorpe
2021-07-23 12:22       ` Jason Gunthorpe
2021-07-23 12:29       ` Christoph Hellwig
2021-07-23 12:29         ` [Intel-gfx] " Christoph Hellwig
2021-07-23 13:11         ` Jason Gunthorpe
2021-07-23 13:11           ` [Intel-gfx] " Jason Gunthorpe
2021-07-23 13:11           ` Jason Gunthorpe
2021-07-20 17:42 ` [PATCH v2 07/14] vfio/platform: Use open_device() instead of open coding a refcnt scheme Jason Gunthorpe
2021-07-20 17:42   ` [Intel-gfx] " Jason Gunthorpe
2021-07-20 17:42   ` Jason Gunthorpe
2021-07-22 14:48   ` Cornelia Huck
2021-07-22 14:48     ` [Intel-gfx] " Cornelia Huck
2021-07-22 14:48     ` Cornelia Huck
2021-07-23  7:45   ` Christoph Hellwig
2021-07-23  7:45     ` [Intel-gfx] " Christoph Hellwig
2021-07-23 12:23     ` Jason Gunthorpe
2021-07-23 12:23       ` [Intel-gfx] " Jason Gunthorpe
2021-07-23 12:23       ` Jason Gunthorpe
2021-07-20 17:42 ` [PATCH v2 08/14] vfio/pci: Move to the device set infrastructure Jason Gunthorpe
2021-07-20 17:42   ` [Intel-gfx] " Jason Gunthorpe
2021-07-20 17:42   ` Jason Gunthorpe
2021-07-23  7:47   ` Christoph Hellwig
2021-07-23  7:47     ` [Intel-gfx] " Christoph Hellwig
2021-07-23 12:59     ` Jason Gunthorpe
2021-07-23 12:59       ` [Intel-gfx] " Jason Gunthorpe
2021-07-23 12:59       ` Jason Gunthorpe
2021-07-20 17:42 ` [PATCH v2 09/14] vfio/pci: Change vfio_pci_try_bus_reset() to use the dev_set Jason Gunthorpe
2021-07-20 17:42   ` [Intel-gfx] " Jason Gunthorpe
2021-07-20 17:42   ` Jason Gunthorpe
2021-07-23  8:05   ` Christoph Hellwig [this message]
2021-07-23  8:05     ` [Intel-gfx] " Christoph Hellwig
2021-07-23 13:30     ` Jason Gunthorpe
2021-07-23 13:30       ` [Intel-gfx] " Jason Gunthorpe
2021-07-23 13:30       ` Jason Gunthorpe
2021-07-20 17:42 ` [PATCH v2 10/14] vfio/pci: Reorganize VFIO_DEVICE_PCI_HOT_RESET to use the device set Jason Gunthorpe
2021-07-20 17:42   ` [Intel-gfx] " Jason Gunthorpe
2021-07-20 17:42   ` Jason Gunthorpe
2021-07-23  8:12   ` Christoph Hellwig
2021-07-23  8:12     ` [Intel-gfx] " Christoph Hellwig
2021-07-23 13:31     ` Jason Gunthorpe
2021-07-23 13:31       ` [Intel-gfx] " Jason Gunthorpe
2021-07-23 13:31       ` Jason Gunthorpe
2021-07-20 17:42 ` [PATCH v2 11/14] vfio/mbochs: Fix close when multiple device FDs are open Jason Gunthorpe
2021-07-20 17:42   ` [Intel-gfx] " Jason Gunthorpe
2021-07-20 17:42   ` Jason Gunthorpe
2021-07-23  8:13   ` Christoph Hellwig
2021-07-23  8:13     ` [Intel-gfx] " Christoph Hellwig
2021-07-20 17:42 ` [PATCH v2 12/14] vfio/ap,ccw: Fix open/close " Jason Gunthorpe
2021-07-20 17:42   ` [Intel-gfx] [PATCH v2 12/14] vfio/ap, ccw: " Jason Gunthorpe
2021-07-20 17:42   ` Jason Gunthorpe
2021-07-20 17:42 ` [PATCH v2 13/14] vfio/gvt: " Jason Gunthorpe
2021-07-20 17:42   ` [Intel-gfx] " Jason Gunthorpe
2021-07-20 17:42   ` Jason Gunthorpe
2021-07-23  8:14   ` Christoph Hellwig
2021-07-23  8:14     ` [Intel-gfx] " Christoph Hellwig
2021-07-20 17:43 ` [PATCH v2 14/14] vfio: Remove struct vfio_device_ops open/release Jason Gunthorpe
2021-07-20 17:43   ` [Intel-gfx] " Jason Gunthorpe
2021-07-20 17:43   ` Jason Gunthorpe
2021-07-23  8:14   ` Christoph Hellwig
2021-07-23  8:14     ` [Intel-gfx] " Christoph Hellwig
2021-07-20 17:55 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Provide core infrastructure for managing open/release (rev4) Patchwork
2021-07-20 17:59 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2021-07-20 18:25 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-07-20 19:53 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-07-20 22:22 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Provide core infrastructure for managing open/release (rev5) Patchwork
2021-07-23  9:41 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Provide core infrastructure for managing open/release (rev6) 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=20210723080543.GD2795@lst.de \
    --to=hch@lst.de \
    --cc=airlied@linux.ie \
    --cc=akrowiak@linux.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=ashok.raj@intel.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=corbet@lwn.net \
    --cc=daniel@ffwll.ch \
    --cc=diana.craciun@oss.nxp.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eric.auger@redhat.com \
    --cc=farman@linux.ibm.com \
    --cc=freude@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=jgg@nvidia.com \
    --cc=jjherne@linux.ibm.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=leonro@nvidia.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mgurtovoy@nvidia.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=oberpar@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=vneethv@linux.ibm.com \
    --cc=yishaih@nvidia.com \
    --cc=zhenyuw@linux.intel.com \
    --cc=zhi.a.wang@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.