From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Deucher, Alexander" <Alexander.Deucher@amd.com>
Cc: "Hegde, Vasant" <Vasant.Hegde@amd.com>,
"Limonciello, Mario" <Mario.Limonciello@amd.com>,
"Kuehling, Felix" <Felix.Kuehling@amd.com>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"joro@8bytes.org" <joro@8bytes.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"will@kernel.org" <will@kernel.org>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"Longia, Amandeep Kaur" <AmandeepKaur.Longia@amd.com>
Subject: Re: [PATCH 2/2] iommu/amd: Force identity mode for selected GPUs only
Date: Wed, 5 Aug 2026 14:53:08 -0300 [thread overview]
Message-ID: <20260805175308.GD28508@ziepe.ca> (raw)
In-Reply-To: <BN9PR12MB5146934D584CF0A2A9DD8CFCF7D32@BN9PR12MB5146.namprd12.prod.outlook.com>
On Wed, Aug 05, 2026 at 05:22:22PM +0000, Deucher, Alexander wrote:
> IIRC, they supported SME, but it wasn't usable due to other
> limitations (e.g., the requirement for identity mappings due to the
> display hw bug and the latency impact of encryption for displays in
> system memory). Do you could effectively pick either SME or
> displays.
IMHO the GPU driver should fail if it cannot work because it can't
reach the IOVA space requried for SME ...
I don't think this should be a iommu problem to deal with
Jason
next prev parent reply other threads:[~2026-08-05 17:53 UTC|newest]
Thread overview: 37+ 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 6:21 ` sashiko-bot
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 6:25 ` sashiko-bot
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
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 [this message]
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=20260805175308.GD28508@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=Alexander.Deucher@amd.com \
--cc=AmandeepKaur.Longia@amd.com \
--cc=Felix.Kuehling@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=Vasant.Hegde@amd.com \
--cc=bhelgaas@google.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-pci@vger.kernel.org \
--cc=robin.murphy@arm.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