Linux IOMMU Development
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Yi Liu <yi.l.liu@intel.com>,
	joro@8bytes.org, jgg@nvidia.com, kevin.tian@intel.com
Cc: alex.williamson@redhat.com, eric.auger@redhat.com,
	nicolinc@nvidia.com, kvm@vger.kernel.org,
	chao.p.peng@linux.intel.com, iommu@lists.linux.dev,
	zhenzhong.duan@intel.com, vasant.hegde@amd.com,
	willy@infradead.org
Subject: Re: [PATCH v6 00/13] Make set_dev_pasid op supporting domain replacement
Date: Fri, 8 Nov 2024 10:12:01 +0800	[thread overview]
Message-ID: <b3d351dd-e75f-483f-be7d-0c0bcb1dec7a@linux.intel.com> (raw)
In-Reply-To: <20241107122234.7424-1-yi.l.liu@intel.com>

On 11/7/24 20:22, Yi Liu wrote:
> This splits the preparation works of the iommu and the Intel iommu driver
> out from the iommufd pasid attach/replace series. [1]
> 
> To support domain replacement, the definition of the set_dev_pasid op
> needs to be enhanced. Meanwhile, the existing set_dev_pasid callbacks
> should be extended as well to suit the new definition.
> 
> This series first passes the old domain to the set_dev_pasid op, and prepares
> the Intel iommu set_dev_pasid callbacks (paging domain, identity domain, and
> sva domain) for the new definition, add the missing set_dev_pasid callback
> for the nested domain, makes ARM SMMUv3 set_dev_pasid op to suit the new
> set_dev_pasid op definition, and in the end, claims the set_dev_pasid op support
> domain replacement. The AMD set_dev_pasid callback is extended to fail if the
> caller tries to do the domain replacement to meet the new definition of
> set_dev_pasid op. AMD iommu driver would support it later per Vasant [2].
> 
> [1]https://lore.kernel.org/linux-iommu/20240412081516.31168-1- 
> yi.l.liu@intel.com/
> [2]https://lore.kernel.org/linux-iommu/fa9c4fc3-9365-465e-8926- 
> b4d2d6361b9c@amd.com/
> 
> This is based on Joerg's next branch. Base commit: 75bc266cd1a6
> 
> v6:
>   - Fix a 0day compiling issue (Baolu)
>   - Refine the pasid replace helpers to compose new pasid entry and do a full
>     copy instead of setting each fields in the pasid entry from the pasid table.
>     This avoids transit the existing pasid entry multiple times. (Baolu)

Queued for v6.13. Thank you, Yi.

--
baolu

      parent reply	other threads:[~2024-11-08  2:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07 12:22 [PATCH v6 00/13] Make set_dev_pasid op supporting domain replacement Yi Liu
2024-11-07 12:22 ` [PATCH v6 01/13] iommu: Pass old domain to set_dev_pasid op Yi Liu
2024-11-07 12:22 ` [PATCH v6 02/13] iommu/vt-d: Add a helper to flush cache for updating present pasid entry Yi Liu
2024-11-07 12:22 ` [PATCH v6 03/13] iommu/vt-d: Refactor the pasid setup helpers Yi Liu
2024-11-07 12:22 ` [PATCH v6 04/13] iommu/vt-d: Add pasid replace helpers Yi Liu
2024-11-07 12:22 ` [PATCH v6 05/13] iommu/vt-d: Consolidate the struct dev_pasid_info add/remove Yi Liu
2024-11-07 12:22 ` [PATCH v6 06/13] iommu/vt-d: Add iommu_domain_did() to get did Yi Liu
2024-11-07 12:22 ` [PATCH v6 07/13] iommu/vt-d: Make intel_iommu_set_dev_pasid() to handle domain replacement Yi Liu
2024-11-07 12:22 ` [PATCH v6 08/13] iommu/vt-d: Limit intel_iommu_set_dev_pasid() for paging domain Yi Liu
2024-11-07 12:22 ` [PATCH v6 09/13] iommu/vt-d: Make intel_svm_set_dev_pasid() support domain replacement Yi Liu
2024-11-07 12:22 ` [PATCH v6 10/13] iommu/vt-d: Make identity_domain_set_dev_pasid() to handle " Yi Liu
2024-11-07 12:22 ` [PATCH v6 11/13] iommu/vt-d: Add set_dev_pasid callback for nested domain Yi Liu
2024-11-07 12:22 ` [PATCH v6 12/13] iommu/arm-smmu-v3: Make set_dev_pasid() op support replace Yi Liu
2024-11-07 12:22 ` [PATCH v6 13/13] iommu: Make set_dev_pasid op support domain replacement Yi Liu
2024-11-08  2:12 ` Baolu Lu [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=b3d351dd-e75f-483f-be7d-0c0bcb1dec7a@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=alex.williamson@redhat.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=eric.auger@redhat.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=vasant.hegde@amd.com \
    --cc=willy@infradead.org \
    --cc=yi.l.liu@intel.com \
    --cc=zhenzhong.duan@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