From: Jason Gunthorpe <jgg@ziepe.ca>
To: Matthew Brost <matthew.brost@intel.com>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
leonro@nvidia.com, francois.dugast@intel.com,
thomas.hellstrom@linux.intel.com,
himal.prasad.ghimiray@intel.com
Subject: Re: [RFC PATCH v2 0/3] Use new dma-map IOVA alloc, link, and sync API in GPU SVM and DRM pagemap
Date: Tue, 27 Jan 2026 14:37:01 -0400 [thread overview]
Message-ID: <20260127183701.GI1641016@ziepe.ca> (raw)
In-Reply-To: <aXjtvj/2AZxY1MwO@lstrano-desk.jf.intel.com>
On Tue, Jan 27, 2026 at 08:54:22AM -0800, Matthew Brost wrote:
> That will likely work for dma-buf, let me see if I can convert our
> dma-buf flows to use this helper. But it won't work for things like SVM,
> so it would be desirable to figure out to have an API drivers can use to
> iova alloc/link/sync/unlink/free for multi-device or just agree we trust
> drivers enough to use the existing API.
SVM should be driven with HMM and there is a helper in
hmm_dma_map_pfn() for this.
Yonatan posted a series to expand it to work with ZONE_DEVICE PRIVATE
pages but it needs a refresh
https://lore.kernel.org/linux-rdma/20250718115112.3881129-1-ymaman@nvidia.com/
If there are other cases it would be reasonable to discuss enhancing
hmm_dma_map_pfn().
Jason
next prev parent reply other threads:[~2026-01-27 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 21:59 [RFC PATCH v2 0/3] Use new dma-map IOVA alloc, link, and sync API in GPU SVM and DRM pagemap Matthew Brost
2026-01-23 21:59 ` [RFC PATCH v2 1/3] drm/pagemap: Add helper to access zone_device_data Matthew Brost
2026-01-23 21:59 ` [RFC PATCH v2 2/3] drm/gpusvm: Use new dma-map IOVA alloc, link, and sync API in GPU SVM Matthew Brost
2026-01-23 21:59 ` [RFC PATCH v2 3/3] drm/pagemap: Use new dma-map IOVA alloc, link, and sync API for DRM pagemap Matthew Brost
2026-01-23 22:41 ` [RFC PATCH v2 0/3] Use new dma-map IOVA alloc, link, and sync API in GPU SVM and " Jason Gunthorpe
2026-01-23 22:53 ` Matthew Brost
2026-01-24 0:26 ` Jason Gunthorpe
2026-01-27 16:54 ` Matthew Brost
2026-01-27 18:37 ` Jason Gunthorpe [this message]
2026-01-27 19:05 ` Matthew Brost
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=20260127183701.GI1641016@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dri-devel@lists.freedesktop.org \
--cc=francois.dugast@intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=leonro@nvidia.com \
--cc=matthew.brost@intel.com \
--cc=thomas.hellstrom@linux.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