From: Vasant Hegde <vasant.hegde@amd.com>
To: Pranjal Shrivastava <praan@google.com>,
iommu@lists.linux.dev, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Joerg Roedel <joro@8bytes.org>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Ankit Soni <ankit.soni@amd.com>, Jason Gunthorpe <jgg@nvidia.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Samiullah Khawaja <skhawaja@google.com>
Subject: Re: [PATCH v2 1/5] iommu/amd: Refactor device probe and capability initialization
Date: Sat, 22 Aug 2026 18:34:42 +0530 [thread overview]
Message-ID: <ecb70415-05c9-40bd-8ddb-173267a7a30d@amd.com> (raw)
In-Reply-To: <20260814015647.3370124-2-praan@google.com>
Pranjal,
On 8/14/2026 7:26 AM, Pranjal Shrivastava wrote:
> Restructure the device probe path to improve readability and prepare for
> cleaner error handling. Refactor check_device() into iommu_lookup_device
> to explicitly validate and return the amd_iommu ptr & devid. Refactor
> iommu_init_device() to return the allocated dev_data. Consolidate all
> PCI cap inits (MSI domains, PASID, ATS) into a new helper:
> iommu_init_device_caps().
>
> Suggested-by: Vasant Hegde <vasant.hegde@amd.com>
> Signed-off-by: Pranjal Shrivastava <praan@google.com>
> ---
> drivers/iommu/amd/iommu.c | 114 +++++++++++++++++++-------------------
> 1 file changed, 56 insertions(+), 58 deletions(-)
>
> diff --git a/drivers/iommu/amd/iommu.c b/drivers/iommu/amd/iommu.c
> index 4c31294fabc5..9b8ad131ba79 100644
> --- a/drivers/iommu/amd/iommu.c
> +++ b/drivers/iommu/amd/iommu.c
> @@ -675,7 +675,8 @@ static void pdev_disable_caps(struct pci_dev *pdev)
.../...
> - amd_iommu_set_pci_msi_domain(dev, iommu);
> + iommu_init_device_caps(dev_data, dev, iommu);
> iommu_dev = &iommu->iommu;
>
> - /*
> - * If IOMMU and device supports PASID then it will contain max
> - * supported PASIDs, else it will be zero.
> - */
> - dev_data = dev_iommu_priv_get(dev);
> - if (amd_iommu_pasid_supported() && dev_is_pci(dev) &&
> - pdev_pasid_supported(dev_data)) {
> - dev_data->max_pasids = min_t(u32, iommu->iommu.max_pasids,
> - pci_max_pasids(to_pci_dev(dev)));
> - }
> -
Can you add something like below comment so that we know why we are not calling
iommu_ignore_device in error path.
+ * When DMA translation is unavailable return error so the iommu core
+ * won't attempt domain attach for this device. But interrupt-remap
+ * is still supported. Hence do not ignore the device.
-Vasant
> if (amd_iommu_pgtable == PD_MODE_NONE) {
> pr_warn_once("%s: DMA translation not supported by iommu.\n",
> __func__);
> @@ -2527,16 +2535,6 @@ static struct iommu_device *amd_iommu_probe_device(struct device *dev)
> goto out_err;
> }
>
> - iommu_completion_wait(iommu);
> -
> - if (FEATURE_NUM_INT_REMAP_SUP_2K(amd_iommu_efr2))
> - dev_data->max_irqs = MAX_IRQS_PER_TABLE_2K;
> - else
> - dev_data->max_irqs = MAX_IRQS_PER_TABLE_512;
> -
> - if (dev_is_pci(dev))
> - pci_prepare_ats(to_pci_dev(dev), PAGE_SHIFT);
> -
> out_err:
> return iommu_dev;
> }
next prev parent reply other threads:[~2026-08-22 13:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 1:56 [PATCH v2 0/5] iommu/amd: Refactors for ATS robustness Pranjal Shrivastava
2026-08-14 1:56 ` [PATCH v2 1/5] iommu/amd: Refactor device probe and capability initialization Pranjal Shrivastava
2026-08-14 2:13 ` sashiko-bot
2026-08-22 13:04 ` Vasant Hegde [this message]
2026-08-24 10:07 ` Pranjal Shrivastava
2026-08-14 1:56 ` [PATCH v2 2/5] iommu/amd: Fix DTE clearing and rename iommu_ignore_device() Pranjal Shrivastava
2026-08-14 2:34 ` sashiko-bot
2026-08-22 13:58 ` Vasant Hegde
2026-08-24 10:09 ` Pranjal Shrivastava
2026-08-24 10:37 ` Vasant Hegde
2026-08-14 1:56 ` [PATCH v2 3/5] iommu/amd: Split probe error paths to preserve IRQ remapping Pranjal Shrivastava
2026-08-14 2:54 ` sashiko-bot
2026-08-22 13:56 ` Vasant Hegde
2026-08-14 1:56 ` [PATCH v2 4/5] iommu/amd: Fail probe on ATS configuration failure Pranjal Shrivastava
2026-08-14 3:05 ` sashiko-bot
2026-08-22 13:55 ` Vasant Hegde
2026-08-14 1:56 ` [PATCH v2 5/5] PCI/ATS: Mandate checking pci_ats_supported() before pci_prepare_ats() Pranjal Shrivastava
2026-08-14 3:11 ` sashiko-bot
2026-08-22 13:55 ` Vasant Hegde
2026-08-22 14:04 ` [PATCH v2 0/5] iommu/amd: Refactors for ATS robustness 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=ecb70415-05c9-40bd-8ddb-173267a7a30d@amd.com \
--to=vasant.hegde@amd.com \
--cc=ankit.soni@amd.com \
--cc=bhelgaas@google.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=praan@google.com \
--cc=skhawaja@google.com \
--cc=suravee.suthikulpanit@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