From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Suthikulpanit, Suravee" <suravee.suthikulpanit@amd.com>
Cc: Vasant Hegde <vasant.hegde@amd.com>,
iommu@lists.linux.dev, joro@8bytes.org, wei.huang2@amd.com,
jsnitsel@redhat.com
Subject: Re: [PATCH v3 10/16] iommu/amd: Modify logic for checking GT and PPR features
Date: Fri, 11 Aug 2023 10:15:54 -0300 [thread overview]
Message-ID: <ZNY0imlDnwRkPb+7@ziepe.ca> (raw)
In-Reply-To: <b11dcd0d-f24c-c940-ce10-a5eba650b27c@amd.com>
On Thu, Aug 10, 2023 at 01:31:41PM -0700, Suthikulpanit, Suravee wrote:
>
> Actually, it is not just for the SNP.
>
> Please let me further clarify the existence of the global amd_iommu_efr and
> amd_iommu_efr2 variables.
>
> EFR and EFR2 are provided in two places:
> 1. The IVHD block in the ACPI IVRS table.
> 2. The register offset 0030h (EFR) and 01A0h (EFR2).
> where information in the IVHD block supersedes the MMIO registers.
>
> The EFR/EFR2 information is needed early in the initialization process prior
> to amd_iomu_init_pci() (where we can start accessing the MMIO registers).
> So, current code ignore information in the MMIO registers (only check and
> warn in case of the IVHD and MMIO are mismatch).
>
> Currently, IOMMU driver assumes capabilities on all IOMMU instances to be
> homogeneous. Therefore, during early_amd_iommu_init(), the driver probes all
> IVHD blocks and do sanity check to make sure that only features common among
> all IOMMU instances are supported. This is tracked in the global
> amd_iommu_efr / amd_iommu_efr2.
Assuming homogeneous is sort of the point - things should be localized
to their instances so you don't need to make this assumption, that
means minimizing the places that touch the global version
> Therefore, the helper function check_feature_on_all_iommus() uses the
> effective amd_iommu_efr/amd_iommu_efr2 instead of iommu->features. In facts,
> we should remove the code which directly uses the iommu->features,
> iommu->features2, and the iommu_feature() helper function to simply and make
> the code less confusing.
But if you do this I would not object - I just don't think it is good
driver design *for the iommu*
However..
Looking at it I only see two places that need the global 'all iommus'
check - one is amd_iommu_snp_enable() which is never called (seriously
stop adding dead code to support your out of tree patch sets!!!)
And the other is enable_iommus_vapic() which looks like it has the
iommus probed already.
So really this is 'we need it global for some SNP thing that isn't
even in the kernel' which is a really, really, bad justification.
Jason
next prev parent reply other threads:[~2023-08-11 13:15 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 [this message]
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
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=ZNY0imlDnwRkPb+7@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