Linux IOMMU Development
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: iommu@lists.linux.dev, joro@8bytes.org,
	suravee.suthikulpanit@amd.com, wei.huang2@amd.com,
	jsnitsel@redhat.com
Subject: Re: [PATCH v3 15/16] iommu/amd: Initialize iommu_device->max_pasids
Date: Fri, 4 Aug 2023 10:14:53 -0300	[thread overview]
Message-ID: <ZMz5zVbcEVX6Rrj2@ziepe.ca> (raw)
In-Reply-To: <20230804064216.835544-16-vasant.hegde@amd.com>

On Fri, Aug 04, 2023 at 06:42:15AM +0000, Vasant Hegde wrote:
> Commit 1adf3cc20d69 ("iommu: Add max_pasids field in struct iommu_device")
> introduced a variable struct iommu_device.max_pasids to track max
> PASIDS supported by each IOMMU.
> 
> Let us initialize this field for AMD IOMMU. IOMMU core will use this value
> to set max PASIDs per device (see __iommu_probe_device()).
> 
> Also remove unused global 'amd_iommu_max_pasid' variable.
> 
> Signed-off-by: Vasant Hegde <vasant.hegde@amd.com>
> ---
>  drivers/iommu/amd/amd_iommu_types.h | 3 ---
>  drivers/iommu/amd/init.c            | 9 ++-------
>  2 files changed, 2 insertions(+), 10 deletions(-)
> 
> diff --git a/drivers/iommu/amd/amd_iommu_types.h b/drivers/iommu/amd/amd_iommu_types.h
> index e114e4af0f05..0d339e022572 100644
> --- a/drivers/iommu/amd/amd_iommu_types.h
> +++ b/drivers/iommu/amd/amd_iommu_types.h
> @@ -895,9 +895,6 @@ extern unsigned amd_iommu_aperture_order;
>  /* allocation bitmap for domain ids */
>  extern unsigned long *amd_iommu_pd_alloc_bitmap;
>  
> -/* Smallest max PASID supported by any IOMMU in the system */
> -extern u32 amd_iommu_max_pasid;
> -
>  extern bool amd_iommu_force_isolation;
>  
>  /* Max levels of glxval supported */
> diff --git a/drivers/iommu/amd/init.c b/drivers/iommu/amd/init.c
> index 1f56478ae74e..e0b0e48d3d38 100644
> --- a/drivers/iommu/amd/init.c
> +++ b/drivers/iommu/amd/init.c
> @@ -185,8 +185,6 @@ static int amd_iommus_present;
>  bool amd_iommu_np_cache __read_mostly;
>  bool amd_iommu_iotlb_sup __read_mostly = true;
>  
> -u32 amd_iommu_max_pasid __read_mostly = ~0;
> -
>  static bool amd_iommu_pc_present __read_mostly;
>  bool amdr_ivrs_remap_support __read_mostly;
>  
> @@ -2086,16 +2084,13 @@ static int __init iommu_init_pci(struct amd_iommu *iommu)
>  
>  	if (iommu_feature(iommu, FEATURE_GT)) {
>  		int glxval;
> -		u32 max_pasid;
>  		u64 pasmax;
>  
>  		pasmax = iommu->features & FEATURE_PASID_MASK;
>  		pasmax >>= FEATURE_PASID_SHIFT;
> -		max_pasid  = (1 << (pasmax + 1)) - 1;
> -
> -		amd_iommu_max_pasid = min(amd_iommu_max_pasid, max_pasid);
> +		iommu->iommu.max_pasids = (1 << (pasmax + 1)) - 1;
>  
> -		BUG_ON(amd_iommu_max_pasid & ~PASID_MASK);
> +		BUG_ON(iommu->iommu.max_pasids & ~PASID_MASK);

You said you'd fix this to remove the BUG_ON.

Jason

  reply	other threads:[~2023-08-04 13:14 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04  6:42 [PATCH v3 00/16] iommu/amd: SVA Support (Part 1) - cleanup/refactoring Vasant Hegde
2023-08-04  6:42 ` [PATCH v3 01/16] iommu/amd: Remove unused amd_io_pgtable.pt_root variable Vasant Hegde
2023-08-04  6:42 ` [PATCH v3 02/16] iommu/amd: Consolidate timeout pre-define to amd_iommu_type.h Vasant Hegde
2023-08-04  6:42 ` [PATCH v3 03/16] iommu/amd: Consolidate logic to allocate protection domain Vasant Hegde
2023-08-04  6:42 ` [PATCH v3 04/16] iommu/amd: Refactor protection domain allocation code Vasant Hegde
2023-08-04  6:42 ` [PATCH v3 05/16] iommu/amd/iommu_v2: Use protection_domain in struct device_state Vasant Hegde
2023-08-04  6:42 ` [PATCH v3 06/16] iommu/amd: Introduce helper functions for managing GCR3 table Vasant Hegde
2023-08-04 13:17   ` Jason Gunthorpe
2023-08-04 16:51     ` Vasant Hegde
2023-08-04 18:13       ` Jason Gunthorpe
2023-08-07  6:13         ` Vasant Hegde
2023-08-04  6:42 ` [PATCH v3 07/16] iommu/amd: Use struct protection_domain in helper functions Vasant Hegde
2023-08-04  6:42 ` [PATCH v3 08/16] iommu/amd: Do not set amd_iommu_pgtable in pass-through mode Vasant Hegde
2023-08-04  6:42 ` [PATCH v3 09/16] iommu/amd: Miscellaneous clean up when free domain Vasant Hegde
2023-08-04 13:19   ` Jason Gunthorpe
2023-08-04  6:42 ` [PATCH v3 10/16] iommu/amd: Modify logic for checking GT and PPR features Vasant Hegde
2023-08-04 13:19   ` Jason Gunthorpe
2023-08-07 16:44     ` Vasant Hegde
2023-08-08 13:55       ` Jason Gunthorpe
2023-08-10 20:31         ` Suthikulpanit, Suravee
2023-08-11 13:15           ` Jason Gunthorpe
2023-08-11 17:02             ` Suthikulpanit, Suravee
2023-08-04  6:42 ` [PATCH v3 11/16] iommu/amd: Rename ats related variables Vasant Hegde
2023-08-04  6:42 ` [PATCH v3 12/16] iommu/amd: Add support for different types of PPR handler Vasant Hegde
2023-08-04 13:28   ` Jason Gunthorpe
2023-08-04 16:22     ` Vasant Hegde
2023-08-04  6:42 ` [PATCH v3 13/16] iommu/amd: Introduce iommu_dev_data.flags to track device capabilities Vasant Hegde
2023-08-04 13:36   ` Jason Gunthorpe
2023-08-04  6:42 ` [PATCH v3 14/16] iommu/amd: Enable device ATS/PASID/PRI capabilities independently Vasant Hegde
2023-08-04  6:42 ` [PATCH v3 15/16] iommu/amd: Initialize iommu_device->max_pasids Vasant Hegde
2023-08-04 13:14   ` Jason Gunthorpe [this message]
2023-08-07 16:45     ` Vasant Hegde
2023-08-04  6:42 ` [PATCH v3 16/16] iommu/amd: Simplify amd_iommu_device_info() Vasant Hegde

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=ZMz5zVbcEVX6Rrj2@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=jsnitsel@redhat.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=vasant.hegde@amd.com \
    --cc=wei.huang2@amd.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