From: Jason Gunthorpe <jgg@nvidia.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Alex Williamson <alex.williamson@redhat.com>,
Diana Craciun <diana.craciun@oss.nxp.com>,
Cornelia Huck <cohuck@redhat.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
Eric Auger <eric.auger@redhat.com>,
Terrence Xu <terrence.xu@intel.com>,
kvm@vger.kernel.org
Subject: Re: cleanup vfio iommu_group creation v5
Date: Wed, 15 Sep 2021 15:07:34 -0300 [thread overview]
Message-ID: <20210915180734.GA256807@nvidia.com> (raw)
In-Reply-To: <20210913071606.2966-1-hch@lst.de>
On Mon, Sep 13, 2021 at 09:15:52AM +0200, Christoph Hellwig wrote:
> Hi Alex,
>
> this series cleans up how iommu group are created in VFIO as well as
> various other lose ends around that.
>
> Terrence: I did not pick up your Tested-by as there were quite a few
> changes and a major rebase.
>
> Changes since v4:
> - clean up an intermediate version of vfio_group_find_or_alloc to avoid
> reviewer confusion
> - replace an incorrect NULL check with IS_ERR
> - rebased ontop of the vfio_ap_ops changes in Linux 5.15-rc
> - improve a commit message
This all still looks good to me, can we get it into your tree in the
early party of the rc cycle Alex? Due to the
vfio_register_emulated_iommu_dev() it conflicts with the vfio_ccw and
i915 mdev conversions patches - this should go first..
Thanks,
Jason
prev parent reply other threads:[~2021-09-15 18:07 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 7:15 cleanup vfio iommu_group creation v5 Christoph Hellwig
2021-09-13 7:15 ` [PATCH 01/14] vfio: Move vfio_iommu_group_get() to vfio_register_group_dev() Christoph Hellwig
2021-09-14 1:57 ` Tian, Kevin
2021-09-14 5:46 ` Christoph Hellwig
2021-09-14 6:11 ` Tian, Kevin
2021-09-13 7:15 ` [PATCH 02/14] vfio: factor out a vfio_iommu_driver_allowed helper Christoph Hellwig
2021-09-23 22:59 ` Alex Williamson
2021-09-13 7:15 ` [PATCH 03/14] vfio: remove the iommudata check in vfio_noiommu_attach_group Christoph Hellwig
2021-09-13 7:15 ` [PATCH 04/14] vfio: factor out a vfio_group_find_or_alloc helper Christoph Hellwig
2021-09-14 2:00 ` Tian, Kevin
2021-09-13 7:15 ` [PATCH 05/14] vfio: refactor noiommu group creation Christoph Hellwig
2021-09-14 2:07 ` Tian, Kevin
2021-09-13 7:15 ` [PATCH 06/14] vfio: remove the iommudata hack for noiommu groups Christoph Hellwig
2021-09-15 16:44 ` Jason Gunthorpe
2021-09-13 7:15 ` [PATCH 07/14] vfio: simplify iommu group allocation for mediated devices Christoph Hellwig
2021-09-14 2:23 ` Tian, Kevin
2021-09-13 7:16 ` [PATCH 08/14] vfio: remove unused method from vfio_iommu_driver_ops Christoph Hellwig
2021-09-13 7:16 ` [PATCH 09/14] vfio: move the vfio_iommu_driver_ops interface out of <linux/vfio.h> Christoph Hellwig
2021-09-13 7:16 ` [PATCH 10/14] vfio: remove the unused mdev iommu hook Christoph Hellwig
2021-09-13 7:16 ` [PATCH 11/14] vfio: clean up the check for mediated device in vfio_iommu_type1 Christoph Hellwig
2021-09-16 19:55 ` Kirti Wankhede
2021-09-16 22:18 ` Jason Gunthorpe
2021-09-17 4:49 ` Tian, Kevin
2021-09-17 5:05 ` Christoph Hellwig
2021-09-17 6:51 ` Kirti Wankhede
2021-09-17 12:53 ` Jason Gunthorpe
2021-09-30 16:46 ` Alex Williamson
2021-09-30 16:57 ` Jason Gunthorpe
2021-10-01 3:20 ` Christoph Hellwig
2021-09-13 7:16 ` [PATCH 12/14] vfio/spapr_tce: reject mediated devices Christoph Hellwig
2021-09-13 7:16 ` [PATCH 13/14] vfio/iommu_type1: remove the "external" domain Christoph Hellwig
2021-09-23 22:59 ` Alex Williamson
2021-09-23 23:06 ` Jason Gunthorpe
2021-09-13 7:16 ` [PATCH 14/14] vfio/iommu_type1: remove IS_IOMMU_CAP_DOMAIN_IN_CONTAINER Christoph Hellwig
2021-09-15 18:07 ` Jason Gunthorpe [this message]
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=20210915180734.GA256807@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=diana.craciun@oss.nxp.com \
--cc=eric.auger@redhat.com \
--cc=hch@lst.de \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=terrence.xu@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.