From: "Adrián Martínez Larumbe" <adrian.larumbe@collabora.com>
To: 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>
Cc: Cc: kernel@collabora.com,
"Adrián Larumbe" <adrian.larumbe@collabora.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org;
Subject: [PATCH v5 0/2] drm/panthor: Display size of internal kernel BOs through fdinfo
Date: Thu, 19 Dec 2024 02:18:40 +0800 [thread overview]
Message-ID: <20241218181844.886043-1-adrian.larumbe@collabora.com> (raw)
This patch series enables display of the size of driver-owned shmem BO's that aren't
exposed to userspace through a DRM handle.
Discussion of previous revision can be found here [1].
Changelog:
v5:
- Replaced down_write semaphore with the read flavour
- Fixed typo and added explicit description for drm-shared-internal in
the fdinfo documentation file for Panthor.
v4:
- Remove unrelated formating fix
- Moved calculating overall size of a group's kernel BO's into
its own static helper.
- Renamed group kernel BO's size aggregation function to better
reflect its actual responsibility.
[1] https://lore.kernel.org/dri-devel/20241211163436.381069-1-adrian.larumbe@collabora.com/
Adrián Larumbe (2):
drm/panthor: Expose size of driver internal BO's over fdinfo
Documentation/gpu: Add fdinfo meanings of drm-*-internal memory tags
Documentation/gpu/panthor.rst | 14 +++++++
drivers/gpu/drm/panthor/panthor_drv.c | 12 ++++++
drivers/gpu/drm/panthor/panthor_heap.c | 26 +++++++++++++
drivers/gpu/drm/panthor/panthor_heap.h | 2 +
drivers/gpu/drm/panthor/panthor_mmu.c | 35 +++++++++++++++++
drivers/gpu/drm/panthor/panthor_mmu.h | 4 ++
drivers/gpu/drm/panthor/panthor_sched.c | 52 ++++++++++++++++++++++++-
drivers/gpu/drm/panthor/panthor_sched.h | 4 ++
8 files changed, 148 insertions(+), 1 deletion(-)
base-commit: 6a8d72b80807ad45229c0f5a17e3be843b15a703
--
2.47.0
next reply other threads:[~2024-12-18 18:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 18:18 Adrián Martínez Larumbe [this message]
2024-12-18 18:18 ` [PATCH v5 1/2] drm/panthor: Expose size of driver internal BO's over fdinfo Adrián Martínez Larumbe
2024-12-18 19:14 ` Adrián Larumbe
2024-12-20 11:12 ` Steven Price
2024-12-19 16:30 ` Mihail Atanassov
2024-12-20 11:08 ` Steven Price
2024-12-20 11:14 ` Mihail Atanassov
2025-01-02 20:35 ` Adrián Martínez Larumbe
2024-12-20 21:06 ` kernel test robot
2024-12-18 18:18 ` [PATCH v5 2/2] Documentation/gpu: Add fdinfo meanings of drm-*-internal memory tags Adrián Martínez Larumbe
2024-12-19 13:06 ` Liviu Dudau
2024-12-20 11:13 ` Steven Price
2025-01-02 21:59 ` Tvrtko Ursulin
2025-01-02 22:18 ` Adrián Martínez Larumbe
2025-01-03 10:49 ` Tvrtko Ursulin
2025-01-06 16:53 ` Adrián Martínez Larumbe
2025-01-07 10:43 ` Tvrtko Ursulin
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=20241218181844.886043-1-adrian.larumbe@collabora.com \
--to=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@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=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®