From: "Adrián Larumbe" <adrian.larumbe@collabora.com>
To: "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>,
"Rob Clark" <robdclark@gmail.com>,
"Abhinav Kumar" <quic_abhinavk@quicinc.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"Sean Paul" <sean@poorly.run>,
"Marijn Suijten" <marijn.suijten@somainline.org>,
"Boris Brezillon" <boris.brezillon@collabora.com>,
"Rob Herring" <robh@kernel.org>,
"Steven Price" <steven.price@arm.com>,
"Melissa Wen" <mwen@igalia.com>,
"Maíra Canal" <mcanal@igalia.com>
Cc: "Adrián Larumbe" <adrian.larumbe@collabora.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org
Subject: [RFC PATCH 0/2] Allow fdinfo to display size of internal BO's
Date: Thu, 3 Oct 2024 00:45:09 +0100 [thread overview]
Message-ID: <20241002234531.3113431-1-adrian.larumbe@collabora.com> (raw)
This patch series lets DRM fdinfo stats functions display an additional tag
that will reflect the amount of memory internal BOs of a DRM driver take
up.
The rationale for this is that some drivers, like Panthor, need quite a bit
of memory for things like queue ring buffers or tiler heap chunks, and
these will vary dynamically as new scheduler groups, queues or heap chunks
are created by one or more render contexts.
Because these are tied to an open DRM file that represents an ongoing
render context, then it makes sense to provide users with this information
in the DRM file fdinfo descriptor, even though they would never be exposed
to UM through a handle.
These two patches were originally part of a wider series, but broke it down
into two different submissions for ease of discussion.
The previous debate can be found at [1], in its latest two patches.
[1] https://lore.kernel.org/dri-devel/dqhnxhgho6spfh7xhw6yvs2iiqeqzeg63e6jqqpw2g7gkrfphn@dojsixyl4esv/
Adrián Larumbe (2):
drm/drm_file: Add display of driver's internal memory size
drm/panthor: register size of internal objects through fdinfo
drivers/gpu/drm/drm_file.c | 6 ++-
drivers/gpu/drm/msm/msm_drv.c | 2 +-
drivers/gpu/drm/panfrost/panfrost_drv.c | 2 +-
drivers/gpu/drm/panthor/panthor_device.c | 2 +
drivers/gpu/drm/panthor/panthor_device.h | 6 +++
drivers/gpu/drm/panthor/panthor_drv.c | 16 +++++--
drivers/gpu/drm/panthor/panthor_fw.c | 14 ++++--
drivers/gpu/drm/panthor/panthor_fw.h | 6 ++-
drivers/gpu/drm/panthor/panthor_gem.c | 55 ++++++++++++++++++++++--
drivers/gpu/drm/panthor/panthor_gem.h | 15 ++++++-
drivers/gpu/drm/panthor/panthor_heap.c | 20 ++++++---
drivers/gpu/drm/panthor/panthor_heap.h | 6 ++-
drivers/gpu/drm/panthor/panthor_mmu.c | 7 ++-
drivers/gpu/drm/panthor/panthor_mmu.h | 3 +-
drivers/gpu/drm/panthor/panthor_sched.c | 19 ++++----
drivers/gpu/drm/v3d/v3d_drv.c | 2 +-
include/drm/drm_file.h | 7 ++-
17 files changed, 150 insertions(+), 38 deletions(-)
--
2.46.2
next reply other threads:[~2024-10-02 23:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 23:45 Adrián Larumbe [this message]
2024-10-02 23:45 ` [RFC PATCH 1/2] drm/drm_file: Add display of driver's internal memory size Adrián Larumbe
2024-10-04 13:41 ` Tvrtko Ursulin
2024-10-09 22:55 ` Adrián Larumbe
2024-10-10 9:50 ` Tvrtko Ursulin
2024-10-15 19:05 ` Adrián Larumbe
2024-10-16 8:07 ` Tvrtko Ursulin
2024-10-28 13:52 ` Adrián Larumbe
2024-10-02 23:45 ` [RFC PATCH 2/2] drm/panthor: register size of internal objects through fdinfo 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=20241002234531.3113431-1-adrian.larumbe@collabora.com \
--to=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=mcanal@igalia.com \
--cc=mripard@kernel.org \
--cc=mwen@igalia.com \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robh@kernel.org \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
--cc=steven.price@arm.com \
--cc=tursulin@ursulin.net \
--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®