From: Rob Clark <robin.clark@oss.qualcomm.com>
To: dri-devel@lists.freedesktop.org
Cc: linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org,
"Jianfeng Liu" <liujianfeng1994@gmail.com>,
"Christian König" <christian.koenig@amd.com>,
"Rob Clark" <robin.clark@oss.qualcomm.com>,
"Abel Vesa" <abelvesa@kernel.org>,
"Abhinav Kumar" <abhinav.kumar@linux.dev>,
"Andrei Kuchynski" <akuchynski@chromium.org>,
"Benson Leung" <bleung@chromium.org>,
"Chia-Lin Kao (AceLan)" <acelan.kao@canonical.com>,
"David Airlie" <airlied@gmail.com>,
"Dmitry Baryshkov" <lumag@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Heikki Krogerus" <heikki.krogerus@linux.intel.com>,
"Hsin-Te Yuan" <yuanhsinte@chromium.org>,
"Jessica Zhang" <jesszhan0024@gmail.com>,
"Johan Hovold" <johan@kernel.org>,
linaro-mm-sig@lists.linaro.org (moderated list:DMA BUFFER
SHARING FRAMEWORK:Keyword:bdma_(?:buf|fence|resv)b),
linux-kernel@vger.kernel.org (open list),
linux-media@vger.kernel.org (open list:DMA BUFFER SHARING
FRAMEWORK:Keyword:bdma_(?:buf|fence|resv)b),
linux-usb@vger.kernel.org (open list:USB TYPEC CLASS),
"Marijn Suijten" <marijn.suijten@somainline.org>,
"Pooja Katiyar" <pooja.katiyar@intel.com>,
"Sean Paul" <sean@poorly.run>, "Simona Vetter" <simona@ffwll.ch>,
"Sumit Semwal" <sumit.semwal@linaro.org>
Subject: [PATCH 0/6] drm/msm/gem: Drop use of pages for imported dma-bufs
Date: Sat, 26 Sep 2026 11:30:40 -0700 [thread overview]
Message-ID: <20260926183051.25754-1-robin.clark@oss.qualcomm.com> (raw)
The use of msm_obj->pages _mostly_ served to mark that the obj is
resident in memory. Mapping to the GPU, etc, all works in terms of
the sgt.
The exception was the fault path. Resolve this by using dma_buf_mmap()
for mmap'ing imported buffers, like we are supposed to. With that and
a bit more cleanup we can drop the use of drm_prime_sg_to_page_array().
This doesn't solve the issues with DMABUF_DEBUG, mapping to the GPU,
either via iommu_map_sgtable() (display, and TTBR1 for GPU, aka the
kernel managed mappings), or msm_iommu_pagetable_map() (userspace
managed mappings), still requires pages under the hood. That will
be harder to solve. But this is a step along the way.
Lightly tested.. in that I don't actually have a good way to test
importing buffers that weren't first exported by drm/msm. And I'm
headed to XDC soon.
Rob Clark (6):
drm/msm/gem: Add helper to check if resident
drm/msm/gem: Mmap imported dma-bufs via the exporter
drm/msm/gem: Use get_pages() directly in vmap path
drm/msm/gem: Stop exposing a page array
drm/msm/gem: Stop calling get_pages() for imported dma-bufs
drm/msm/gem: Drop use of drm_prime_sg_to_page_array()
drivers/gpu/drm/msm/msm_gem.c | 107 +++++++++++++++++-----------
drivers/gpu/drm/msm/msm_gem.h | 10 ++-
drivers/gpu/drm/msm/msm_gem_prime.c | 5 +-
drivers/gpu/drm/msm/msm_gem_vma.c | 8 +--
4 files changed, 78 insertions(+), 52 deletions(-)
--
2.55.0
next reply other threads:[~2026-09-26 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 18:30 Rob Clark [this message]
2026-09-26 18:30 ` [PATCH 1/6] drm/msm/gem: Add helper to check if resident Rob Clark
2026-09-26 18:30 ` [PATCH 2/6] drm/msm/gem: Mmap imported dma-bufs via the exporter Rob Clark
2026-09-26 18:30 ` [PATCH 3/6] drm/msm/gem: Use get_pages() directly in vmap path Rob Clark
2026-09-26 18:30 ` [PATCH 4/6] drm/msm/gem: Stop exposing a page array Rob Clark
2026-09-26 18:30 ` [PATCH 5/6] drm/msm/gem: Stop calling get_pages() for imported dma-bufs Rob Clark
2026-09-26 18:30 ` [PATCH 6/6] drm/msm/gem: Drop use of drm_prime_sg_to_page_array() Rob Clark
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=20260926183051.25754-1-robin.clark@oss.qualcomm.com \
--to=robin.clark@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=abhinav.kumar@linux.dev \
--cc=acelan.kao@canonical.com \
--cc=airlied@gmail.com \
--cc=akuchynski@chromium.org \
--cc=bleung@chromium.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jesszhan0024@gmail.com \
--cc=johan@kernel.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=liujianfeng1994@gmail.com \
--cc=lumag@kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=pooja.katiyar@intel.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
--cc=sumit.semwal@linaro.org \
--cc=yuanhsinte@chromium.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
all inboxes | Powered by JetHome®