All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yi Liu <yi.l.liu@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>,
	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>
Cc: Nicolin Chen <nicolinc@nvidia.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: Fri, 11 Nov 2022 12:12:36 +0800	[thread overview]
Message-ID: <5d50d507-6cd9-5f38-23d4-85f784cb8609@intel.com> (raw)
In-Reply-To: <7-v2-65016290f146+33e-vfio_iommufd_jgg@nvidia.com>

On 2022/11/8 08:52, Jason Gunthorpe wrote:
> This creates the iommufd_device for the physical VFIO drivers. These are
> all the drivers that are calling vfio_register_group_dev() and expect the
> type1 code to setup a real iommu_domain against their parent struct
> device.
> 
> The design gives the driver a choice in how it gets connected to iommufd
> by providing bind_iommufd/unbind_iommufd/attach_ioas callbacks to
> implement as required. The core code provides three default callbacks for
> physical mode using a real iommu_domain. This is suitable for drivers
> using vfio_register_group_dev()
> 
> Tested-by: Nicolin Chen <nicolinc@nvidia.com>
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> ---
>   drivers/vfio/Makefile                         |  1 +
>   drivers/vfio/fsl-mc/vfio_fsl_mc.c             |  3 +
>   drivers/vfio/iommufd.c                        | 99 +++++++++++++++++++
>   .../vfio/pci/hisilicon/hisi_acc_vfio_pci.c    |  6 ++
>   drivers/vfio/pci/mlx5/main.c                  |  3 +
>   drivers/vfio/pci/vfio_pci.c                   |  3 +
>   drivers/vfio/platform/vfio_amba.c             |  3 +
>   drivers/vfio/platform/vfio_platform.c         |  3 +
>   drivers/vfio/vfio.h                           | 15 +++
>   drivers/vfio/vfio_main.c                      | 13 ++-
>   include/linux/vfio.h                          | 25 +++++
>   11 files changed, 172 insertions(+), 2 deletions(-)
>   create mode 100644 drivers/vfio/iommufd.c
> 
> diff --git a/drivers/vfio/Makefile b/drivers/vfio/Makefile
> index b693a1169286f8..3863922529ef20 100644
> --- a/drivers/vfio/Makefile
> +++ b/drivers/vfio/Makefile
> @@ -6,6 +6,7 @@ obj-$(CONFIG_VFIO) += vfio.o
>   vfio-y += vfio_main.o \
>   	  iova_bitmap.o \
>   	  container.o
> +vfio-$(CONFIG_IOMMUFD) += iommufd.o
>   
>   obj-$(CONFIG_VFIO_VIRQFD) += vfio_virqfd.o
>   obj-$(CONFIG_VFIO_IOMMU_TYPE1) += vfio_iommu_type1.o
> diff --git a/drivers/vfio/fsl-mc/vfio_fsl_mc.c b/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> index b16874e913e4f5..5cd4bb47644039 100644
> --- a/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> +++ b/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> @@ -592,6 +592,9 @@ static const struct vfio_device_ops vfio_fsl_mc_ops = {
>   	.read		= vfio_fsl_mc_read,
>   	.write		= vfio_fsl_mc_write,
>   	.mmap		= vfio_fsl_mc_mmap,
> +	.bind_iommufd	= vfio_iommufd_physical_bind,
> +	.unbind_iommufd	= vfio_iommufd_physical_unbind,
> +	.attach_ioas	= vfio_iommufd_physical_attach_ioas,
>   };
>   
>   static struct fsl_mc_driver vfio_fsl_mc_driver = {
> diff --git a/drivers/vfio/iommufd.c b/drivers/vfio/iommufd.c
> new file mode 100644
> index 00000000000000..bf755d0f375c5d
> --- /dev/null
> +++ b/drivers/vfio/iommufd.c
> @@ -0,0 +1,99 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * Copyright (c) 2021-2022, NVIDIA CORPORATION & AFFILIATES
> + */
> +#include <linux/vfio.h>
> +#include <linux/iommufd.h>
> +
> +#include "vfio.h"
> +
> +MODULE_IMPORT_NS(IOMMUFD);
> +MODULE_IMPORT_NS(IOMMUFD_VFIO);
> +
> +int vfio_iommufd_bind(struct vfio_device *vdev, struct iommufd_ctx *ictx)
> +{
> +	u32 ioas_id;
> +	u32 device_id;
> +	int ret;
> +
> +	lockdep_assert_held(&vdev->dev_set->lock);
> +
> +	/*
> +	 * If the driver doesn't provide this op then it means the device does
> +	 * not do DMA at all. So nothing to do.
> +	 */
> +	if (!vdev->ops->bind_iommufd)
> +		return 0;
> +
> +	ret = vdev->ops->bind_iommufd(vdev, ictx, &device_id);
> +	if (ret)
> +		return ret;
> +
> +	ret = iommufd_vfio_compat_ioas_id(ictx, &ioas_id);
> +	if (ret)
> +		goto err_unbind;
> +	ret = vdev->ops->attach_ioas(vdev, &ioas_id);
> +	if (ret)
> +		goto err_unbind;
> +	vdev->iommufd_attached = true;

it's better to set this bool in vfio_iommufd_physical_attach_ioas() as
the emulated devices uses iommufd_access instead. is it? or you mean this
flag to cover both cases?
  --
Regards,
Yi Liu

WARNING: multiple messages have this Message-ID (diff)
From: Yi Liu <yi.l.liu@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>,
	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>
Cc: Lu Baolu <baolu.lu@linux.intel.com>, Nicolin Chen <nicolinc@nvidia.com>
Subject: Re: [PATCH v2 07/11] vfio-iommufd: Support iommufd for physical VFIO devices
Date: Fri, 11 Nov 2022 12:12:36 +0800	[thread overview]
Message-ID: <5d50d507-6cd9-5f38-23d4-85f784cb8609@intel.com> (raw)
In-Reply-To: <7-v2-65016290f146+33e-vfio_iommufd_jgg@nvidia.com>

On 2022/11/8 08:52, Jason Gunthorpe wrote:
> This creates the iommufd_device for the physical VFIO drivers. These are
> all the drivers that are calling vfio_register_group_dev() and expect the
> type1 code to setup a real iommu_domain against their parent struct
> device.
> 
> The design gives the driver a choice in how it gets connected to iommufd
> by providing bind_iommufd/unbind_iommufd/attach_ioas callbacks to
> implement as required. The core code provides three default callbacks for
> physical mode using a real iommu_domain. This is suitable for drivers
> using vfio_register_group_dev()
> 
> Tested-by: Nicolin Chen <nicolinc@nvidia.com>
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> ---
>   drivers/vfio/Makefile                         |  1 +
>   drivers/vfio/fsl-mc/vfio_fsl_mc.c             |  3 +
>   drivers/vfio/iommufd.c                        | 99 +++++++++++++++++++
>   .../vfio/pci/hisilicon/hisi_acc_vfio_pci.c    |  6 ++
>   drivers/vfio/pci/mlx5/main.c                  |  3 +
>   drivers/vfio/pci/vfio_pci.c                   |  3 +
>   drivers/vfio/platform/vfio_amba.c             |  3 +
>   drivers/vfio/platform/vfio_platform.c         |  3 +
>   drivers/vfio/vfio.h                           | 15 +++
>   drivers/vfio/vfio_main.c                      | 13 ++-
>   include/linux/vfio.h                          | 25 +++++
>   11 files changed, 172 insertions(+), 2 deletions(-)
>   create mode 100644 drivers/vfio/iommufd.c
> 
> diff --git a/drivers/vfio/Makefile b/drivers/vfio/Makefile
> index b693a1169286f8..3863922529ef20 100644
> --- a/drivers/vfio/Makefile
> +++ b/drivers/vfio/Makefile
> @@ -6,6 +6,7 @@ obj-$(CONFIG_VFIO) += vfio.o
>   vfio-y += vfio_main.o \
>   	  iova_bitmap.o \
>   	  container.o
> +vfio-$(CONFIG_IOMMUFD) += iommufd.o
>   
>   obj-$(CONFIG_VFIO_VIRQFD) += vfio_virqfd.o
>   obj-$(CONFIG_VFIO_IOMMU_TYPE1) += vfio_iommu_type1.o
> diff --git a/drivers/vfio/fsl-mc/vfio_fsl_mc.c b/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> index b16874e913e4f5..5cd4bb47644039 100644
> --- a/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> +++ b/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> @@ -592,6 +592,9 @@ static const struct vfio_device_ops vfio_fsl_mc_ops = {
>   	.read		= vfio_fsl_mc_read,
>   	.write		= vfio_fsl_mc_write,
>   	.mmap		= vfio_fsl_mc_mmap,
> +	.bind_iommufd	= vfio_iommufd_physical_bind,
> +	.unbind_iommufd	= vfio_iommufd_physical_unbind,
> +	.attach_ioas	= vfio_iommufd_physical_attach_ioas,
>   };
>   
>   static struct fsl_mc_driver vfio_fsl_mc_driver = {
> diff --git a/drivers/vfio/iommufd.c b/drivers/vfio/iommufd.c
> new file mode 100644
> index 00000000000000..bf755d0f375c5d
> --- /dev/null
> +++ b/drivers/vfio/iommufd.c
> @@ -0,0 +1,99 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * Copyright (c) 2021-2022, NVIDIA CORPORATION & AFFILIATES
> + */
> +#include <linux/vfio.h>
> +#include <linux/iommufd.h>
> +
> +#include "vfio.h"
> +
> +MODULE_IMPORT_NS(IOMMUFD);
> +MODULE_IMPORT_NS(IOMMUFD_VFIO);
> +
> +int vfio_iommufd_bind(struct vfio_device *vdev, struct iommufd_ctx *ictx)
> +{
> +	u32 ioas_id;
> +	u32 device_id;
> +	int ret;
> +
> +	lockdep_assert_held(&vdev->dev_set->lock);
> +
> +	/*
> +	 * If the driver doesn't provide this op then it means the device does
> +	 * not do DMA at all. So nothing to do.
> +	 */
> +	if (!vdev->ops->bind_iommufd)
> +		return 0;
> +
> +	ret = vdev->ops->bind_iommufd(vdev, ictx, &device_id);
> +	if (ret)
> +		return ret;
> +
> +	ret = iommufd_vfio_compat_ioas_id(ictx, &ioas_id);
> +	if (ret)
> +		goto err_unbind;
> +	ret = vdev->ops->attach_ioas(vdev, &ioas_id);
> +	if (ret)
> +		goto err_unbind;
> +	vdev->iommufd_attached = true;

it's better to set this bool in vfio_iommufd_physical_attach_ioas() as
the emulated devices uses iommufd_access instead. is it? or you mean this
flag to cover both cases?
  --
Regards,
Yi Liu

WARNING: multiple messages have this Message-ID (diff)
From: Yi Liu <yi.l.liu@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>,
	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>
Cc: Nicolin Chen <nicolinc@nvidia.com>, Lu Baolu <baolu.lu@linux.intel.com>
Subject: Re: [PATCH v2 07/11] vfio-iommufd: Support iommufd for physical VFIO devices
Date: Fri, 11 Nov 2022 12:12:36 +0800	[thread overview]
Message-ID: <5d50d507-6cd9-5f38-23d4-85f784cb8609@intel.com> (raw)
In-Reply-To: <7-v2-65016290f146+33e-vfio_iommufd_jgg@nvidia.com>

On 2022/11/8 08:52, Jason Gunthorpe wrote:
> This creates the iommufd_device for the physical VFIO drivers. These are
> all the drivers that are calling vfio_register_group_dev() and expect the
> type1 code to setup a real iommu_domain against their parent struct
> device.
> 
> The design gives the driver a choice in how it gets connected to iommufd
> by providing bind_iommufd/unbind_iommufd/attach_ioas callbacks to
> implement as required. The core code provides three default callbacks for
> physical mode using a real iommu_domain. This is suitable for drivers
> using vfio_register_group_dev()
> 
> Tested-by: Nicolin Chen <nicolinc@nvidia.com>
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> ---
>   drivers/vfio/Makefile                         |  1 +
>   drivers/vfio/fsl-mc/vfio_fsl_mc.c             |  3 +
>   drivers/vfio/iommufd.c                        | 99 +++++++++++++++++++
>   .../vfio/pci/hisilicon/hisi_acc_vfio_pci.c    |  6 ++
>   drivers/vfio/pci/mlx5/main.c                  |  3 +
>   drivers/vfio/pci/vfio_pci.c                   |  3 +
>   drivers/vfio/platform/vfio_amba.c             |  3 +
>   drivers/vfio/platform/vfio_platform.c         |  3 +
>   drivers/vfio/vfio.h                           | 15 +++
>   drivers/vfio/vfio_main.c                      | 13 ++-
>   include/linux/vfio.h                          | 25 +++++
>   11 files changed, 172 insertions(+), 2 deletions(-)
>   create mode 100644 drivers/vfio/iommufd.c
> 
> diff --git a/drivers/vfio/Makefile b/drivers/vfio/Makefile
> index b693a1169286f8..3863922529ef20 100644
> --- a/drivers/vfio/Makefile
> +++ b/drivers/vfio/Makefile
> @@ -6,6 +6,7 @@ obj-$(CONFIG_VFIO) += vfio.o
>   vfio-y += vfio_main.o \
>   	  iova_bitmap.o \
>   	  container.o
> +vfio-$(CONFIG_IOMMUFD) += iommufd.o
>   
>   obj-$(CONFIG_VFIO_VIRQFD) += vfio_virqfd.o
>   obj-$(CONFIG_VFIO_IOMMU_TYPE1) += vfio_iommu_type1.o
> diff --git a/drivers/vfio/fsl-mc/vfio_fsl_mc.c b/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> index b16874e913e4f5..5cd4bb47644039 100644
> --- a/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> +++ b/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> @@ -592,6 +592,9 @@ static const struct vfio_device_ops vfio_fsl_mc_ops = {
>   	.read		= vfio_fsl_mc_read,
>   	.write		= vfio_fsl_mc_write,
>   	.mmap		= vfio_fsl_mc_mmap,
> +	.bind_iommufd	= vfio_iommufd_physical_bind,
> +	.unbind_iommufd	= vfio_iommufd_physical_unbind,
> +	.attach_ioas	= vfio_iommufd_physical_attach_ioas,
>   };
>   
>   static struct fsl_mc_driver vfio_fsl_mc_driver = {
> diff --git a/drivers/vfio/iommufd.c b/drivers/vfio/iommufd.c
> new file mode 100644
> index 00000000000000..bf755d0f375c5d
> --- /dev/null
> +++ b/drivers/vfio/iommufd.c
> @@ -0,0 +1,99 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * Copyright (c) 2021-2022, NVIDIA CORPORATION & AFFILIATES
> + */
> +#include <linux/vfio.h>
> +#include <linux/iommufd.h>
> +
> +#include "vfio.h"
> +
> +MODULE_IMPORT_NS(IOMMUFD);
> +MODULE_IMPORT_NS(IOMMUFD_VFIO);
> +
> +int vfio_iommufd_bind(struct vfio_device *vdev, struct iommufd_ctx *ictx)
> +{
> +	u32 ioas_id;
> +	u32 device_id;
> +	int ret;
> +
> +	lockdep_assert_held(&vdev->dev_set->lock);
> +
> +	/*
> +	 * If the driver doesn't provide this op then it means the device does
> +	 * not do DMA at all. So nothing to do.
> +	 */
> +	if (!vdev->ops->bind_iommufd)
> +		return 0;
> +
> +	ret = vdev->ops->bind_iommufd(vdev, ictx, &device_id);
> +	if (ret)
> +		return ret;
> +
> +	ret = iommufd_vfio_compat_ioas_id(ictx, &ioas_id);
> +	if (ret)
> +		goto err_unbind;
> +	ret = vdev->ops->attach_ioas(vdev, &ioas_id);
> +	if (ret)
> +		goto err_unbind;
> +	vdev->iommufd_attached = true;

it's better to set this bool in vfio_iommufd_physical_attach_ioas() as
the emulated devices uses iommufd_access instead. is it? or you mean this
flag to cover both cases?
  --
Regards,
Yi Liu

  parent reply	other threads:[~2022-11-11  4:12 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
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   ` Yi Liu [this message]
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=5d50d507-6cd9-5f38-23d4-85f784cb8609@intel.com \
    --to=yi.l.liu@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=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=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.