From: "Adrián Larumbe" <adrian.larumbe@collabora.com>
To: linux-kernel@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org,
"Boris Brezillon" <boris.brezillon@collabora.com>,
kernel@collabora.com,
"Adrián Larumbe" <adrian.larumbe@collabora.com>
Subject: [PATCH v2 0/3] Panfrost BO tagging and GEMS debug display
Date: Wed, 7 May 2025 17:07:06 +0100 [thread overview]
Message-ID: <20250507160713.1363985-1-adrian.larumbe@collabora.com> (raw)
This patch series is a Panfrost port of the already merged patches
previously discussed at [1].
The differences are minimal. However, Panfrost doesn't have Kernel-only BO's, so all the
functionality that dealt with them has been removed.
The under-discussion Mesa MR that would allow one to test these changes can be found at [2].
The way BO flags is printed is also slightly different.
Discussion of previous version in the series can be found at [3]
Changelog:
v2:
- Introduced u64_to_user_ptr() for casting user pointers
- Refined documentation for uAPI bo labelling struct fields
- Moved panfrost device debugfs struct fields into a single debugfs struct
- Add BO to debugfs GEMs list right before creating its handle to avoid unnecessary initialised field.
[1] https://lore.kernel.org/dri-devel/20250418022710.74749-1-adrian.larumbe@collabora.com/
[2] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/34224
[3] https://lore.kernel.org/dri-devel/20250424022138.709303-1-adrian.larumbe@collabora.com/T/#t
Adrián Larumbe (3):
drm/panfrost: Add BO labelling to Panfrost
drm/panfrost: Add driver IOCTL for setting BO labels
drm/panfrost: show device-wide list of DRM GEM objects over DebugFS
drivers/gpu/drm/panfrost/panfrost_device.c | 5 +
drivers/gpu/drm/panfrost/panfrost_device.h | 15 ++
drivers/gpu/drm/panfrost/panfrost_drv.c | 79 ++++++++++-
drivers/gpu/drm/panfrost/panfrost_gem.c | 154 +++++++++++++++++++++
drivers/gpu/drm/panfrost/panfrost_gem.h | 65 +++++++++
include/uapi/drm/panfrost_drm.h | 21 +++
6 files changed, 338 insertions(+), 1 deletion(-)
base-commit: 9ff4fdf4f44b69237c0afc1d3a8dac916ce66f3e
--
2.48.1
next reply other threads:[~2025-05-07 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 16:07 Adrián Larumbe [this message]
2025-05-07 16:07 ` [PATCH v2 1/3] drm/panfrost: Add BO labelling to Panfrost Adrián Larumbe
2025-05-07 16:07 ` [PATCH v2 2/3] drm/panfrost: Add driver IOCTL for setting BO labels Adrián Larumbe
2025-05-07 16:07 ` [PATCH v2 3/3] drm/panfrost: show device-wide list of DRM GEM objects over DebugFS Adrián Larumbe
2025-05-08 10:42 ` Steven Price
2025-05-15 18:04 ` Daniel Stone
2025-05-19 16:02 ` Steven Price
2025-05-20 12:53 ` Adrián Larumbe
2025-05-20 11:30 ` Adrián Larumbe
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=20250507160713.1363985-1-adrian.larumbe@collabora.com \
--to=adrian.larumbe@collabora.com \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®