From: Jason Gunthorpe <jgg@ziepe.ca>
To: Tina Zhang <tina.zhang@intel.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
Lu Baolu <baolu.lu@linux.intel.com>,
Michael Shavit <mshavit@google.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] iommu: Support mm PASID 1:n with sva domains
Date: Tue, 8 Aug 2023 12:12:42 -0300 [thread overview]
Message-ID: <ZNJbaiTDG+YTgpDP@ziepe.ca> (raw)
In-Reply-To: <20230808074944.7825-5-tina.zhang@intel.com>
On Tue, Aug 08, 2023 at 03:49:43PM +0800, Tina Zhang wrote:
> Each mm bound to devices gets a PASID and corresponding sva domains
> allocated in iommu_sva_bind_device(), which are referenced by iommu_mm
> field of the mm. The PASID is released in __mmdrop(), while a sva domain
> is released when on one is using it (the reference count is decremented
> in iommu_sva_unbind_device()).
>
> Since the required info of PASID and sva domains is kept in struct
> iommu_mm_data of a mm, use mm->iommu_mm field instead of the old pasid
> field in mm struct. The sva domain list is protected by iommu_sva_lock.
>
> Besides, this patch removes mm_pasid_init(), as with the introduced
> iommu_mm structure, initializing mm pasid in mm_init() is unnecessary.
>
> Signed-off-by: Tina Zhang <tina.zhang@intel.com>
> ---
> drivers/iommu/iommu-sva.c | 38 +++++++++++++++++++++++++-------------
> include/linux/iommu.h | 10 +++-------
> kernel/fork.c | 1 -
> 3 files changed, 28 insertions(+), 21 deletions(-)
>
> diff --git a/drivers/iommu/iommu-sva.c b/drivers/iommu/iommu-sva.c
> index 0a4a1ed40814..35366f51ad27 100644
> --- a/drivers/iommu/iommu-sva.c
> +++ b/drivers/iommu/iommu-sva.c
> @@ -15,6 +15,7 @@ static DEFINE_IDA(iommu_global_pasid_ida);
> /* Allocate a PASID for the mm within range (inclusive) */
> static int iommu_sva_alloc_pasid(struct mm_struct *mm, ioasid_t min, ioasid_t max)
> {
> + struct iommu_mm_data *iommu_mm = NULL;
> int ret = 0;
>
> if (min == IOMMU_PASID_INVALID ||
> @@ -33,11 +34,22 @@ static int iommu_sva_alloc_pasid(struct mm_struct *mm, ioasid_t min, ioasid_t ma
> goto out;
> }
>
> + iommu_mm = kzalloc(sizeof(struct iommu_mm_data), GFP_KERNEL);
> + if (!iommu_mm) {
> + ret = -ENOMEM;
> + goto out;
> + }
> +
> ret = ida_alloc_range(&iommu_global_pasid_ida, min, max, GFP_KERNEL);
> - if (ret < 0)
> + if (ret < 0) {
> + kfree(iommu_mm);
> goto out;
> + }
> +
> + iommu_mm->pasid = ret;
> + mm->iommu_mm = iommu_mm;
> + INIT_LIST_HEAD(&mm->iommu_mm->sva_domains);
>
> - mm->pasid = ret;
> ret = 0;
> out:
> mutex_unlock(&iommu_sva_lock);
> @@ -82,16 +94,12 @@ struct iommu_sva *iommu_sva_bind_device(struct device *dev, struct mm_struct *mm
Lets please rework this function into two parts
The first should be 'iommu_sva_alloc_domain()'
It should do the list searching and user management. The usual
'iommu_domain_free()' should be modified to clean it up.
Then you have the 'alloc global/enqcmd pasid' function
Then bind is just callling alloc sva domain, alloc global pasid,
set_dev_pasid in a sequence.
It will make this much more understandable what all the parts are
supposed to be doing.
Jason
next prev parent reply other threads:[~2023-08-08 17:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 7:49 [PATCH 0/5] Share sva domains with all devices bound to a mm Tina Zhang
2023-08-08 7:49 ` [PATCH 1/5] iommu: Add mm_get_pasid() helper function Tina Zhang
2023-08-08 15:02 ` Jason Gunthorpe
2023-08-09 0:31 ` Baolu Lu
2023-08-09 9:47 ` Tian, Kevin
2023-08-09 12:31 ` Jason Gunthorpe
2023-08-08 7:49 ` [PATCH 2/5] iommu: Call helper function to get assigned pasid value Tina Zhang
2023-08-09 0:21 ` Baolu Lu
2023-08-09 9:49 ` Tian, Kevin
2023-08-09 10:58 ` Baolu Lu
2023-08-09 14:48 ` Jason Gunthorpe
2023-08-10 1:37 ` Baolu Lu
2023-08-10 16:30 ` Jason Gunthorpe
2023-08-09 12:35 ` Jason Gunthorpe
2023-08-10 7:52 ` Tian, Kevin
2023-08-10 16:36 ` Jason Gunthorpe
2023-08-11 3:18 ` Tian, Kevin
2023-08-08 7:49 ` [PATCH 3/5] mm: Add structure to keep sva information Tina Zhang
2023-08-08 7:49 ` [PATCH 4/5] iommu: Support mm PASID 1:n with sva domains Tina Zhang
2023-08-08 15:12 ` Jason Gunthorpe [this message]
2023-08-08 15:19 ` Jason Gunthorpe
2023-08-10 2:14 ` Tina Zhang
2023-08-08 7:49 ` [PATCH 5/5] mm: Deprecate pasid field Tina Zhang
2023-08-09 0:18 ` [PATCH 0/5] Share sva domains with all devices bound to a mm Baolu Lu
2023-08-09 9:44 ` Tian, Kevin
2023-08-09 10:51 ` Baolu Lu
2023-08-11 1:06 ` Tina Zhang
2023-08-09 14:46 ` Jason Gunthorpe
2023-08-10 1:23 ` Baolu Lu
2023-08-10 7:44 ` Tian, Kevin
2023-08-09 9:41 ` Tian, Kevin
2023-08-10 1:31 ` Tina Zhang
2023-08-10 7:49 ` Tian, Kevin
2023-08-10 16:27 ` Jason Gunthorpe
2023-08-11 1:12 ` Tina Zhang
2023-08-11 1:07 ` Tina Zhang
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=ZNJbaiTDG+YTgpDP@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mshavit@google.com \
--cc=tina.zhang@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