From: Baolu Lu <baolu.lu@linux.intel.com>
To: Jacob Pan <jacob.jun.pan@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
iommu@lists.linux.dev, Jason Gunthorpe <jgg@nvidia.com>,
Joerg Roedel <joro@8bytes.org>,
Jean-Philippe Brucker <jean-philippe@linaro.com>,
Robin Murphy <robin.murphy@arm.com>,
Dave Hansen <dave.hansen@intel.com>,
Thomas Gleixner <tglx@linutronix.de>, X86 Kernel <x86@kernel.org>,
bp@alien8.de, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
corbet@lwn.net, vkoul@kernel.org, dmaengine@vger.kernel.org,
linux-doc@vger.kernel.org
Cc: baolu.lu@linux.intel.com, Will Deacon <will@kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
Raj Ashok <ashok.raj@intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>, Yi Liu <yi.l.liu@intel.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Kirill Shutemov <kirill.shutemov@linux.intel.com>,
Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH v6 4/7] iommu/sva: Stop using ioasid_set for SVA
Date: Tue, 14 Mar 2023 10:16:41 +0800 [thread overview]
Message-ID: <0548021d-d9b3-3a2e-8c1f-e266dedb8f1c@linux.intel.com> (raw)
In-Reply-To: <20230313204158.1495067-5-jacob.jun.pan@linux.intel.com>
On 3/14/23 4:41 AM, Jacob Pan wrote:
> From: Jason Gunthorpe<jgg@nvidia.com>
>
> Instead SVA drivers can use a simple global IDA to allocate PASIDs for
> each mm_struct.
>
> Future work would be to allow drivers using the SVA APIs to reserve global
> PASIDs from this IDA for their internal use, eg with the DMA API PASID
> support.
>
> Signed-off-by: Jason Gunthorpe<jgg@nvidia.com>
> Signed-off-by: Jacob Pan<jacob.jun.pan@linux.intel.com>
> ---
> v5:
> - Put removing iommu_sva_find() to a separate patch (Kevin)
> - Make pasid allocation range to be inclusive (Tina)
> - Simplified return code handling (Baolu)
> v4:
> - Keep GFP_ATOMIC flag for PASID allocation, will changed to
> GFP_KERNEL in a separate patch.
> ---
> drivers/iommu/iommu-sva.c | 43 ++++++++++++++-------------------------
> drivers/iommu/iommu-sva.h | 2 --
> 2 files changed, 15 insertions(+), 30 deletions(-)
>
> diff --git a/drivers/iommu/iommu-sva.c b/drivers/iommu/iommu-sva.c
> index 4f357ef14f04..d4640731727a 100644
> --- a/drivers/iommu/iommu-sva.c
> +++ b/drivers/iommu/iommu-sva.c
> @@ -9,47 +9,34 @@
> #include "iommu-sva.h"
>
> static DEFINE_MUTEX(iommu_sva_lock);
> -static DECLARE_IOASID_SET(iommu_sva_pasid);
> +static DEFINE_IDA(iommu_global_pasid_ida);
>
> -/**
> - * iommu_sva_alloc_pasid - Allocate a PASID for the mm
> - * @mm: the mm
> - * @min: minimum PASID value (inclusive)
> - * @max: maximum PASID value (inclusive)
> - *
> - * Try to allocate a PASID for this mm, or take a reference to the existing one
> - * provided it fits within the [@min, @max] range. On success the PASID is
> - * available in mm->pasid and will be available for the lifetime of the mm.
> - *
> - * Returns 0 on success and < 0 on error.
> - */
> -int iommu_sva_alloc_pasid(struct mm_struct *mm, ioasid_t min, ioasid_t max)
> +/* 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)
> {
> int ret = 0;
> - ioasid_t pasid;
>
> - if (min == INVALID_IOASID || max == INVALID_IOASID ||
> - min == 0 || max < min)
> + if (!pasid_valid(min) || !pasid_valid(max) ||
> + min == 0 || max < min)
I still think the last line change is unnecessary. Otherwise, you
probably will get below CHECK warning:
CHECK: Alignment should match open parenthesis
#259: FILE: drivers/iommu/iommu-sva.c:20:
+ if (!pasid_valid(min) || !pasid_valid(max) ||
+ min == 0 || max < min)
Besides that,
Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>
Best regards,
baolu
next prev parent reply other threads:[~2023-03-14 2:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 20:41 Jacob Pan
2023-03-13 20:41 ` [PATCH v6 1/7] iommu/vt-d: Remove virtual command interface Jacob Pan
2023-03-13 20:41 ` [PATCH v6 2/7] iommu/sva: Move PASID helpers to sva code Jacob Pan
2023-03-14 2:07 ` Baolu Lu
2023-03-20 15:05 ` Jason Gunthorpe
2023-03-13 20:41 ` [PATCH v6 3/7] iommu/sva: Remove PASID to mm lookup function Jacob Pan
2023-03-14 2:08 ` Baolu Lu
2023-03-13 20:41 ` [PATCH v6 4/7] iommu/sva: Stop using ioasid_set for SVA Jacob Pan
2023-03-14 2:16 ` Baolu Lu [this message]
2023-03-14 15:15 ` Jacob Pan
2023-03-13 20:41 ` [PATCH v6 5/7] iommu/sva: Use GFP_KERNEL for pasid allocation Jacob Pan
2023-03-20 15:04 ` Jason Gunthorpe
2023-03-13 20:41 ` [PATCH v6 6/7] iommu/ioasid: Rename INVALID_IOASID Jacob Pan
2023-03-13 20:41 ` [PATCH v6 7/7] iommu: Remove ioasid infrastructure Jacob Pan
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=0548021d-d9b3-3a2e-8c1f-e266dedb8f1c@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux.dev \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jean-philippe@linaro.com \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=robin.murphy@arm.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=vkoul@kernel.org \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).