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: Nicolin Chen <nicolinc@nvidia.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	David Airlie <airlied@gmail.com>,
	Tony Krowiak <akrowiak@linux.ibm.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Cornelia Huck <cohuck@redhat.com>,
	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, iommu@lists.linux.dev,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Jason Herne <jjherne@linux.ibm.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Joerg Roedel <joro@8bytes.org>, Kevin Tian <kevin.tian@intel.com>,
	kvm@vger.kernel.org, linux-s390@vger.kernel.org,
	Longfang Liu <liulongfang@huawei.com>,
	Matthew Rosato <mjrosato@linux.ibm.com>,
	Peter Oberparleiter <oberpar@linux.ibm.com>,
	Halil Pasic <pasic@linux.ibm.com>,
	Robin Murphy <robin.murphy@arm.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
	Sven Schnelle <svens@linux.ibm.com>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	Vineeth Vijayan <vneethv@linux.ibm.com>,
	Will Deacon <will@kernel.org>, Yishai Hadas <yishaih@nvidia.com>,
	Zhenyu Wang <zhenyuw@linux.intel.com>,
	Zhi Wang <zhi.a.wang@intel.com>,
	Lu Baolu <baolu.lu@linux.intel.com>
Subject: Re: [PATCH v2 07/11] vfio-iommufd: Support iommufd for physical VFIO devices
Date: Tue, 8 Nov 2022 13:51:49 -0400	[thread overview]
Message-ID: <Y2qXNcqXtAVkmXGN@nvidia.com> (raw)
In-Reply-To: <78d1994d-f6ac-7d1e-7d00-4a98c309bc5b@intel.com>

On Tue, Nov 08, 2022 at 03:41:25PM +0800, Yi Liu wrote:
> On 2022/11/8 14:10, Nicolin Chen wrote:
> > On Mon, Nov 07, 2022 at 08:52:51PM -0400, Jason Gunthorpe wrote:
> > 
> > > @@ -795,6 +800,10 @@ static int vfio_device_first_open(struct vfio_device *device)
> > >   		ret = vfio_group_use_container(device->group);
> > >   		if (ret)
> > >   			goto err_module_put;
> > > +	} else if (device->group->iommufd) {
> > > +		ret = vfio_iommufd_bind(device, device->group->iommufd);
> > 
> > Here we check device->group->iommufd...
> > 
> > > +		if (ret)
> > > +			goto err_module_put;
> > >   	}
> > >   	device->kvm = device->group->kvm;
> > > @@ -812,6 +821,7 @@ static int vfio_device_first_open(struct vfio_device *device)
> > >   	device->kvm = NULL;
> > >   	if (device->group->container)
> > >   		vfio_group_unuse_container(device->group);
> > > +	vfio_iommufd_unbind(device);
> > 
> > ...yet, missing here, which could result in kernel oops.
> > 
> > Should probably add something similar:
> > +	if (device->group->iommufd)
> > +		vfio_iommufd_unbind(device);
> > 
> > Or should check !vdev->iommufd_device inside the ->unbind.
> 
> this check was in prior version, but removed in this version. any
> special reason? Jason?

Oooh, this makes more sense - Kevin pointed out the check was wrong:

> > +void vfio_iommufd_unbind(struct vfio_device *vdev)
> > +{
> > +	lockdep_assert_held(&vdev->dev_set->lock);
> > +
> > +	if (!vdev->iommufd_device)
> > +		return;

> there is no iommufd_device in the emulated path...

And he is right, so I dropped it. But really the check was just
misspelled, it was supposed to be "device->group->iommufd" because the
caller assumed it.

Still, I think the right way to fix it is to lift the check as we
don't touch group->iommufd in iommufd.c

Thanks,
Jason

WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Yi Liu <yi.l.liu@intel.com>
Cc: kvm@vger.kernel.org, Kevin Tian <kevin.tian@intel.com>,
	dri-devel@lists.freedesktop.org,
	Vineeth Vijayan <vneethv@linux.ibm.com>,
	Diana Craciun <diana.craciun@oss.nxp.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Longfang Liu <liulongfang@huawei.com>,
	linux-s390@vger.kernel.org,
	Matthew Rosato <mjrosato@linux.ibm.com>,
	Will Deacon <will@kernel.org>, Joerg Roedel <joro@8bytes.org>,
	Halil Pasic <pasic@linux.ibm.com>,
	iommu@lists.linux.dev, Nicolin Chen <nicolinc@nvidia.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	intel-gfx@lists.freedesktop.org, Zhi Wang <zhi.a.wang@intel.com>,
	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>,
	Alex Williamson <alex.williamson@redhat.com>,
	Harald Freudenberger <freude@linux.ibm.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	intel-gvt-dev@lists.freedesktop.org,
	Tony Krowiak <akrowiak@linux.ibm.com>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	Yishai Hadas <yishaih@nvidia.com>,
	Cornelia Huck <cohuck@redhat.com>,
	Peter Oberparleiter <oberpar@linux.ibm.com>,
	Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
	Sven Schnelle <svens@linux.ibm.com>,
	Robin Murphy <robin.murphy@arm.com>,
	Lu Baolu <baolu.lu@linux.intel.com>
Subject: Re: [PATCH v2 07/11] vfio-iommufd: Support iommufd for physical VFIO devices
Date: Tue, 8 Nov 2022 13:51:49 -0400	[thread overview]
Message-ID: <Y2qXNcqXtAVkmXGN@nvidia.com> (raw)
In-Reply-To: <78d1994d-f6ac-7d1e-7d00-4a98c309bc5b@intel.com>

On Tue, Nov 08, 2022 at 03:41:25PM +0800, Yi Liu wrote:
> On 2022/11/8 14:10, Nicolin Chen wrote:
> > On Mon, Nov 07, 2022 at 08:52:51PM -0400, Jason Gunthorpe wrote:
> > 
> > > @@ -795,6 +800,10 @@ static int vfio_device_first_open(struct vfio_device *device)
> > >   		ret = vfio_group_use_container(device->group);
> > >   		if (ret)
> > >   			goto err_module_put;
> > > +	} else if (device->group->iommufd) {
> > > +		ret = vfio_iommufd_bind(device, device->group->iommufd);
> > 
> > Here we check device->group->iommufd...
> > 
> > > +		if (ret)
> > > +			goto err_module_put;
> > >   	}
> > >   	device->kvm = device->group->kvm;
> > > @@ -812,6 +821,7 @@ static int vfio_device_first_open(struct vfio_device *device)
> > >   	device->kvm = NULL;
> > >   	if (device->group->container)
> > >   		vfio_group_unuse_container(device->group);
> > > +	vfio_iommufd_unbind(device);
> > 
> > ...yet, missing here, which could result in kernel oops.
> > 
> > Should probably add something similar:
> > +	if (device->group->iommufd)
> > +		vfio_iommufd_unbind(device);
> > 
> > Or should check !vdev->iommufd_device inside the ->unbind.
> 
> this check was in prior version, but removed in this version. any
> special reason? Jason?

Oooh, this makes more sense - Kevin pointed out the check was wrong:

> > +void vfio_iommufd_unbind(struct vfio_device *vdev)
> > +{
> > +	lockdep_assert_held(&vdev->dev_set->lock);
> > +
> > +	if (!vdev->iommufd_device)
> > +		return;

> there is no iommufd_device in the emulated path...

And he is right, so I dropped it. But really the check was just
misspelled, it was supposed to be "device->group->iommufd" because the
caller assumed it.

Still, I think the right way to fix it is to lift the check as we
don't touch group->iommufd in iommufd.c

Thanks,
Jason

WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Yi Liu <yi.l.liu@intel.com>
Cc: kvm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Vineeth Vijayan <vneethv@linux.ibm.com>,
	Diana Craciun <diana.craciun@oss.nxp.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	David Airlie <airlied@gmail.com>,
	Longfang Liu <liulongfang@huawei.com>,
	linux-s390@vger.kernel.org,
	Matthew Rosato <mjrosato@linux.ibm.com>,
	Will Deacon <will@kernel.org>, Joerg Roedel <joro@8bytes.org>,
	Halil Pasic <pasic@linux.ibm.com>,
	iommu@lists.linux.dev, Nicolin Chen <nicolinc@nvidia.com>,
	Christian Borntraeger <borntraeger@linux.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>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	intel-gvt-dev@lists.freedesktop.org,
	Tony Krowiak <akrowiak@linux.ibm.com>,
	Yishai Hadas <yishaih@nvidia.com>,
	Cornelia Huck <cohuck@redhat.com>,
	Peter Oberparleiter <oberpar@linux.ibm.com>,
	Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
	Sven Schnelle <svens@linux.ibm.com>,
	Daniel Vetter <daniel@ffwll.ch>,
	Robin Murphy <robin.murphy@arm.com>,
	Lu Baolu <baolu.lu@linux.intel.com>
Subject: Re: [Intel-gfx] [PATCH v2 07/11] vfio-iommufd: Support iommufd for physical VFIO devices
Date: Tue, 8 Nov 2022 13:51:49 -0400	[thread overview]
Message-ID: <Y2qXNcqXtAVkmXGN@nvidia.com> (raw)
In-Reply-To: <78d1994d-f6ac-7d1e-7d00-4a98c309bc5b@intel.com>

On Tue, Nov 08, 2022 at 03:41:25PM +0800, Yi Liu wrote:
> On 2022/11/8 14:10, Nicolin Chen wrote:
> > On Mon, Nov 07, 2022 at 08:52:51PM -0400, Jason Gunthorpe wrote:
> > 
> > > @@ -795,6 +800,10 @@ static int vfio_device_first_open(struct vfio_device *device)
> > >   		ret = vfio_group_use_container(device->group);
> > >   		if (ret)
> > >   			goto err_module_put;
> > > +	} else if (device->group->iommufd) {
> > > +		ret = vfio_iommufd_bind(device, device->group->iommufd);
> > 
> > Here we check device->group->iommufd...
> > 
> > > +		if (ret)
> > > +			goto err_module_put;
> > >   	}
> > >   	device->kvm = device->group->kvm;
> > > @@ -812,6 +821,7 @@ static int vfio_device_first_open(struct vfio_device *device)
> > >   	device->kvm = NULL;
> > >   	if (device->group->container)
> > >   		vfio_group_unuse_container(device->group);
> > > +	vfio_iommufd_unbind(device);
> > 
> > ...yet, missing here, which could result in kernel oops.
> > 
> > Should probably add something similar:
> > +	if (device->group->iommufd)
> > +		vfio_iommufd_unbind(device);
> > 
> > Or should check !vdev->iommufd_device inside the ->unbind.
> 
> this check was in prior version, but removed in this version. any
> special reason? Jason?

Oooh, this makes more sense - Kevin pointed out the check was wrong:

> > +void vfio_iommufd_unbind(struct vfio_device *vdev)
> > +{
> > +	lockdep_assert_held(&vdev->dev_set->lock);
> > +
> > +	if (!vdev->iommufd_device)
> > +		return;

> there is no iommufd_device in the emulated path...

And he is right, so I dropped it. But really the check was just
misspelled, it was supposed to be "device->group->iommufd" because the
caller assumed it.

Still, I think the right way to fix it is to lift the check as we
don't touch group->iommufd in iommufd.c

Thanks,
Jason

  reply	other threads:[~2022-11-08 17:51 UTC|newest]

Thread overview: 170+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08  0:52 [PATCH v2 00/11] Connect VFIO to IOMMUFD Jason Gunthorpe
2022-11-08  0:52 ` Jason Gunthorpe
2022-11-08  0:52 ` [Intel-gfx] " Jason Gunthorpe
2022-11-08  0:52 ` [PATCH v2 01/11] vfio: Move vfio_device driver open/close code to a function Jason Gunthorpe
2022-11-08  0:52   ` [Intel-gfx] " Jason Gunthorpe
2022-11-08  0:52   ` Jason Gunthorpe
2022-11-08  0:52 ` [PATCH v2 02/11] vfio: Move vfio_device_assign_container() into vfio_device_first_open() Jason Gunthorpe
2022-11-08  0:52   ` [Intel-gfx] " Jason Gunthorpe
2022-11-08  0:52   ` Jason Gunthorpe
2022-11-08  0:52 ` [PATCH v2 03/11] vfio: Rename vfio_device_assign/unassign_container() Jason Gunthorpe
2022-11-08  0:52   ` Jason Gunthorpe
2022-11-08  0:52   ` [Intel-gfx] " Jason Gunthorpe
2022-11-08  0:52 ` [PATCH v2 04/11] vfio: Move storage of allow_unsafe_interrupts to vfio_main.c Jason Gunthorpe
2022-11-08  0:52   ` [Intel-gfx] " Jason Gunthorpe
2022-11-08  0:52   ` Jason Gunthorpe
2022-11-08  0:52 ` [PATCH v2 05/11] vfio: Use IOMMU_CAP_ENFORCE_CACHE_COHERENCY for vfio_file_enforced_coherent() Jason Gunthorpe
2022-11-08  0:52   ` [Intel-gfx] " Jason Gunthorpe
2022-11-08  0:52   ` Jason Gunthorpe
2022-11-10  2:48   ` Tian, Kevin
2022-11-10  2:48     ` Tian, Kevin
2022-11-10  2:48     ` [Intel-gfx] " Tian, Kevin
2022-11-08  0:52 ` [PATCH v2 06/11] vfio-iommufd: Allow iommufd to be used in place of a container fd Jason Gunthorpe
2022-11-08  0:52   ` [Intel-gfx] " Jason Gunthorpe
2022-11-08  0:52   ` Jason Gunthorpe
2022-11-10  2:51   ` Tian, Kevin
2022-11-10  2:51     ` [Intel-gfx] " Tian, Kevin
2022-11-10  2:51     ` Tian, Kevin
2022-11-08  0:52 ` [PATCH v2 07/11] vfio-iommufd: Support iommufd for physical VFIO devices Jason Gunthorpe
2022-11-08  0:52   ` Jason Gunthorpe
2022-11-08  0:52   ` [Intel-gfx] " Jason Gunthorpe
2022-11-08  6:10   ` Nicolin Chen
2022-11-08  6:10     ` [Intel-gfx] " Nicolin Chen
2022-11-08  6:10     ` Nicolin Chen
2022-11-08  7:41     ` Yi Liu
2022-11-08  7:41       ` [Intel-gfx] " Yi Liu
2022-11-08  7:41       ` Yi Liu
2022-11-08 17:51       ` Jason Gunthorpe [this message]
2022-11-08 17:51         ` [Intel-gfx] " Jason Gunthorpe
2022-11-08 17:51         ` Jason Gunthorpe
2022-11-10  3:12         ` Tian, Kevin
2022-11-10  3:12           ` Tian, Kevin
2022-11-10  3:12           ` [Intel-gfx] " Tian, Kevin
2022-11-08 17:48     ` Jason Gunthorpe
2022-11-08 17:48       ` [Intel-gfx] " Jason Gunthorpe
2022-11-08 17:48       ` Jason Gunthorpe
2022-11-10  3:11   ` Tian, Kevin
2022-11-10  3:11     ` [Intel-gfx] " Tian, Kevin
2022-11-10  3:11     ` Tian, Kevin
2022-11-10 17:20     ` Jason Gunthorpe
2022-11-10 17:20       ` [Intel-gfx] " Jason Gunthorpe
2022-11-10 17:20       ` Jason Gunthorpe
2022-11-10 23:58       ` Tian, Kevin
2022-11-10 23:58         ` [Intel-gfx] " Tian, Kevin
2022-11-10 23:58         ` Tian, Kevin
2022-11-11  4:12   ` [Intel-gfx] " Yi Liu
2022-11-11  4:12     ` Yi Liu
2022-11-11  4:12     ` Yi Liu
2022-11-14 14:47     ` Jason Gunthorpe
2022-11-14 14:47       ` [Intel-gfx] " Jason Gunthorpe
2022-11-14 14:47       ` Jason Gunthorpe
2022-11-08  0:52 ` [PATCH v2 08/11] vfio-iommufd: Support iommufd for emulated " Jason Gunthorpe
2022-11-08  0:52   ` [Intel-gfx] " Jason Gunthorpe
2022-11-08  0:52   ` Jason Gunthorpe
2022-11-10  5:33   ` Tian, Kevin
2022-11-10  5:33     ` [Intel-gfx] " Tian, Kevin
2022-11-10  5:33     ` Tian, Kevin
2022-11-08  0:52 ` [PATCH v2 09/11] vfio: Move container related MODULE_ALIAS statements into container.c Jason Gunthorpe
2022-11-08  0:52   ` [Intel-gfx] " Jason Gunthorpe
2022-11-08  0:52   ` Jason Gunthorpe
2022-11-10  5:34   ` Tian, Kevin
2022-11-10  5:34     ` [Intel-gfx] " Tian, Kevin
2022-11-10  5:34     ` Tian, Kevin
2022-11-11  4:13   ` Yi Liu
2022-11-11  4:13     ` [Intel-gfx] " Yi Liu
2022-11-11  4:13     ` Yi Liu
2022-11-08  0:52 ` [PATCH v2 10/11] vfio: Make vfio_container optionally compiled Jason Gunthorpe
2022-11-08  0:52   ` [Intel-gfx] " Jason Gunthorpe
2022-11-08  0:52   ` Jason Gunthorpe
2022-11-08 22:28   ` Alex Williamson
2022-11-08 22:28     ` [Intel-gfx] " Alex Williamson
2022-11-08 22:28     ` Alex Williamson
2022-11-09  0:54     ` Jason Gunthorpe
2022-11-09  0:54       ` [Intel-gfx] " Jason Gunthorpe
2022-11-09  0:54       ` Jason Gunthorpe
2022-11-09 17:18       ` Alex Williamson
2022-11-09 17:18         ` [Intel-gfx] " Alex Williamson
2022-11-09 17:18         ` Alex Williamson
2022-11-09 19:52         ` Jason Gunthorpe
2022-11-09 19:52           ` [Intel-gfx] " Jason Gunthorpe
2022-11-09 19:52           ` Jason Gunthorpe
2022-11-10  6:57           ` Tian, Kevin
2022-11-10  6:57             ` [Intel-gfx] " Tian, Kevin
2022-11-10  6:57             ` Tian, Kevin
2022-11-10 17:10             ` Alex Williamson
2022-11-10 17:10               ` [Intel-gfx] " Alex Williamson
2022-11-10 17:10               ` Alex Williamson
2022-11-10 17:52             ` Jason Gunthorpe
2022-11-10 17:52               ` [Intel-gfx] " Jason Gunthorpe
2022-11-10 17:52               ` Jason Gunthorpe
2022-11-08  0:52 ` [PATCH v2 11/11] iommufd: Allow iommufd to supply /dev/vfio/vfio Jason Gunthorpe
2022-11-08  0:52   ` Jason Gunthorpe
2022-11-08  0:52   ` [Intel-gfx] " Jason Gunthorpe
2022-11-10  7:01   ` Tian, Kevin
2022-11-10  7:01     ` Tian, Kevin
2022-11-10  7:01     ` [Intel-gfx] " Tian, Kevin
2022-11-11  4:16   ` Yi Liu
2022-11-11  4:16     ` [Intel-gfx] " Yi Liu
2022-11-11  4:16     ` Yi Liu
2022-11-11  6:38     ` Yi Liu
2022-11-11  6:38       ` [Intel-gfx] " Yi Liu
2022-11-11  6:38       ` Yi Liu
2022-11-14 14:50     ` Jason Gunthorpe
2022-11-14 14:50       ` [Intel-gfx] " Jason Gunthorpe
2022-11-14 14:50       ` Jason Gunthorpe
2022-11-08  1:27 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Connect VFIO to IOMMUFD (rev3) Patchwork
2022-11-08  9:19 ` [PATCH v2 00/11] Connect VFIO to IOMMUFD Nicolin Chen
2022-11-08  9:19   ` [Intel-gfx] " Nicolin Chen
2022-11-08  9:19   ` Nicolin Chen
2022-11-08 15:18   ` Yi Liu
2022-11-08 15:18     ` [Intel-gfx] " Yi Liu
2022-11-08 15:18     ` Yi Liu
2022-11-09 16:57     ` Jason Gunthorpe
2022-11-09 16:57       ` [Intel-gfx] " Jason Gunthorpe
2022-11-09 16:57       ` Jason Gunthorpe
2022-11-14 12:51       ` Yi Liu
2022-11-14 12:51         ` [Intel-gfx] " Yi Liu
2022-11-14 12:51         ` Yi Liu
2022-11-14 14:37         ` Yang, Lixiao
2022-11-14 14:37           ` [Intel-gfx] " Yang, Lixiao
2022-11-14 14:37           ` Yang, Lixiao
2022-11-15  5:41           ` He, Yu
2022-11-15  5:41             ` [Intel-gfx] " He, Yu
2022-11-15  5:41             ` He, Yu
2022-11-14 14:38         ` Jason Gunthorpe
2022-11-14 14:38           ` [Intel-gfx] " Jason Gunthorpe
2022-11-14 14:38           ` Jason Gunthorpe
2022-11-14 14:42           ` Yi Liu
2022-11-14 14:42             ` Yi Liu
2022-11-14 14:42             ` [Intel-gfx] " Yi Liu
2022-11-15  1:16       ` Matthew Rosato
2022-11-15  1:16         ` [Intel-gfx] " Matthew Rosato
2022-11-15  1:16         ` Matthew Rosato
2022-11-09  9:03 ` Tian, Kevin
2022-11-09  9:03   ` [Intel-gfx] " Tian, Kevin
2022-11-09  9:03   ` Tian, Kevin
2022-11-09 12:48   ` Jason Gunthorpe
2022-11-09 12:48     ` [Intel-gfx] " Jason Gunthorpe
2022-11-09 12:48     ` Jason Gunthorpe
2022-11-10  2:16     ` Tian, Kevin
2022-11-10  2:16       ` [Intel-gfx] " Tian, Kevin
2022-11-10  2:16       ` Tian, Kevin
2022-11-11  3:01 ` Matthew Rosato
2022-11-11  3:01   ` [Intel-gfx] " Matthew Rosato
2022-11-11  3:01   ` Matthew Rosato
2022-11-14 14:23   ` Jason Gunthorpe
2022-11-14 14:23     ` [Intel-gfx] " Jason Gunthorpe
2022-11-14 14:23     ` Jason Gunthorpe
2022-11-14 14:55     ` Matthew Rosato
2022-11-14 14:55       ` [Intel-gfx] " Matthew Rosato
2022-11-14 14:55       ` Matthew Rosato
2022-11-14 14:59       ` Jason Gunthorpe
2022-11-14 14:59         ` [Intel-gfx] " Jason Gunthorpe
2022-11-14 14:59         ` Jason Gunthorpe
2022-11-14 15:21         ` Matthew Rosato
2022-11-14 15:21           ` [Intel-gfx] " Matthew Rosato
2022-11-14 15:21           ` Matthew Rosato
2022-11-14 19:27           ` Jason Gunthorpe
2022-11-14 19:27             ` [Intel-gfx] " Jason Gunthorpe
2022-11-14 19:27             ` Jason Gunthorpe
2022-11-11  4:06 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Connect VFIO to IOMMUFD (rev5) 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=Y2qXNcqXtAVkmXGN@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=agordeev@linux.ibm.com \
    --cc=airlied@gmail.com \
    --cc=akrowiak@linux.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=cohuck@redhat.com \
    --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=iommu@lists.linux.dev \
    --cc=jani.nikula@linux.intel.com \
    --cc=jjherne@linux.ibm.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=liulongfang@huawei.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=nicolinc@nvidia.com \
    --cc=oberpar@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=robin.murphy@arm.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=svens@linux.ibm.com \
    --cc=tvrtko.ursulin@linux.intel.com \
    --cc=vneethv@linux.ibm.com \
    --cc=will@kernel.org \
    --cc=yi.l.liu@intel.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.