Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
	"Kuehling, Felix" <felix.kuehling@amd.com>,
	"Deucher, Alexander" <Alexander.Deucher@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,
	Amandeep Kaur Longia <AmandeepKaur.Longia@amd.com>
Subject: Re: [PATCH 2/2] iommu/amd: Force identity mode for selected GPUs only
Date: Tue, 4 Aug 2026 22:07:06 -0300	[thread overview]
Message-ID: <20260805010706.GC28508@ziepe.ca> (raw)
In-Reply-To: <08f2e48e-6e98-4fde-af71-cb8cde666bdf@amd.com>

On Thu, Jul 30, 2026 at 04:56:37PM +0530, Vasant Hegde wrote:

> Based on discussion so far in this thread and the link Mario shared earlier [1]:
>   - We still need identity mapping for APUs. I will fine tune the patch based on
> the discussion in this thread.

IMHO if certain HW has broken support for PAGING (eg because it can't
handle the isochronous needs) then it should be quirked and blocked
properly.

I thought the issue here was the PASID check forcing identity and
accidently capturing these raven chips too? It should just be moved
out to a normal quirk..

>   - Its fine to drop SNP check
>   - I am still not sure its safe to drop SME check (CC_ATTR_MEM_ENCRYPT)
>     Because here were are putting all APUs in identity mode.
>     Commit ea68573d408f explicitly error out for RAVEN and some of the older APU
> platform didn't support SME. But not sure about newer ones.

That's quite a hacky check to make in that commit..

> So I am inclined to keep SME check for now. Once this patch stabilized we can
> revisit the SME check?

The SME check makes no sense either, but if you want to stage things
I'm OK with it.

Jason

  reply	other threads:[~2026-08-05  1:07 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 [this message]
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=20260805010706.GC28508@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=Alexander.Deucher@amd.com \
    --cc=AmandeepKaur.Longia@amd.com \
    --cc=bhelgaas@google.com \
    --cc=felix.kuehling@amd.com \
    --cc=iommu@lists.linux.dev \
    --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