From: "Adrián Larumbe" <adrian.larumbe@collabora.com>
To: ?UTF-8?q?Adri=C3=A1n=20Larumbe?= <adrian.larumbe@collabora.com>,
"Boris Brezillon" <boris.brezillon@collabora.com>,
"Steven Price" <steven.price@arm.com>,
"Liviu Dudau" <liviu.dudau@arm.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>
Cc: kernel@collabora.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linaro-mm-sig@lists.linaro.org
Subject: [PATCH v3 0/4] Panthor BO tagging and GEMS debug display
Date: Thu, 27 Mar 2025 14:08:33 +0000 [thread overview]
Message-ID: <20250327140845.105962-1-adrian.larumbe@collabora.com> (raw)
This patch series is aimed at providing UM with detailed memory profiling
information in debug builds. It is achieved through a device-wide list of
DRM GEM objects, and also implementing the ability to label BO's from UM
through a new IOCTL.
The new debugfs file shows a list of driver DRM GEM objects in tabular mode.
To visualise it, cat sudo cat /sys/kernel/debug/dri/*.gpu/gems.
To test this functionality from UM, please refer to this Mesa patch series:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/34224
Changelog:
v3:
- Replaced kfree() with kfree_const() when freeing a bo label
- Rearranged functions for delaing with GEMs list adding and deleting
- Changed Kernel BO labelling format not to include quotes
- Return error in labelling ioctl when string length is too long
Adrián Larumbe (4):
drm/panthor: Introduce BO labeling
drm/panthor: Add driver IOCTL for setting BO labels
drm/panthor: show device-wide list of DRM GEM objects over DebugFS
drm/panthor: Display heap chunk entries in DebugFS GEMS file
drivers/gpu/drm/panthor/panthor_device.c | 5 +
drivers/gpu/drm/panthor/panthor_device.h | 11 ++
drivers/gpu/drm/panthor/panthor_drv.c | 66 ++++++++++
drivers/gpu/drm/panthor/panthor_gem.c | 158 +++++++++++++++++++++++
drivers/gpu/drm/panthor/panthor_gem.h | 60 +++++++++
drivers/gpu/drm/panthor/panthor_heap.c | 3 +
include/uapi/drm/panthor_drm.h | 19 +++
7 files changed, 322 insertions(+)
--
2.48.1
next reply other threads:[~2025-03-27 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 14:08 Adrián Larumbe [this message]
2025-03-27 14:08 ` [PATCH v3 1/4] drm/panthor: Introduce BO labeling Adrián Larumbe
2025-03-27 14:08 ` [PATCH v3 2/4] drm/panthor: Add driver IOCTL for setting BO labels Adrián Larumbe
2025-03-27 14:08 ` [PATCH v3 3/4] drm/panthor: show device-wide list of DRM GEM objects over DebugFS Adrián Larumbe
2025-03-28 14:30 ` Boris Brezillon
2025-04-02 12:09 ` Adrián Larumbe
2025-03-27 14:08 ` [PATCH v3 4/4] drm/panthor: Display heap chunk entries in DebugFS GEMS file 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=20250327140845.105962-1-adrian.larumbe@collabora.com \
--to=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=steven.price@arm.com \
--cc=sumit.semwal@linaro.org \
--cc=tzimmermann@suse.de \
/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®