From: Yi Liu <yi.l.liu@intel.com>
To: joro@8bytes.org, kevin.tian@intel.com, baolu.lu@linux.intel.com,
jgg@nvidia.com
Cc: yi.l.liu@intel.com, iommu@lists.linux.dev,
jacob.pan@linux.microsoft.com, robin.murphy@arm.com,
nicolinc@nvidia.com, will@kernel.org
Subject: [PATCH 0/2] Two enhancements to iommu_attach_device_pasid()
Date: Sun, 19 Jan 2025 19:08:38 -0800 [thread overview]
Message-ID: <20250120030840.4171-1-yi.l.liu@intel.com> (raw)
It's spotted during the review process of iommufd pasid series [1]. The
first one is about storing entry to group->pasid_array, and the second
one is to avoid the potential PRIs anchored on the failed domain. Details
can be found in the individial patch.
[1] https://lore.kernel.org/linux-iommu/20241219132746.16193-2-yi.l.liu@intel.com/
Yi Liu (2):
iommu: Store either domain or handle in group->pasid_array
iommu: Swap the order of setting group->pasid_array and
__iommu_set_group_pasid()
drivers/iommu/iommu.c | 40 ++++++++++++++++++++++++++++++----------
1 file changed, 30 insertions(+), 10 deletions(-)
--
2.34.1
next reply other threads:[~2025-01-20 3:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 3:08 Yi Liu [this message]
2025-01-20 3:08 ` [PATCH 1/2] iommu: Store either domain or handle in group->pasid_array Yi Liu
2025-01-20 5:55 ` Tian, Kevin
2025-01-20 15:55 ` Jason Gunthorpe
2025-01-21 2:02 ` Baolu Lu
2025-01-21 7:22 ` Yi Liu
2025-01-20 3:08 ` [PATCH 2/2] iommu: Swap the order of setting group->pasid_array and __iommu_set_group_pasid() Yi Liu
2025-01-20 5:58 ` Tian, Kevin
2025-01-20 6:57 ` Yi Liu
2025-01-20 16:13 ` Jason Gunthorpe
2025-01-21 9:27 ` Yi Liu
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=20250120030840.4171-1-yi.l.liu@intel.com \
--to=yi.l.liu@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jacob.pan@linux.microsoft.com \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
/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