[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250108210259.647030-5-adrian.larumbe@collabora.com>
Date: Wed, 8 Jan 2025 21:02:41 +0000
From: Adrián Larumbe <adrian.larumbe@...labora.com>
To: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...il.com>,
Simona Vetter <simona@...ll.ch>,
Jonathan Corbet <corbet@....net>
Cc: kernel@...labora.com,
Adrián Larumbe <adrian.larumbe@...labora.com>,
Tvrtko Ursulin <tursulin@...ulin.net>,
dri-devel@...ts.freedesktop.org,
linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org,
Mihail Atanassov <mihail.atanassov@....com>,
Liviu Dudau <liviu.dudau@....com>,
Steven Price <steven.price@....com>
Subject: [PATCH v7 4/4] Documentation/gpu: Add fdinfo meanings of drm-*-internal memory tags
A previous commit enabled display of driver-internal kernel BO sizes
through the device file's fdinfo interface.
Expand the description of the relevant driver-specific key:value pairs
with the definitions of the new panthor-*-memory ones.
Reviewed-by: Mihail Atanassov <mihail.atanassov@....com>
Reviewed-by: Liviu Dudau <liviu.dudau@....com>
Reviewed-by: Steven Price <steven.price@....com>
Signed-off-by: Adrián Larumbe <adrian.larumbe@...labora.com>
---
Documentation/gpu/panthor.rst | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/Documentation/gpu/panthor.rst b/Documentation/gpu/panthor.rst
index 3f8979fa2b86..76e03304fe7a 100644
--- a/Documentation/gpu/panthor.rst
+++ b/Documentation/gpu/panthor.rst
@@ -26,6 +26,8 @@ the currently possible format options:
drm-cycles-panthor: 94439687187
drm-maxfreq-panthor: 1000000000 Hz
drm-curfreq-panthor: 1000000000 Hz
+ panthor-resident-memory: 10396 KiB
+ panthor-active-memory: 10396 KiB
drm-total-memory: 16480 KiB
drm-shared-memory: 0
drm-active-memory: 16200 KiB
@@ -44,3 +46,11 @@ driver by writing into the appropriate sysfs node::
Where `N` is a bit mask where cycle and timestamp sampling are respectively
enabled by the first and second bits.
+
+Possible `panthor-*-memory` keys are: `active` and `resident`.
+These values convey the sizes of the internal driver-owned shmem BO's that
+aren't exposed to user-space through a DRM handle, like queue ring buffers,
+sync object arrays and heap chunks. Because they are all allocated and pinned
+at creation time, only `panthor-resident-memory` is necessary to tell us their
+size. `panthor-resident-active` shows the size of kernel BO's associated with
+VM's and groups currently being scheduled for execution by the GPU.
--
2.47.1
Powered by blists - more mailing lists