From: Matthew Brost <matthew.brost@intel.com>
To: Lizhi Hou <lizhi.hou@amd.com>
Cc: <ogabbay@kernel.org>, <quic_jhugo@quicinc.com>,
<dri-devel@lists.freedesktop.org>, <mario.limonciello@amd.com>,
<maciej.falkowski@linux.intel.com>, Max Zhen <max.zhen@amd.com>,
<linux-kernel@vger.kernel.org>, <sonal.santan@amd.com>
Subject: Re: [PATCH V2] accel/amdxdna: Support read-only user-pointer BO mappings
Date: Tue, 31 Mar 2026 22:00:33 -0700 [thread overview]
Message-ID: <acymcah+Wlt/T4sL@gsse-cloud1.jf.intel.com> (raw)
In-Reply-To: <acylqAdORtJs4cgO@gsse-cloud1.jf.intel.com>
On Tue, Mar 31, 2026 at 09:57:12PM -0700, Matthew Brost wrote:
> On Tue, Mar 31, 2026 at 10:26:35AM -0700, Lizhi Hou wrote:
> > From: Max Zhen <max.zhen@amd.com>
> >
> > Update the amdxdna user-pointer (ubuf) BO path to support creating buffer
> > objects from read-only user mappings.
> >
> > Detect read-only VMAs by checking VMA permissions across all user virtual
> > address ranges associated with the BO. When all entries are read-only, pin
> > user pages without FOLL_WRITE and export the resulting dmabuf as read-only
> > (O_RDONLY).
> >
> > This allows userptr BOs backed by read-only mappings to be safely imported
> > and used without requiring write access, which was previously rejected due
> > to unconditional FOLL_WRITE usage.
> >
> > Signed-off-by: Max Zhen <max.zhen@amd.com>
> > Signed-off-by: Lizhi Hou <lizhi.hou@amd.com>
> > ---
> > drivers/accel/amdxdna/amdxdna_ubuf.c | 29 ++++++++++++++++++++++++++--
> > 1 file changed, 27 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/accel/amdxdna/amdxdna_ubuf.c b/drivers/accel/amdxdna/amdxdna_ubuf.c
> > index 4c0647057759..3769210c55cc 100644
> > --- a/drivers/accel/amdxdna/amdxdna_ubuf.c
> > +++ b/drivers/accel/amdxdna/amdxdna_ubuf.c
> > @@ -125,6 +125,26 @@ static const struct dma_buf_ops amdxdna_ubuf_dmabuf_ops = {
> > .vunmap = amdxdna_ubuf_vunmap,
> > };
> >
> > +static int readonly_va_entry(struct amdxdna_drm_va_entry *va_ent)
> > +{
> > + struct mm_struct *mm = current->mm;
> > + struct vm_area_struct *vma;
> > + int ret;
> > +
> > + mmap_read_lock(mm);
> > +
> > + vma = find_vma(mm, va_ent->vaddr);
> > + if (!vma ||
> > + vma->vm_start > va_ent->vaddr ||
> > + vma->vm_end - va_ent->vaddr < va_ent->len)
> > + ret = -ENOENT;
> > + else
> > + ret = vma->vm_flags & VM_WRITE ? 0 : 1;
> > +
> > + mmap_read_unlock(mm);
>
>
> This looks highly questionable. Drivers should be reaching into the core
s/should/shouldn't
Matt
> MM to create primitives.
>
> I also glanced at the userptr implementation here — it’s quite
> questionable as well, especially regarding whether notifier locking /
> hmm_range_fault interaction is needed on the driver side.
>
> I’m fairly certain that, with a bit of thought and some extensions to
> DRM GPUSVM, amdxdna could build userptr on that layer (Xe does this
> wihtout SVM). That would isolate core MM interactions to the common DRM
> layer, which I believe the core MM folks would appreciate.
>
> The biggest issue I see is that get_pages() in GPUSVM also performs a
> DMA map, which amdxdna doesn’t appear to need. That should be easy
> enough to split out. But amdxdna does need locking semantics, notifiers,
> etc., which GPUSVM already provides.
>
> I’d rather see GPUSVM expanded for the amdxdna use case so future
> drivers can use it as well.
>
> Happy to work with you on this.
>
> Matt
>
> > + return ret;
> > +}
> > +
> > struct dma_buf *amdxdna_get_ubuf(struct drm_device *dev,
> > u32 num_entries, void __user *va_entries)
> > {
> > @@ -134,6 +154,7 @@ struct dma_buf *amdxdna_get_ubuf(struct drm_device *dev,
> > struct amdxdna_ubuf_priv *ubuf;
> > u32 npages, start = 0;
> > struct dma_buf *dbuf;
> > + bool readonly = true;
> > int i, ret;
> > DEFINE_DMA_BUF_EXPORT_INFO(exp_info);
> >
> > @@ -172,6 +193,10 @@ struct dma_buf *amdxdna_get_ubuf(struct drm_device *dev,
> > ret = -EINVAL;
> > goto free_ent;
> > }
> > +
> > + /* Pin pages as writable as long as not all entries are read-only. */
> > + if (readonly && readonly_va_entry(&va_ent[i]) != 1)
> > + readonly = false;
> > }
> >
> > ubuf->nr_pages = exp_info.size >> PAGE_SHIFT;
> > @@ -194,7 +219,7 @@ struct dma_buf *amdxdna_get_ubuf(struct drm_device *dev,
> > npages = va_ent[i].len >> PAGE_SHIFT;
> >
> > ret = pin_user_pages_fast(va_ent[i].vaddr, npages,
> > - FOLL_WRITE | FOLL_LONGTERM,
> > + (readonly ? 0 : FOLL_WRITE) | FOLL_LONGTERM,
> > &ubuf->pages[start]);
> > if (ret >= 0) {
> > start += ret;
> > @@ -211,7 +236,7 @@ struct dma_buf *amdxdna_get_ubuf(struct drm_device *dev,
> >
> > exp_info.ops = &amdxdna_ubuf_dmabuf_ops;
> > exp_info.priv = ubuf;
> > - exp_info.flags = O_RDWR | O_CLOEXEC;
> > + exp_info.flags = (readonly ? O_RDONLY : O_RDWR) | O_CLOEXEC;
> >
> > dbuf = dma_buf_export(&exp_info);
> > if (IS_ERR(dbuf)) {
> > --
> > 2.34.1
> >
next prev parent reply other threads:[~2026-04-01 5:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 17:26 [PATCH V2] accel/amdxdna: Support read-only user-pointer BO mappings Lizhi Hou
2026-03-31 17:52 ` Mario Limonciello
2026-04-01 4:57 ` Matthew Brost
2026-04-01 5:00 ` Matthew Brost [this message]
2026-04-01 16:51 ` Lizhi Hou
2026-04-01 20:09 ` Matthew Brost
2026-04-01 20:30 ` Lizhi Hou
2026-04-02 5:24 ` Lizhi Hou
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=acymcah+Wlt/T4sL@gsse-cloud1.jf.intel.com \
--to=matthew.brost@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.hou@amd.com \
--cc=maciej.falkowski@linux.intel.com \
--cc=mario.limonciello@amd.com \
--cc=max.zhen@amd.com \
--cc=ogabbay@kernel.org \
--cc=quic_jhugo@quicinc.com \
--cc=sonal.santan@amd.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