public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Lu Baolu <baolu.lu@linux.intel.com>,
	Cornelia Huck <cohuck@redhat.com>,
	Eric Auger <eric.auger@redhat.com>,
	Kevin Tian <kevin.tian@intel.com>,
	kvm@vger.kernel.org, Lixiao Yang <lixiao.yang@intel.com>,
	Matthew Rosato <mjrosato@linux.ibm.com>,
	Nicolin Chen <nicolinc@nvidia.com>, Yi Liu <yi.l.liu@intel.com>,
	Yu He <yu.he@intel.com>
Subject: Re: [PATCH v4 00/10] Connect VFIO to IOMMUFD
Date: Wed, 30 Nov 2022 13:34:55 -0700	[thread overview]
Message-ID: <20221130133455.3f8ef495.alex.williamson@redhat.com> (raw)
In-Reply-To: <0-v4-42cd2eb0e3eb+335a-vfio_iommufd_jgg@nvidia.com>

On Tue, 29 Nov 2022 16:31:45 -0400
Jason Gunthorpe <jgg@nvidia.com> wrote:

> [ As with the iommufd series, this will be the last posting unless
> something major happens, futher fixes will be in new commits ]
> 
> This series provides an alternative container layer for VFIO implemented
> using iommufd. This is optional, if CONFIG_IOMMUFD is not set then it will
> not be compiled in.
> 
> At this point iommufd can be injected by passing in a iommfd FD to
> VFIO_GROUP_SET_CONTAINER which will use the VFIO compat layer in iommufd
> to obtain the compat IOAS and then connect up all the VFIO drivers as
> appropriate.
> 
> This is temporary stopping point, a following series will provide a way to
> directly open a VFIO device FD and directly connect it to IOMMUFD using
> native ioctls that can expose the IOMMUFD features like hwpt, future
> vPASID and dynamic attachment.
> 
> This series, in compat mode, has passed all the qemu tests we have
> available, including the test suites for the Intel GVT mdev. Aside from
> the temporary limitation with P2P memory this is belived to be fully
> compatible with VFIO.
> 
> This is on github: https://github.com/jgunthorpe/linux/commits/vfio_iommufd
> 
> It requires the iommufd series:
> 
> https://lore.kernel.org/r/0-v6-a196d26f289e+11787-iommufd_jgg@nvidia.com
> 
> v4:
>  - Change the assertion in vfio_group_has_iommu to be clearer
>  - Use vfio_group_has_iommu()
>  - Remove allow_unsafe_interrupts stuff
>  - Update IOMMUFD_VFIO_CONTAINER kconfig description
>  - Use DEBUG_KERNEL insted of RUNTIME_TESTING_MENU for IOMMUFD_TEST kconfig

This looks ok to me and passes all my testing.  What's your merge plan?
I'm guessing you'd like to send it along with the main IOMMUFD pull
request, there are currently no conflicts with my next branch,
therefore:

Reviewed-by: Alex Williamson <alex.williamson@redhat.com>
Tested-by: Alex Williamson <alex.williamson@redhat.com>

Otherwise, let's figure out the branch merge plan.  Thanks,

Alex


  parent reply	other threads:[~2022-11-30 20:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 20:31 [PATCH v4 00/10] Connect VFIO to IOMMUFD Jason Gunthorpe
2022-11-29 20:31 ` [PATCH v4 01/10] vfio: Move vfio_device driver open/close code to a function Jason Gunthorpe
2022-11-29 20:31 ` [PATCH v4 02/10] vfio: Move vfio_device_assign_container() into vfio_device_first_open() Jason Gunthorpe
2022-11-29 20:31 ` [PATCH v4 03/10] vfio: Rename vfio_device_assign/unassign_container() Jason Gunthorpe
2022-11-29 20:31 ` [PATCH v4 04/10] vfio: Use IOMMU_CAP_ENFORCE_CACHE_COHERENCY for vfio_file_enforced_coherent() Jason Gunthorpe
2022-11-29 20:31 ` [PATCH v4 05/10] vfio-iommufd: Allow iommufd to be used in place of a container fd Jason Gunthorpe
2022-11-29 20:31 ` [PATCH v4 06/10] vfio-iommufd: Support iommufd for physical VFIO devices Jason Gunthorpe
2022-11-29 20:31 ` [PATCH v4 07/10] vfio-iommufd: Support iommufd for emulated " Jason Gunthorpe
2022-11-29 20:31 ` [PATCH v4 08/10] vfio: Move container related MODULE_ALIAS statements into container.c Jason Gunthorpe
2022-11-29 20:31 ` [PATCH v4 09/10] vfio: Make vfio_container optionally compiled Jason Gunthorpe
2022-11-29 20:31 ` [PATCH v4 10/10] iommufd: Allow iommufd to supply /dev/vfio/vfio Jason Gunthorpe
2022-11-30 20:34 ` Alex Williamson [this message]
2022-12-01  0:44   ` [PATCH v4 00/10] Connect VFIO to IOMMUFD Jason Gunthorpe

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=20221130133455.3f8ef495.alex.williamson@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=cohuck@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=lixiao.yang@intel.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=nicolinc@nvidia.com \
    --cc=yi.l.liu@intel.com \
    --cc=yu.he@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox