From: Jason Gunthorpe <jgg@nvidia.com>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: "Alice Ryhl" <aliceryhl@google.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Will Deacon" <will@kernel.org>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Joerg Roedel" <joro@8bytes.org>,
"Robin Murphy" <robin.murphy@arm.com>,
"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
"Asahi Lina" <lina+kernel@asahilina.net>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
iommu@lists.linux.dev, linux-mm@kvack.org,
"Alistair Popple" <apopple@nvidia.com>
Subject: Re: [PATCH v3] io: add io_pgtable abstraction
Date: Sat, 13 Dec 2025 20:51:25 -0400 [thread overview]
Message-ID: <aT4KDZSWLMlKwusl@nvidia.com> (raw)
In-Reply-To: <20251212104105.6af97d05@fedora>
On Fri, Dec 12, 2025 at 10:41:05AM +0100, Boris Brezillon wrote:
> > Then you can think about what is ideal for GPU and consider what the
> > work would be like. My uneducated feeling is with gpuvm trying to be
> > common code it could also have gpuvm provide shared common code that
> > directly builds page tables in CPU memory using the above framework.
>
> So, gpuvm is one level up (it doesn't deal at all with any HW
> representation), but I guess we could provide helpers for UMA-GPUs,
> where preparing the page table on the CPU is a thing, and it could be
> that MSM would be interested in using those helpers too.
You can make it work like the iommu does where gpuvm gets a "gpu
domain" from the driver that is created by using the common code from
gpuvm. Then most of the code is common.
I think something could be built that works with the framebuffer
resident page tables too if they are being accessed over mmio.
Jason
prev parent reply other threads:[~2025-12-14 0:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 10:15 [PATCH v3] io: add io_pgtable abstraction Alice Ryhl
2025-11-12 12:57 ` Daniel Almeida
2025-11-17 16:34 ` Alice Ryhl
2025-11-19 8:59 ` Boris Brezillon
2025-11-19 10:53 ` Boris Brezillon
2025-11-19 10:56 ` Boris Brezillon
2025-11-28 11:56 ` Robin Murphy
2025-11-28 12:27 ` Alice Ryhl
2025-11-28 16:47 ` Robin Murphy
2025-12-01 9:58 ` Alice Ryhl
2025-12-01 13:55 ` Robin Murphy
2025-11-28 18:02 ` Jason Gunthorpe
2025-12-12 8:44 ` Boris Brezillon
2025-12-12 9:21 ` Jason Gunthorpe
2025-12-12 9:41 ` Boris Brezillon
2025-12-14 0:51 ` Jason Gunthorpe [this message]
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=aT4KDZSWLMlKwusl@nvidia.com \
--to=jgg@nvidia.com \
--cc=Liam.Howlett@oracle.com \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=lina+kernel@asahilina.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--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;
as well as URLs for NNTP newsgroup(s).