From: Jason Gunthorpe <jgg@ziepe.ca>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Mario Limonciello <superm1@gmail.com>,
Joerg Roedel <joro@8bytes.org>,
Alex Deucher <alexander.deucher@amd.com>,
amd-gfx@lists.freedesktop.org,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Vasant Hegde <vasant.hegde@amd.com>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
"open list:AMD IOMMU (AMD-VI)" <iommu@lists.linux.dev>,
Jatin Kataria <jkataria@netflix.com>,
Boqun Feng <boqunf@netflix.com>,
"Derek J . Clark" <derekjohn.clark@gmail.com>
Subject: Re: [PATCH v2 1/2] iommu/amd: Add PerfOpt IOMMU performance optimization support
Date: Mon, 28 Sep 2026 14:11:57 -0300 [thread overview]
Message-ID: <20260928171157.GI163130@ziepe.ca> (raw)
In-Reply-To: <34bcdf7a-82b1-43cb-8409-735ebef3fa97@amd.com>
On Mon, Sep 28, 2026 at 10:32:41AM -0500, Mario Limonciello wrote:
> Actually; no. amdgpu has migrated away from PCI IDs and probes based on the
> "ATI vendor" + "display class" instead. As part of the probe sequence there
> is something called an IP discovery table pull from the platform that
> identifies all IP blocks in the hardware.
Oh, so that big table is not processing pci ids.. OK
> This IP discovery table will indicate graphics IP and that is mapped to
> relevant driver code. So for example GC 11.5.1 is what you find in a Strix
> Halo APU. If a future APU had exactly the same graphics IP but a different
> display IP it would still be GC 11.5.1.
Move this stuff to drivers/firmware and iommu and GPU can access it
together?
"IP discovery table" sure sounds like a platform firmware datablob to
me at least?
Jason
next prev parent reply other threads:[~2026-09-29 8:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 4:12 [PATCH v2 0/2] IOMMU Performance Optimization support Mario Limonciello
2026-09-08 4:12 ` [PATCH v2 1/2] iommu/amd: Add PerfOpt IOMMU performance optimization support Mario Limonciello
2026-09-24 22:50 ` Jason Gunthorpe
2026-09-25 0:03 ` Mario Limonciello
2026-09-25 0:17 ` Jason Gunthorpe
2026-09-25 0:21 ` Mario Limonciello
2026-09-25 7:20 ` Joerg Roedel
2026-09-25 12:28 ` Jason Gunthorpe
2026-09-25 13:11 ` Mario Limonciello
2026-09-25 22:39 ` Jason Gunthorpe
2026-09-26 0:33 ` Mario Limonciello
2026-09-28 12:08 ` Jason Gunthorpe
2026-09-28 15:32 ` Mario Limonciello
2026-09-28 17:11 ` Jason Gunthorpe [this message]
2026-09-28 17:15 ` Mario Limonciello
2026-09-29 2:53 ` Deucher, Alexander
2026-09-28 5:17 ` Christoph Hellwig
2026-09-25 7:30 ` Joerg Roedel
2026-09-08 4:12 ` [PATCH v2 2/2] drm/amdgpu: Enable PerfOpt IOMMU perf optimization when GPU in identity domain Mario Limonciello
2026-09-20 14:10 ` [PATCH v2 0/2] IOMMU Performance Optimization support Mario Limonciello
2026-09-20 16:27 ` Boqun Feng
2026-09-24 11:42 ` Joerg Roedel
2026-09-24 13:01 ` Deucher, Alexander
2026-09-24 13:50 ` Joerg Roedel
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=20260928171157.GI163130@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=boqunf@netflix.com \
--cc=derekjohn.clark@gmail.com \
--cc=iommu@lists.linux.dev \
--cc=jkataria@netflix.com \
--cc=joro@8bytes.org \
--cc=mario.limonciello@amd.com \
--cc=robin.murphy@arm.com \
--cc=superm1@gmail.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