From: "'Joerg Roedel'" <jroedel@suse.de>
To: "Nath, Arindam" <Arindam.Nath@amd.com>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
"'Joerg Roedel'" <joro@8bytes.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Daniel Drake <drake@endlessm.com>
Subject: Re: [PATCH] PCI: Blacklist AMD Stoney GPU devices for ATS
Date: Wed, 29 Mar 2017 11:42:18 +0200 [thread overview]
Message-ID: <20170329094218.GU8329@suse.de> (raw)
In-Reply-To: <MWHPR12MB15181A0AC24BC60C4579742D9C350@MWHPR12MB1518.namprd12.prod.outlook.com>
Hi Arindam,
On Wed, Mar 29, 2017 at 07:15:42AM +0000, Nath, Arindam wrote:
> Joerg, as per my limited understanding of ATS, the ATC will respond to
> invalidation requests after making sure there are no in-flight DMA
> transactions with the address requested by IOMMU to be invalidated.
> Now since the IOMMU was sending invalidate command to GPU even though
> there was no explicit page unmapping request from the graphics
> subsystem, we _might_ end up in a situation where the ATC takes longer
> than the invalidation timeout to respond to IOMMU.
The maximum wait-time in the loop is 100ms. This should be more than
enough for the ATC to complete any in-flight transaction and flush its
internal TLB.
If that is not enough, there is almost certainly something wrong with
the hardware.
Joerg
next prev parent reply other threads:[~2017-03-29 9:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 12:16 [PATCH] PCI: Blacklist AMD Stoney GPU devices for ATS Joerg Roedel
2017-03-28 20:18 ` Deucher, Alexander
2017-03-28 20:28 ` Joerg Roedel
2017-03-28 20:37 ` Deucher, Alexander
2017-03-28 20:56 ` 'Joerg Roedel'
2017-03-28 21:13 ` Deucher, Alexander
2017-03-28 22:26 ` 'Joerg Roedel'
2017-03-29 7:15 ` Nath, Arindam
2017-03-29 9:42 ` 'Joerg Roedel' [this message]
2017-03-29 9:47 ` Nath, Arindam
2017-03-29 16:21 ` Deucher, Alexander
2017-04-04 16:43 ` Bjorn Helgaas
2017-04-07 12:34 ` 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=20170329094218.GU8329@suse.de \
--to=jroedel@suse.de \
--cc=Alexander.Deucher@amd.com \
--cc=Arindam.Nath@amd.com \
--cc=bhelgaas@google.com \
--cc=drake@endlessm.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.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