From: Pranjal Shrivastava <praan@google.com>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: iommu@lists.linux.dev, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, 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>,
sashiko-bot@kernel.org
Subject: Re: [PATCH v2 2/5] iommu/amd: Fix DTE clearing and rename iommu_ignore_device()
Date: Mon, 24 Aug 2026 10:09:03 +0000 [thread overview]
Message-ID: <aowYPxhzGKMLIU10@google.com> (raw)
In-Reply-To: <3032d568-f23c-4e52-9303-5816bb2e2372@amd.com>
On Sat, Aug 22, 2026 at 07:28:20PM +0530, Vasant Hegde wrote:
>
>
[...]
> >
> > -static void iommu_ignore_device(struct amd_iommu *iommu, struct device *dev)
> > -{
> > - struct amd_iommu_pci_seg *pci_seg = iommu->pci_seg;
> > - struct dev_table_entry *dev_table = get_dev_table(iommu);
> > - int devid, sbdf;
> > -
> > - sbdf = get_device_sbdf_id(dev);
> > - if (sbdf < 0)
> > - return;
> > -
> > - devid = PCI_SBDF_TO_DEVID(sbdf);
> > - pci_seg->rlookup_table[devid] = NULL;
> > - memset(&dev_table[devid], 0, sizeof(struct dev_table_entry));
> > -
> > - setup_aliases(iommu, dev);
> > -}
> >
> >
> > /****************************************************************************
> > @@ -2233,6 +2217,41 @@ static void dev_update_dte(struct iommu_dev_data *dev_data, bool set)
> > clear_dte_entry(iommu, dev_data);
> > }
> >
> > +/*
> > + * Invalidate a DTE by clearing the Valid bit first.
> > + * Note: Not to be used on a fully probed device with
> > + * live dev_data.
> > + */
> > +static void amd_iommu_disable_dte(struct dev_table_entry *ptr)
> > +{
> > + struct dev_table_entry new = {};
> > +
> > + write_dte_lower128(ptr, &new);
> > + write_dte_upper128(ptr, &new);
> > +}
> > +
> > +static void iommu_disable_device_dma(struct amd_iommu *iommu, struct device *dev)
>
> This will disable interrupt remapping support as well. May be we should rename
> this function.
>
Ack, Sure. How about iommu_disable_device() ?
> Otherwise patch looks good.
>
Thanks,
Praan
next prev parent reply other threads:[~2026-08-24 10:09 UTC|newest]
Thread overview: 15+ 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-22 13:04 ` Vasant Hegde
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-22 13:58 ` Vasant Hegde
2026-08-24 10:09 ` Pranjal Shrivastava [this message]
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-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-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-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=aowYPxhzGKMLIU10@google.com \
--to=praan@google.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=sashiko-bot@kernel.org \
--cc=skhawaja@google.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@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