From: Jason Gunthorpe <jgg@nvidia.com>
To: Dave Airlie <airlied@gmail.com>
Cc: "Christian König" <christian.koenig@amd.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
iommu@lists.linux-foundation.org,
"Alistair Popple" <apopple@nvidia.com>,
"Matthew Brost" <matthew.brost@intel.com>
Subject: Re: iommu/smmu/PCI ATS + TTM unmaps + nouveau best way forward
Date: Tue, 30 Jun 2026 21:17:02 -0300 [thread overview]
Message-ID: <20260701001702.GI7481@nvidia.com> (raw)
In-Reply-To: <CAPM=9ty=fiCTrfwE4VUGUDak7paNcKwVo9t171FyYP4VyGM=4A@mail.gmail.com>
On Wed, Jul 01, 2026 at 07:00:01AM +1000, Dave Airlie wrote:
> From the production driver, there definitely was some issues in the
> past, however this seems possibly fixed with mmu notifiers, but for
> these memory allocations I'm doing I'm not using MMU notifiers at all.
Well, the comment on that is this:
// Fix for Bug 4130089: [GH180][r535] WAR for kernel not issuing SMMU
// TLB invalidates on read-only to read-write upgrades
And the upstream kernel has that issue fixed, so it looks like that
whole disaster compiles out.
Jason
next prev parent reply other threads:[~2026-07-01 0:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 9:39 iommu/smmu/PCI ATS + TTM unmaps + nouveau best way forward Dave Airlie
2026-06-30 11:24 ` Christian König
2026-06-30 11:51 ` Jason Gunthorpe
2026-06-30 20:45 ` Dave Airlie
2026-06-30 21:00 ` Dave Airlie
2026-07-01 0:17 ` Jason Gunthorpe [this message]
2026-07-01 1:22 ` Alistair Popple
2026-06-30 23:59 ` Jason Gunthorpe
2026-06-30 11:39 ` Jason Gunthorpe
2026-06-30 23:21 ` Matthew Brost
2026-07-01 1:30 ` Alistair Popple
2026-07-01 23:34 ` Jason Gunthorpe
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=20260701001702.GI7481@nvidia.com \
--to=jgg@nvidia.com \
--cc=airlied@gmail.com \
--cc=apopple@nvidia.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=iommu@lists.linux-foundation.org \
--cc=matthew.brost@intel.com \
/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