All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tian, Kevin" <kevin.tian@intel.com>
To: Jason Gunthorpe <jgg@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"
	<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-gfx@lists.freedesktop.org>,
	"intel-gvt-dev@lists.freedesktop.org" 
	<intel-gvt-dev@lists.freedesktop.org>,
	"iommu@lists.linux.dev" <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>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-s390@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>,
	"Vivi, Rodrigo" <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>,
	"Wang, Zhi A" <zhi.a.wang@intel.com>
Cc: Lu Baolu <baolu.lu@linux.intel.com>,
	Nicolin Chen <nicolinc@nvidia.com>,
	"Liu, Yi L" <yi.l.liu@intel.com>
Subject: RE: [PATCH 08/10] vfio-iommufd: Support iommufd for emulated VFIO devices
Date: Tue, 1 Nov 2022 08:37:39 +0000	[thread overview]
Message-ID: <BN9PR11MB5276B6ACAE7E511770887BF38C369@BN9PR11MB5276.namprd11.prod.outlook.com> (raw)
In-Reply-To: <8-v1-4991695894d8+211-vfio_iommufd_jgg@nvidia.com>

> From: Jason Gunthorpe <jgg@nvidia.com>
> Sent: Wednesday, October 26, 2022 2:51 AM
> 
> Emulated VFIO devices are calling vfio_register_emulated_iommu_dev() and
> consist of all the mdev drivers.
> 
> Like the physical drivers, support for iommufd is provided by the driver
> supplying the correct correct standard ops. Provide ops from the core that
> duplicate what vfio_register_emulated_iommu_dev() does.
> 
> Emulated drivers are where it is more likely to see variation in the
> iommfd support ops. For instance IDXD will probably need to setup both a
> iommfd_device context linked to a PASID and an iommufd_access context to
> support all their mdev operations.
> 
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> ---
>  drivers/gpu/drm/i915/gvt/kvmgt.c  |   3 +
>  drivers/s390/cio/vfio_ccw_ops.c   |   3 +
>  drivers/s390/crypto/vfio_ap_ops.c |   3 +
>  drivers/vfio/container.c          | 108 ++++++-----------------------
>  drivers/vfio/iommufd.c            |  57 ++++++++++++++++
>  drivers/vfio/vfio.h               |  10 ++-
>  drivers/vfio/vfio_main.c          | 110 +++++++++++++++++++++++++++++-
>  include/linux/vfio.h              |  14 ++++
>  8 files changed, 217 insertions(+), 91 deletions(-)

mtty, mdpy and mbochs?

> diff --git a/drivers/vfio/container.c b/drivers/vfio/container.c
> index 8772dad6808539..0388f2e33447eb 100644
> --- a/drivers/vfio/container.c
> +++ b/drivers/vfio/container.c
> @@ -540,113 +540,45 @@ void vfio_group_unuse_container(struct
> vfio_group *group)
>  	fput(group->opened_file);
>  }
> 
> -/*
> - * Pin contiguous user pages and return their associated host pages for local
> - * domain only.
> - * @device [in]  : device
> - * @iova [in]    : starting IOVA of user pages to be pinned.
> - * @npage [in]   : count of pages to be pinned.  This count should not
> - *		   be greater than VFIO_PIN_PAGES_MAX_ENTRIES.
> - * @prot [in]    : protection flags
> - * @pages[out]   : array of host pages
> - * Return error or number of pages pinned.
> - *
> - * A driver may only call this function if the vfio_device was created
> - * by vfio_register_emulated_iommu_dev().
> - */
> -int vfio_pin_pages(struct vfio_device *device, dma_addr_t iova,
> -		   int npage, int prot, struct page **pages)
> +int vfio_container_pin_pages(struct vfio_container *container,
> +			     struct iommu_group *iommu_group, dma_addr_t
> iova,
> +			     int npage, int prot, struct page **pages)
>  {
> -	struct vfio_container *container;
> -	struct vfio_group *group = device->group;
> -	struct vfio_iommu_driver *driver;
> -	int ret;
> -
> -	if (!pages || !npage || !vfio_assert_device_open(device))
> -		return -EINVAL;
> +	/* group->container cannot change while a vfio device is open */
> +	struct vfio_iommu_driver *driver = container->iommu_driver;
> 
>  	if (npage > VFIO_PIN_PAGES_MAX_ENTRIES)
>  		return -E2BIG;
> 
>  	/* group->container cannot change while a vfio device is open */
> -	container = group->container;
>  	driver = container->iommu_driver;

duplicated comment and assignment.

Actually, I'm not sure whether the comment should be put within this
container helper and other two. There is no group reference in these
helpers then it sounds like the comment makes more sense to be in the
caller side?

> +void vfio_unpin_pages(struct vfio_device *device, dma_addr_t iova, int
> npage)
> +{
> +	if (WARN_ON(!vfio_assert_device_open(device)))
> +		return;
> +
> +	if (device->group->container) {
> +		vfio_container_unpin_pages(device->group->container, iova,
> +					   npage);
> +	} else if (device->iommufd_access) {

be consistent with other two helpers i.e. if-if instead of if-else

> +		if (WARN_ON(iova > ULONG_MAX))
> +			return;

Is there a reason why this is a WARN_ON only in unpin but not in pin?

> +int vfio_dma_rw(struct vfio_device *device, dma_addr_t iova, void *data,
> +		size_t len, bool write)
> +{
> +	if (!data || len <= 0 || !vfio_assert_device_open(device))
> +		return -EINVAL;
> +
> +	if (device->group->container)
> +		return vfio_container_dma_rw(device->group->container,
> iova,
> +					     data, len, write);
> +
> +	if (device->iommufd_access) {
> +		unsigned int flags = 0;
> +
> +		if (iova > ULONG_MAX)
> +			return -EINVAL;
> +
> +		/* VFIO historically tries to auto-detect a kthread */
> +		if (!current->mm)
> +			flags |= IOMMUFD_ACCESS_RW_KTHREAD;

Can you elaborate why this cannot be put in iommufd as the default
policy similar to what vfio container does?


WARNING: multiple messages have this Message-ID (diff)
From: "Tian, Kevin" <kevin.tian@intel.com>
To: Jason Gunthorpe <jgg@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"
	<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-gfx@lists.freedesktop.org>,
	"intel-gvt-dev@lists.freedesktop.org"
	<intel-gvt-dev@lists.freedesktop.org>,
	"iommu@lists.linux.dev" <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>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-s390@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>,
	"Vivi, Rodrigo" <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>,
	"Wang, Zhi A" <zhi.a.wang@intel.com>
Cc: "Liu, Yi L" <yi.l.liu@intel.com>,
	Nicolin Chen <nicolinc@nvidia.com>,
	Lu Baolu <baolu.lu@linux.intel.com>
Subject: RE: [PATCH 08/10] vfio-iommufd: Support iommufd for emulated VFIO devices
Date: Tue, 1 Nov 2022 08:37:39 +0000	[thread overview]
Message-ID: <BN9PR11MB5276B6ACAE7E511770887BF38C369@BN9PR11MB5276.namprd11.prod.outlook.com> (raw)
In-Reply-To: <8-v1-4991695894d8+211-vfio_iommufd_jgg@nvidia.com>

> From: Jason Gunthorpe <jgg@nvidia.com>
> Sent: Wednesday, October 26, 2022 2:51 AM
> 
> Emulated VFIO devices are calling vfio_register_emulated_iommu_dev() and
> consist of all the mdev drivers.
> 
> Like the physical drivers, support for iommufd is provided by the driver
> supplying the correct correct standard ops. Provide ops from the core that
> duplicate what vfio_register_emulated_iommu_dev() does.
> 
> Emulated drivers are where it is more likely to see variation in the
> iommfd support ops. For instance IDXD will probably need to setup both a
> iommfd_device context linked to a PASID and an iommufd_access context to
> support all their mdev operations.
> 
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> ---
>  drivers/gpu/drm/i915/gvt/kvmgt.c  |   3 +
>  drivers/s390/cio/vfio_ccw_ops.c   |   3 +
>  drivers/s390/crypto/vfio_ap_ops.c |   3 +
>  drivers/vfio/container.c          | 108 ++++++-----------------------
>  drivers/vfio/iommufd.c            |  57 ++++++++++++++++
>  drivers/vfio/vfio.h               |  10 ++-
>  drivers/vfio/vfio_main.c          | 110 +++++++++++++++++++++++++++++-
>  include/linux/vfio.h              |  14 ++++
>  8 files changed, 217 insertions(+), 91 deletions(-)

mtty, mdpy and mbochs?

> diff --git a/drivers/vfio/container.c b/drivers/vfio/container.c
> index 8772dad6808539..0388f2e33447eb 100644
> --- a/drivers/vfio/container.c
> +++ b/drivers/vfio/container.c
> @@ -540,113 +540,45 @@ void vfio_group_unuse_container(struct
> vfio_group *group)
>  	fput(group->opened_file);
>  }
> 
> -/*
> - * Pin contiguous user pages and return their associated host pages for local
> - * domain only.
> - * @device [in]  : device
> - * @iova [in]    : starting IOVA of user pages to be pinned.
> - * @npage [in]   : count of pages to be pinned.  This count should not
> - *		   be greater than VFIO_PIN_PAGES_MAX_ENTRIES.
> - * @prot [in]    : protection flags
> - * @pages[out]   : array of host pages
> - * Return error or number of pages pinned.
> - *
> - * A driver may only call this function if the vfio_device was created
> - * by vfio_register_emulated_iommu_dev().
> - */
> -int vfio_pin_pages(struct vfio_device *device, dma_addr_t iova,
> -		   int npage, int prot, struct page **pages)
> +int vfio_container_pin_pages(struct vfio_container *container,
> +			     struct iommu_group *iommu_group, dma_addr_t
> iova,
> +			     int npage, int prot, struct page **pages)
>  {
> -	struct vfio_container *container;
> -	struct vfio_group *group = device->group;
> -	struct vfio_iommu_driver *driver;
> -	int ret;
> -
> -	if (!pages || !npage || !vfio_assert_device_open(device))
> -		return -EINVAL;
> +	/* group->container cannot change while a vfio device is open */
> +	struct vfio_iommu_driver *driver = container->iommu_driver;
> 
>  	if (npage > VFIO_PIN_PAGES_MAX_ENTRIES)
>  		return -E2BIG;
> 
>  	/* group->container cannot change while a vfio device is open */
> -	container = group->container;
>  	driver = container->iommu_driver;

duplicated comment and assignment.

Actually, I'm not sure whether the comment should be put within this
container helper and other two. There is no group reference in these
helpers then it sounds like the comment makes more sense to be in the
caller side?

> +void vfio_unpin_pages(struct vfio_device *device, dma_addr_t iova, int
> npage)
> +{
> +	if (WARN_ON(!vfio_assert_device_open(device)))
> +		return;
> +
> +	if (device->group->container) {
> +		vfio_container_unpin_pages(device->group->container, iova,
> +					   npage);
> +	} else if (device->iommufd_access) {

be consistent with other two helpers i.e. if-if instead of if-else

> +		if (WARN_ON(iova > ULONG_MAX))
> +			return;

Is there a reason why this is a WARN_ON only in unpin but not in pin?

> +int vfio_dma_rw(struct vfio_device *device, dma_addr_t iova, void *data,
> +		size_t len, bool write)
> +{
> +	if (!data || len <= 0 || !vfio_assert_device_open(device))
> +		return -EINVAL;
> +
> +	if (device->group->container)
> +		return vfio_container_dma_rw(device->group->container,
> iova,
> +					     data, len, write);
> +
> +	if (device->iommufd_access) {
> +		unsigned int flags = 0;
> +
> +		if (iova > ULONG_MAX)
> +			return -EINVAL;
> +
> +		/* VFIO historically tries to auto-detect a kthread */
> +		if (!current->mm)
> +			flags |= IOMMUFD_ACCESS_RW_KTHREAD;

Can you elaborate why this cannot be put in iommufd as the default
policy similar to what vfio container does?


WARNING: multiple messages have this Message-ID (diff)
From: "Tian, Kevin" <kevin.tian@intel.com>
To: Jason Gunthorpe <jgg@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"
	<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-gfx@lists.freedesktop.org>,
	"intel-gvt-dev@lists.freedesktop.org"
	<intel-gvt-dev@lists.freedesktop.org>,
	"iommu@lists.linux.dev" <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>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-s390@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>,
	"Vivi, Rodrigo" <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>,
	"Wang, Zhi A" <zhi.a.wang@intel.com>
Cc: "Liu, Yi L" <yi.l.liu@intel.com>,
	Nicolin Chen <nicolinc@nvidia.com>,
	Lu Baolu <baolu.lu@linux.intel.com>
Subject: Re: [Intel-gfx] [PATCH 08/10] vfio-iommufd: Support iommufd for emulated VFIO devices
Date: Tue, 1 Nov 2022 08:37:39 +0000	[thread overview]
Message-ID: <BN9PR11MB5276B6ACAE7E511770887BF38C369@BN9PR11MB5276.namprd11.prod.outlook.com> (raw)
In-Reply-To: <8-v1-4991695894d8+211-vfio_iommufd_jgg@nvidia.com>

> From: Jason Gunthorpe <jgg@nvidia.com>
> Sent: Wednesday, October 26, 2022 2:51 AM
> 
> Emulated VFIO devices are calling vfio_register_emulated_iommu_dev() and
> consist of all the mdev drivers.
> 
> Like the physical drivers, support for iommufd is provided by the driver
> supplying the correct correct standard ops. Provide ops from the core that
> duplicate what vfio_register_emulated_iommu_dev() does.
> 
> Emulated drivers are where it is more likely to see variation in the
> iommfd support ops. For instance IDXD will probably need to setup both a
> iommfd_device context linked to a PASID and an iommufd_access context to
> support all their mdev operations.
> 
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> ---
>  drivers/gpu/drm/i915/gvt/kvmgt.c  |   3 +
>  drivers/s390/cio/vfio_ccw_ops.c   |   3 +
>  drivers/s390/crypto/vfio_ap_ops.c |   3 +
>  drivers/vfio/container.c          | 108 ++++++-----------------------
>  drivers/vfio/iommufd.c            |  57 ++++++++++++++++
>  drivers/vfio/vfio.h               |  10 ++-
>  drivers/vfio/vfio_main.c          | 110 +++++++++++++++++++++++++++++-
>  include/linux/vfio.h              |  14 ++++
>  8 files changed, 217 insertions(+), 91 deletions(-)

mtty, mdpy and mbochs?

> diff --git a/drivers/vfio/container.c b/drivers/vfio/container.c
> index 8772dad6808539..0388f2e33447eb 100644
> --- a/drivers/vfio/container.c
> +++ b/drivers/vfio/container.c
> @@ -540,113 +540,45 @@ void vfio_group_unuse_container(struct
> vfio_group *group)
>  	fput(group->opened_file);
>  }
> 
> -/*
> - * Pin contiguous user pages and return their associated host pages for local
> - * domain only.
> - * @device [in]  : device
> - * @iova [in]    : starting IOVA of user pages to be pinned.
> - * @npage [in]   : count of pages to be pinned.  This count should not
> - *		   be greater than VFIO_PIN_PAGES_MAX_ENTRIES.
> - * @prot [in]    : protection flags
> - * @pages[out]   : array of host pages
> - * Return error or number of pages pinned.
> - *
> - * A driver may only call this function if the vfio_device was created
> - * by vfio_register_emulated_iommu_dev().
> - */
> -int vfio_pin_pages(struct vfio_device *device, dma_addr_t iova,
> -		   int npage, int prot, struct page **pages)
> +int vfio_container_pin_pages(struct vfio_container *container,
> +			     struct iommu_group *iommu_group, dma_addr_t
> iova,
> +			     int npage, int prot, struct page **pages)
>  {
> -	struct vfio_container *container;
> -	struct vfio_group *group = device->group;
> -	struct vfio_iommu_driver *driver;
> -	int ret;
> -
> -	if (!pages || !npage || !vfio_assert_device_open(device))
> -		return -EINVAL;
> +	/* group->container cannot change while a vfio device is open */
> +	struct vfio_iommu_driver *driver = container->iommu_driver;
> 
>  	if (npage > VFIO_PIN_PAGES_MAX_ENTRIES)
>  		return -E2BIG;
> 
>  	/* group->container cannot change while a vfio device is open */
> -	container = group->container;
>  	driver = container->iommu_driver;

duplicated comment and assignment.

Actually, I'm not sure whether the comment should be put within this
container helper and other two. There is no group reference in these
helpers then it sounds like the comment makes more sense to be in the
caller side?

> +void vfio_unpin_pages(struct vfio_device *device, dma_addr_t iova, int
> npage)
> +{
> +	if (WARN_ON(!vfio_assert_device_open(device)))
> +		return;
> +
> +	if (device->group->container) {
> +		vfio_container_unpin_pages(device->group->container, iova,
> +					   npage);
> +	} else if (device->iommufd_access) {

be consistent with other two helpers i.e. if-if instead of if-else

> +		if (WARN_ON(iova > ULONG_MAX))
> +			return;

Is there a reason why this is a WARN_ON only in unpin but not in pin?

> +int vfio_dma_rw(struct vfio_device *device, dma_addr_t iova, void *data,
> +		size_t len, bool write)
> +{
> +	if (!data || len <= 0 || !vfio_assert_device_open(device))
> +		return -EINVAL;
> +
> +	if (device->group->container)
> +		return vfio_container_dma_rw(device->group->container,
> iova,
> +					     data, len, write);
> +
> +	if (device->iommufd_access) {
> +		unsigned int flags = 0;
> +
> +		if (iova > ULONG_MAX)
> +			return -EINVAL;
> +
> +		/* VFIO historically tries to auto-detect a kthread */
> +		if (!current->mm)
> +			flags |= IOMMUFD_ACCESS_RW_KTHREAD;

Can you elaborate why this cannot be put in iommufd as the default
policy similar to what vfio container does?


  reply	other threads:[~2022-11-01  8:37 UTC|newest]

Thread overview: 206+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 18:17 [PATCH 00/10] Connect VFIO to IOMMUFD Jason Gunthorpe
2022-10-25 18:17 ` [Intel-gfx] " Jason Gunthorpe
2022-10-25 18:17 ` Jason Gunthorpe
2022-10-25 18:17 ` [PATCH 01/10] vfio: Move vfio_device driver open/close code to a function Jason Gunthorpe
2022-10-25 18:17   ` [Intel-gfx] " Jason Gunthorpe
2022-10-25 18:17   ` Jason Gunthorpe
2022-11-01  7:33   ` Tian, Kevin
2022-11-01  7:33     ` [Intel-gfx] " Tian, Kevin
2022-11-01  7:33     ` Tian, Kevin
2022-11-01 12:12     ` Jason Gunthorpe
2022-11-01 12:12       ` [Intel-gfx] " Jason Gunthorpe
2022-11-01 12:12       ` Jason Gunthorpe
2022-11-01 14:36   ` Yi Liu
2022-11-01 14:36     ` [Intel-gfx] " Yi Liu
2022-11-01 14:36     ` Yi Liu
2022-10-25 18:17 ` [PATCH 02/10] vfio: Move vfio_device_assign_container() into vfio_device_first_open() Jason Gunthorpe
2022-10-25 18:17   ` Jason Gunthorpe
2022-10-25 18:17   ` [Intel-gfx] " Jason Gunthorpe
2022-11-01  7:38   ` Tian, Kevin
2022-11-01  7:38     ` [Intel-gfx] " Tian, Kevin
2022-11-01  7:38     ` Tian, Kevin
2022-11-01 12:14     ` Jason Gunthorpe
2022-11-01 12:14       ` [Intel-gfx] " Jason Gunthorpe
2022-11-01 12:14       ` Jason Gunthorpe
2022-11-01 14:37   ` Yi Liu
2022-11-01 14:37     ` Yi Liu
2022-11-01 14:37     ` [Intel-gfx] " Yi Liu
2022-11-01 17:37     ` Jason Gunthorpe
2022-11-01 17:37       ` [Intel-gfx] " Jason Gunthorpe
2022-11-01 17:37       ` Jason Gunthorpe
2022-10-25 18:17 ` [PATCH 03/10] vfio: Rename vfio_device_assign/unassign_container() Jason Gunthorpe
2022-10-25 18:17   ` [Intel-gfx] " Jason Gunthorpe
2022-10-25 18:17   ` Jason Gunthorpe
2022-11-01  7:39   ` Tian, Kevin
2022-11-01  7:39     ` [Intel-gfx] " Tian, Kevin
2022-11-01  7:39     ` Tian, Kevin
2022-11-01 14:39   ` Yi Liu
2022-11-01 14:39     ` [Intel-gfx] " Yi Liu
2022-11-01 14:39     ` Yi Liu
2022-10-25 18:17 ` [PATCH 04/10] vfio: Move storage of allow_unsafe_interrupts to vfio_main.c Jason Gunthorpe
2022-10-25 18:17   ` [Intel-gfx] " Jason Gunthorpe
2022-10-25 18:17   ` Jason Gunthorpe
2022-10-26 21:24   ` Alex Williamson
2022-10-26 21:24     ` [Intel-gfx] " Alex Williamson
2022-10-26 21:24     ` Alex Williamson
2022-10-28 18:40     ` Jason Gunthorpe
2022-10-28 18:40       ` [Intel-gfx] " Jason Gunthorpe
2022-10-28 18:40       ` Jason Gunthorpe
2022-10-31 22:45       ` [Intel-gfx] " Alex Williamson
2022-10-31 22:45         ` Alex Williamson
2022-10-31 22:45         ` Alex Williamson
2022-11-07 13:19         ` Jason Gunthorpe
2022-11-07 13:19           ` [Intel-gfx] " Jason Gunthorpe
2022-11-07 13:19           ` Jason Gunthorpe
2022-11-07 15:18           ` Alex Williamson
2022-11-07 15:18             ` Alex Williamson
2022-11-07 15:18             ` [Intel-gfx] " Alex Williamson
2022-11-07 15:32             ` Jason Gunthorpe
2022-11-07 15:32               ` [Intel-gfx] " Jason Gunthorpe
2022-11-07 15:32               ` Jason Gunthorpe
2022-11-07 18:05               ` Alex Williamson
2022-11-07 18:05                 ` Alex Williamson
2022-11-07 18:05                 ` [Intel-gfx] " Alex Williamson
2022-11-07 18:45                 ` Jason Gunthorpe
2022-11-07 18:45                   ` [Intel-gfx] " Jason Gunthorpe
2022-11-07 18:45                   ` Jason Gunthorpe
2022-11-08 22:55                   ` Alex Williamson
2022-11-08 22:55                     ` [Intel-gfx] " Alex Williamson
2022-11-08 22:55                     ` Alex Williamson
2022-11-09  1:05                     ` Jason Gunthorpe
2022-11-09  1:05                       ` [Intel-gfx] " Jason Gunthorpe
2022-11-09  1:05                       ` Jason Gunthorpe
2022-11-09  3:21                       ` Tian, Kevin
2022-11-09  3:21                         ` [Intel-gfx] " Tian, Kevin
2022-11-09  3:21                         ` Tian, Kevin
2022-11-09 13:11                         ` Jason Gunthorpe
2022-11-09 13:11                           ` [Intel-gfx] " Jason Gunthorpe
2022-11-09 13:11                           ` Jason Gunthorpe
2022-11-10  2:44                           ` Tian, Kevin
2022-11-10  2:44                             ` [Intel-gfx] " Tian, Kevin
2022-11-10  2:44                             ` Tian, Kevin
2022-11-09 18:28                       ` Alex Williamson
2022-11-09 18:28                         ` [Intel-gfx] " Alex Williamson
2022-11-09 18:28                         ` Alex Williamson
2022-11-10 19:19                         ` Jason Gunthorpe
2022-11-10 19:19                           ` [Intel-gfx] " Jason Gunthorpe
2022-11-10 19:19                           ` Jason Gunthorpe
2022-10-25 18:17 ` [PATCH 05/10] vfio: Use IOMMU_CAP_ENFORCE_CACHE_COHERENCY for vfio_file_enforced_coherent() Jason Gunthorpe
2022-10-25 18:17   ` [Intel-gfx] " Jason Gunthorpe
2022-10-25 18:17   ` Jason Gunthorpe
2022-11-01  7:52   ` Tian, Kevin
2022-11-01  7:52     ` [Intel-gfx] " Tian, Kevin
2022-11-01  7:52     ` Tian, Kevin
2022-11-01 12:26     ` Jason Gunthorpe
2022-11-01 12:26       ` [Intel-gfx] " Jason Gunthorpe
2022-11-01 12:26       ` Jason Gunthorpe
2022-11-03  4:38       ` Tian, Kevin
2022-11-03  4:38         ` [Intel-gfx] " Tian, Kevin
2022-11-03  4:38         ` Tian, Kevin
2022-11-04 19:45         ` Jason Gunthorpe
2022-11-04 19:45           ` [Intel-gfx] " Jason Gunthorpe
2022-11-04 19:45           ` Jason Gunthorpe
2022-10-25 18:50 ` [PATCH 06/10] vfio-iommufd: Allow iommufd to be used in place of a container fd Jason Gunthorpe
2022-10-25 18:50   ` [Intel-gfx] " Jason Gunthorpe
2022-10-25 18:50   ` Jason Gunthorpe
2022-11-01  8:09   ` Tian, Kevin
2022-11-01  8:09     ` [Intel-gfx] " Tian, Kevin
2022-11-01  8:09     ` Tian, Kevin
2022-11-01  9:19     ` Nicolin Chen
2022-11-01  9:19       ` [Intel-gfx] " Nicolin Chen
2022-11-01  9:19       ` Nicolin Chen
2022-11-01 11:51       ` Jason Gunthorpe
2022-11-01 11:51         ` [Intel-gfx] " Jason Gunthorpe
2022-11-01 11:51         ` Jason Gunthorpe
2022-11-03  4:39         ` Tian, Kevin
2022-11-03  4:39           ` [Intel-gfx] " Tian, Kevin
2022-11-03  4:39           ` Tian, Kevin
2022-11-01 12:40     ` Jason Gunthorpe
2022-11-01 12:40       ` [Intel-gfx] " Jason Gunthorpe
2022-11-01 12:40       ` Jason Gunthorpe
2022-11-02  7:28   ` Yi Liu
2022-11-02  7:28     ` [Intel-gfx] " Yi Liu
2022-11-02  7:28     ` Yi Liu
2022-11-07 23:45     ` Jason Gunthorpe
2022-11-07 23:45       ` [Intel-gfx] " Jason Gunthorpe
2022-11-07 23:45       ` Jason Gunthorpe
2022-10-25 18:50 ` [PATCH 07/10] vfio-iommufd: Support iommufd for physical VFIO devices Jason Gunthorpe
2022-10-25 18:50   ` [Intel-gfx] " Jason Gunthorpe
2022-10-25 18:50   ` Jason Gunthorpe
2022-11-01  8:21   ` Tian, Kevin
2022-11-01  8:21     ` [Intel-gfx] " Tian, Kevin
2022-11-01  8:21     ` Tian, Kevin
2022-11-04 19:51     ` Jason Gunthorpe
2022-11-04 19:51       ` [Intel-gfx] " Jason Gunthorpe
2022-11-04 19:51       ` Jason Gunthorpe
2022-10-25 18:50 ` [PATCH 08/10] vfio-iommufd: Support iommufd for emulated " Jason Gunthorpe
2022-10-25 18:50   ` [Intel-gfx] " Jason Gunthorpe
2022-10-25 18:50   ` Jason Gunthorpe
2022-11-01  8:37   ` Tian, Kevin [this message]
2022-11-01  8:37     ` [Intel-gfx] " Tian, Kevin
2022-11-01  8:37     ` Tian, Kevin
2022-11-01 12:49     ` Jason Gunthorpe
2022-11-01 12:49       ` [Intel-gfx] " Jason Gunthorpe
2022-11-01 12:49       ` Jason Gunthorpe
2022-11-03  4:52       ` Tian, Kevin
2022-11-03  4:52         ` [Intel-gfx] " Tian, Kevin
2022-11-03  4:52         ` Tian, Kevin
2022-10-25 18:50 ` [PATCH 09/10] vfio: Make vfio_container optionally compiled Jason Gunthorpe
2022-10-25 18:50   ` [Intel-gfx] " Jason Gunthorpe
2022-10-25 18:50   ` Jason Gunthorpe
2022-11-01  8:41   ` Tian, Kevin
2022-11-01  8:41     ` [Intel-gfx] " Tian, Kevin
2022-11-01  8:41     ` Tian, Kevin
2022-11-01 12:56     ` Jason Gunthorpe
2022-11-01 12:56       ` [Intel-gfx] " Jason Gunthorpe
2022-11-01 12:56       ` Jason Gunthorpe
2022-10-25 18:50 ` [PATCH 10/10] iommufd: Allow iommufd to supply /dev/vfio/vfio Jason Gunthorpe
2022-10-25 18:50   ` [Intel-gfx] " Jason Gunthorpe
2022-10-25 18:50   ` Jason Gunthorpe
2022-10-26 21:31   ` Alex Williamson
2022-10-26 21:31     ` Alex Williamson
2022-10-26 21:31     ` [Intel-gfx] " Alex Williamson
2022-10-28 18:44     ` Jason Gunthorpe
2022-10-28 18:44       ` [Intel-gfx] " Jason Gunthorpe
2022-10-28 18:44       ` Jason Gunthorpe
2022-10-31 22:53       ` Alex Williamson
2022-10-31 22:53         ` [Intel-gfx] " Alex Williamson
2022-10-31 22:53         ` Alex Williamson
2022-11-07 13:57         ` Jason Gunthorpe
2022-11-07 13:57           ` [Intel-gfx] " Jason Gunthorpe
2022-11-07 13:57           ` Jason Gunthorpe
2022-10-25 20:42 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Connect VFIO to IOMMUFD Patchwork
2022-10-28 23:53 ` [PATCH 00/10] " Nicolin Chen
2022-10-28 23:53   ` [Intel-gfx] " Nicolin Chen
2022-10-28 23:53   ` Nicolin Chen
2022-10-28 23:54   ` Nicolin Chen
2022-10-28 23:54     ` [Intel-gfx] " Nicolin Chen
2022-10-28 23:54     ` Nicolin Chen
2022-10-31 10:38 ` Yi Liu
2022-10-31 10:38   ` [Intel-gfx] " Yi Liu
2022-10-31 10:38   ` Yi Liu
2022-10-31 12:18   ` [Intel-gfx] " Jason Gunthorpe
2022-10-31 12:18     ` Jason Gunthorpe
2022-10-31 12:18     ` Jason Gunthorpe
2022-10-31 12:25     ` Yi Liu
2022-10-31 12:25       ` [Intel-gfx] " Yi Liu
2022-10-31 12:25       ` Yi Liu
2022-10-31 23:24       ` Jason Gunthorpe
2022-10-31 23:24         ` [Intel-gfx] " Jason Gunthorpe
2022-10-31 23:24         ` Jason Gunthorpe
2022-11-01  3:04         ` Yi Liu
2022-11-01  3:04           ` Yi Liu
2022-11-01  3:04           ` [Intel-gfx] " Yi Liu
2022-11-01  4:21           ` Nicolin Chen
2022-11-01  4:21             ` [Intel-gfx] " Nicolin Chen
2022-11-01  4:21             ` Nicolin Chen
2022-11-01 12:54             ` Yi Liu
2022-11-01 12:54               ` [Intel-gfx] " Yi Liu
2022-11-01 12:54               ` Yi Liu
2022-11-01 11:41           ` Jason Gunthorpe
2022-11-01 11:41             ` [Intel-gfx] " Jason Gunthorpe
2022-11-01 11:41             ` Jason Gunthorpe
2022-11-01 12:55             ` Yi Liu
2022-11-01 12:55               ` Yi Liu
2022-11-01 12:55               ` [Intel-gfx] " Yi Liu
2022-11-07 17:17 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Connect VFIO to IOMMUFD (rev2) 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=BN9PR11MB5276B6ACAE7E511770887BF38C369@BN9PR11MB5276.namprd11.prod.outlook.com \
    --to=kevin.tian@intel.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=jgg@nvidia.com \
    --cc=jjherne@linux.ibm.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=joro@8bytes.org \
    --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.