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: baolu.lu@linux.intel.com, alex.williamson@redhat.com,
eric.auger@redhat.com, nicolinc@nvidia.com,
chao.p.peng@linux.intel.com, iommu@lists.linux.dev,
zhenzhong.duan@intel.com, linux-kselftest@vger.kernel.org,
vasant.hegde@amd.com
Subject: Re: [PATCH 3/3] iommu: Add a wrapper for remove_dev_pasid
Date: Fri, 13 Sep 2024 10:24:45 +0800 [thread overview]
Message-ID: <71452c12-7339-4122-a7a3-64dd32ddba3b@linux.intel.com> (raw)
In-Reply-To: <20240912130653.11028-4-yi.l.liu@intel.com>
On 9/12/24 9:06 PM, Yi Liu wrote:
> The iommu drivers are on the way to drop the remove_dev_pasid op by
> extending the blocked_domain to support PASID. However, this cannot be
> done in one shot. So far, the Intel iommu and the ARM SMMUv3 driver have
> supported it, while the AMD iommu driver has not yet. During this
> transition, the IOMMU core needs to support both ways to destroy the
> attachment of device/PASID and domain.
>
> Signed-off-by: Yi Liu<yi.l.liu@intel.com>
> ---
> drivers/iommu/iommu.c | 30 ++++++++++++++++++++++++------
> 1 file changed, 24 insertions(+), 6 deletions(-)
This patch should be moved before the change in drivers. After all
drivers convert to use set blocking domain to pasid, the
remove_dev_pasid could be removed as the last step.
Thanks,
baolu
next prev parent reply other threads:[~2024-09-13 2:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 13:06 [PATCH 0/3] Support attaching PASID to the blocked_domain Yi Liu
2024-09-12 13:06 ` [PATCH 1/3] iommu/arm-smmu-v3: Make smmuv3 blocked domain support PASID Yi Liu
2024-09-30 7:24 ` Tian, Kevin
2024-09-12 13:06 ` [PATCH 2/3] iommu/vt-d: Make " Yi Liu
2024-09-30 7:24 ` Tian, Kevin
2024-09-12 13:06 ` [PATCH 3/3] iommu: Add a wrapper for remove_dev_pasid Yi Liu
2024-09-13 2:24 ` Baolu Lu [this message]
2024-09-13 11:47 ` Yi Liu
2024-09-30 7:26 ` Tian, Kevin
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=71452c12-7339-4122-a7a3-64dd32ddba3b@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=linux-kselftest@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=vasant.hegde@amd.com \
--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