From: Bjorn Helgaas <helgaas@kernel.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Vasant Hegde <vasant.hegde@amd.com>,
iommu@lists.linux.dev, joro@8bytes.org,
linux-pci@vger.kernel.org, will@kernel.org, robin.murphy@arm.com,
suravee.suthikulpanit@amd.com, bhelgaas@google.com,
alexander.deucher@amd.com, jgg@ziepe.ca,
Amandeep Kaur Longia <AmandeepKaur.Longia@amd.com>,
Gerd Bayer <gbayer@linux.ibm.com>,
Alex Williamson <alex@shazbot.org>
Subject: Re: [PATCH 2/2] iommu/amd: Force identity mode for selected GPUs only
Date: Thu, 23 Jul 2026 16:02:46 -0500 [thread overview]
Message-ID: <20260723210246.GA856455@bhelgaas> (raw)
In-Reply-To: <70e6d40b-3e13-4efd-b1e7-62195ff66e91@amd.com>
[+cc Gerd, Alex]
On Thu, Jul 23, 2026 at 02:58:14PM -0500, Mario Limonciello wrote:
> On 7/23/26 14:53, Bjorn Helgaas wrote:
> > On Thu, Jul 23, 2026 at 11:32:49AM -0500, Mario Limonciello wrote:
> > > On 7/23/26 11:23, Vasant Hegde wrote:
> > > > On 7/23/2026 9:41 PM, Mario Limonciello wrote:
> > > > > On 7/23/26 10:59, Bjorn Helgaas wrote:
> > > > > > On Thu, Jul 23, 2026 at 06:15:48AM +0000, Vasant Hegde wrote:
> > > > > > > Certain AMD GPU's must always be in identity mode. Currently its enforced
> > > > > > > using PASID check. It worked fine as most GPU's has PASID feature. But
> > > > > > > this means, identity mode enforcement is done for all PASID capable devices.
> > > ...
> >
> > > > +static bool quirks_force_identity_mapping(struct pci_dev *pdev)
> > > > +{
> > > > + struct pci_dev *root_port;
> > > > + int class = pdev->class >> 8;
> > > > +
> > > > + /* AMD GPU vendor ID */
> > > > + if (pdev->vendor != PCI_VENDOR_ID_ATI)
> > > > + return false;
> > > > +
> > > > + /* GPU class */
> > > > + if (class != PCI_CLASS_DISPLAY_VGA &&
> > > > + class != PCI_CLASS_DISPLAY_OTHER)
> > > > + return false;
> > > > +
> > > > + if (pci_upstream_bridge(pdev) &&
> > >
> > > I don't think you need to check for pci_upstream_bridge() to be
> > > non-NULL. You already checked that it's an endpoint by looking at
> > > the class. So an endpoint will be connected to a bridge of some
> > > sort (either a switch internal to the dGPU or to a root port).
> >
> > I think devices can be passed through to virtualized guests with
> > no upstream bridge visible to the guest, can't they?
>
> None of the GPUs in APUs support SRIOV, so there isn't a VF to be
> passed in to a guest. But I guess you could pass the whole endpoint
> in.
>
> When passed into a guest doesn't it end up associated behind a root
> port in the guest though?
I don't think the Root Port is always passed into the guest. From
1ae8c4ce1570 ("PCI: Enable AtomicOps only if Root Port supports
them"):
On s390 and many virtualized guests, the Endpoint is visible but the
Root Port is not. In this case, pci_enable_atomic_ops_to_root()
previously enabled AtomicOps in the Endpoint even though it can't
tell whether the Root Port supports them as a completer.
Maybe Alex will chime in and tell us more about non-s390 guests.
next prev parent reply other threads:[~2026-07-23 21:02 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 6:15 [PATCH 0/2] iommu/amd: Fix default domain selection for PASID-capable devices Vasant Hegde
2026-07-23 6:15 ` [PATCH 1/2] PCI: Mark Radeon Pro WX 4100 ATS as broken Vasant Hegde
2026-07-23 15:42 ` Bjorn Helgaas
2026-07-23 15:45 ` Mario Limonciello
2026-07-23 16:51 ` Vasant Hegde
2026-07-23 6:15 ` [PATCH 2/2] iommu/amd: Force identity mode for selected GPUs only Vasant Hegde
2026-07-23 15:53 ` Ankit Soni
2026-07-23 16:29 ` Vasant Hegde
2026-07-23 15:59 ` Bjorn Helgaas
2026-07-23 16:11 ` Mario Limonciello
2026-07-23 16:23 ` Vasant Hegde
2026-07-23 16:32 ` Mario Limonciello
2026-07-23 16:55 ` Vasant Hegde
2026-07-23 19:53 ` Bjorn Helgaas
2026-07-23 19:58 ` Mario Limonciello
2026-07-23 21:02 ` Bjorn Helgaas [this message]
2026-07-24 15:11 ` Jason Gunthorpe
2026-07-27 4:13 ` Vasant Hegde
2026-07-23 16:33 ` Vasant Hegde
2026-07-24 15:15 ` Jason Gunthorpe
2026-07-27 4:19 ` Vasant Hegde
2026-07-27 14:45 ` Mario Limonciello
2026-07-28 4:52 ` Vasant Hegde
2026-07-28 5:31 ` Mario Limonciello
2026-07-28 19:10 ` Kuehling, Felix
2026-07-28 19:57 ` Mario Limonciello
2026-07-30 11:26 ` Vasant Hegde
2026-08-05 1:07 ` Jason Gunthorpe
2026-08-05 14:37 ` Vasant Hegde
2026-08-05 17:22 ` Deucher, Alexander
2026-08-05 17:53 ` Jason Gunthorpe
2026-08-05 18:12 ` Deucher, Alexander
2026-08-05 19:11 ` Jason Gunthorpe
2026-07-31 20:23 ` Deucher, Alexander
2026-07-31 20:19 ` Deucher, Alexander
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=20260723210246.GA856455@bhelgaas \
--to=helgaas@kernel.org \
--cc=AmandeepKaur.Longia@amd.com \
--cc=alex@shazbot.org \
--cc=alexander.deucher@amd.com \
--cc=bhelgaas@google.com \
--cc=gbayer@linux.ibm.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=linux-pci@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@amd.com \
--cc=will@kernel.org \
/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