Linux IOMMU Development
 help / color / mirror / Atom feed
From: Vasant Hegde <vasant.hegde@amd.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
	Bjorn Helgaas <helgaas@kernel.org>
Cc: 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
Subject: Re: [PATCH 1/2] PCI: Mark Radeon Pro WX 4100 ATS as broken
Date: Thu, 23 Jul 2026 22:21:06 +0530	[thread overview]
Message-ID: <f801bd33-1af5-41c9-aeee-bba8096414e5@amd.com> (raw)
In-Reply-To: <2a9f85b9-7fa3-41ab-9383-ffa1f44bbfd8@amd.com>



On 7/23/2026 9:15 PM, Mario Limonciello wrote:
> 
> 
> On 7/23/26 10:42, Bjorn Helgaas wrote:
>> On Thu, Jul 23, 2026 at 06:15:47AM +0000, Vasant Hegde wrote:
>>> If ATS is enabled then IOMMU logs below error and GPU fails to
>>> initialize.
>>>
>>> [  103.687137] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT
>>> device=0000:c4:00.0 address=0x1080006060]
>>
>> Is this a published erratum?
>>
>> Is there enough benefit to using ATS to make it worthwhile?  It would have
>> to be a pretty substantial benefit to outweigh the end-user frustration of
>> defects like this.
>>
>> If ATS isn't going to be validated by vendors, maybe we should disable it
>> on all AMD/ATI devices?  Or maybe only the GPUs?
> 
> Isn't that a pretty big performance impact to have ATS disabled?
> 
> At least I don't think I would want a blanket policy without data supporting
> it's a good idea.

Ack. I will find this GPU internally and will run some more experiement and get
back to you.


-Vasant



  reply	other threads:[~2026-07-23 16:51 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 [this message]
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
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=f801bd33-1af5-41c9-aeee-bba8096414e5@amd.com \
    --to=vasant.hegde@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --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=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