Linux IOMMU Development
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: iommu@lists.linux.dev, linux-kselftest@vger.kernel.org
Cc: Lu Baolu <baolu.lu@linux.intel.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>
Subject: Re: [PATCH v8 00/19] Add iommufd physical device operations for replace and alloc hwpt
Date: Wed, 26 Jul 2023 10:37:14 -0300	[thread overview]
Message-ID: <ZMEhiuvv1tNQNdUW@nvidia.com> (raw)
In-Reply-To: <0-v8-6659224517ea+532-iommufd_alloc_jgg@nvidia.com>

On Mon, Jul 17, 2023 at 03:11:56PM -0300, Jason Gunthorpe wrote:
> This is the basic functionality for iommufd to support
> iommufd_device_replace() and IOMMU_HWPT_ALLOC for physical devices.
> 
> iommufd_device_replace() allows changing the HWPT associated with the
> device to a new IOAS or HWPT. Replace does this in way that failure leaves
> things unchanged, and utilizes the iommu iommu_group_replace_domain() API
> to allow the iommu driver to perform an optional non-disruptive change.
> 
> IOMMU_HWPT_ALLOC allows HWPTs to be explicitly allocated by the user and
> used by attach or replace. At this point it isn't very useful since the
> HWPT is the same as the automatically managed HWPT from the IOAS. However
> a following series will allow userspace to customize the created HWPT.
> 
> The implementation is complicated because we have to introduce some
> per-iommu_group memory in iommufd and redo how we think about multi-device
> groups to be more explicit. This solves all the locking problems in the
> prior attempts.
> 
> This series is infrastructure work for the following series which:
>  - Add replace for attach
>  - Expose replace through VFIO APIs
>  - Implement driver parameters for HWPT creation (nesting)
> 
> Once review of this is complete I will keep it on a side branch and
> accumulate the following series when they are ready so we can have a
> stable base and make more incremental progress. When we have all the parts
> together to get a full implementation it can go to Linus.
> 
> This is on github: https://github.com/jgunthorpe/linux/commits/iommufd_hwpt

> Jason Gunthorpe (17):
>   iommufd: Move isolated msi enforcement to iommufd_device_bind()
>   iommufd: Add iommufd_group
>   iommufd: Replace the hwpt->devices list with iommufd_group
>   iommu: Export iommu_get_resv_regions()
>   iommufd: Keep track of each device's reserved regions instead of
>     groups
>   iommufd: Use the iommufd_group to avoid duplicate MSI setup
>   iommufd: Make sw_msi_start a group global
>   iommufd: Move putting a hwpt to a helper function
>   iommufd: Add enforced_cache_coherency to iommufd_hw_pagetable_alloc()
>   iommufd: Allow a hwpt to be aborted after allocation
>   iommufd: Fix locking around hwpt allocation
>   iommufd: Reorganize iommufd_device_attach into
>     iommufd_device_change_pt
>   iommufd: Add iommufd_device_replace()
>   iommufd: Make destroy_rwsem use a lock class per object type
>   iommufd: Add IOMMU_HWPT_ALLOC
>   iommufd/selftest: Return the real idev id from selftest mock_domain
>   iommufd/selftest: Add a selftest for IOMMU_HWPT_ALLOC
> 
> Nicolin Chen (2):
>   iommu: Introduce a new iommu_group_replace_domain() API
>   iommufd/selftest: Test iommufd_device_replace()

Applied to iommufd for-next, I fixed up the conflicts with the cdev series

Thanks,
Jason

      parent reply	other threads:[~2023-07-26 13:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 18:11 [PATCH v8 00/19] Add iommufd physical device operations for replace and alloc hwpt Jason Gunthorpe
2023-07-17 18:11 ` [PATCH v8 01/19] iommufd: Move isolated msi enforcement to iommufd_device_bind() Jason Gunthorpe
2023-07-17 18:11 ` [PATCH v8 02/19] iommufd: Add iommufd_group Jason Gunthorpe
2023-07-17 18:11 ` [PATCH v8 03/19] iommufd: Replace the hwpt->devices list with iommufd_group Jason Gunthorpe
2023-07-17 18:12 ` [PATCH v8 04/19] iommu: Export iommu_get_resv_regions() Jason Gunthorpe
2023-07-17 18:12 ` [PATCH v8 05/19] iommufd: Keep track of each device's reserved regions instead of groups Jason Gunthorpe
2023-07-17 18:12 ` [PATCH v8 06/19] iommufd: Use the iommufd_group to avoid duplicate MSI setup Jason Gunthorpe
2023-07-17 18:12 ` [PATCH v8 07/19] iommufd: Make sw_msi_start a group global Jason Gunthorpe
2023-07-17 18:12 ` [PATCH v8 08/19] iommufd: Move putting a hwpt to a helper function Jason Gunthorpe
2023-07-17 18:12 ` [PATCH v8 09/19] iommufd: Add enforced_cache_coherency to iommufd_hw_pagetable_alloc() Jason Gunthorpe
2023-07-17 18:12 ` [PATCH v8 10/19] iommufd: Allow a hwpt to be aborted after allocation Jason Gunthorpe
2023-07-17 18:12 ` [PATCH v8 11/19] iommufd: Fix locking around hwpt allocation Jason Gunthorpe
2023-07-17 18:12 ` [PATCH v8 12/19] iommufd: Reorganize iommufd_device_attach into iommufd_device_change_pt Jason Gunthorpe
2023-07-17 18:12 ` [PATCH v8 13/19] iommu: Introduce a new iommu_group_replace_domain() API Jason Gunthorpe
2023-07-17 18:12 ` [PATCH v8 14/19] iommufd: Add iommufd_device_replace() Jason Gunthorpe
2023-07-17 18:12 ` [PATCH v8 15/19] iommufd: Make destroy_rwsem use a lock class per object type Jason Gunthorpe
2023-07-17 18:12 ` [PATCH v8 16/19] iommufd/selftest: Test iommufd_device_replace() Jason Gunthorpe
2023-07-17 18:12 ` [PATCH v8 17/19] iommufd: Add IOMMU_HWPT_ALLOC Jason Gunthorpe
2023-07-17 18:12 ` [PATCH v8 18/19] iommufd/selftest: Return the real idev id from selftest mock_domain Jason Gunthorpe
2023-07-17 18:12 ` [PATCH v8 19/19] iommufd/selftest: Add a selftest for IOMMU_HWPT_ALLOC Jason Gunthorpe
2023-07-26 13:37 ` 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=ZMEhiuvv1tNQNdUW@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=lixiao.yang@intel.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=nicolinc@nvidia.com \
    --cc=yi.l.liu@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