From: "Adrián 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>, Daniel Vetter <daniel@ffwll.ch>
Cc: kernel@collabora.com,
Adrian Larumbe <adrian.larumbe@collabora.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] Support fdinfo runtime and memory stats on Panthor
Date: Tue, 23 Apr 2024 22:32:33 +0100 [thread overview]
Message-ID: <20240423213240.91412-1-adrian.larumbe@collabora.com> (raw)
This patch series enables userspace utilities like gputop and nvtop to
query a render context's fdinfo file and figure out rates of engine
and memory utilisation.
Changelog:
v2:
- Split original first patch in two, one for FW CS cycle and timestamp
calculations and job accounting memory management, and a second one
that enables fdinfo.
- Moved NUM_INSTRS_PER_SLOT to the file prelude
- Removed nelem variable from the group's struct definition.
- Precompute size of group's syncobj BO to avoid code duplication.
- Some minor nits.
Adrián Larumbe (3):
drm/panthor: introduce job cycle and timestamp accounting
drm/panthor: Add DRM fdinfo support
drm/panthor: Enable fdinfo for memory stats
drivers/gpu/drm/panthor/panthor_devfreq.c | 10 ++
drivers/gpu/drm/panthor/panthor_device.h | 11 ++
drivers/gpu/drm/panthor/panthor_drv.c | 31 ++++
drivers/gpu/drm/panthor/panthor_gem.c | 12 ++
drivers/gpu/drm/panthor/panthor_sched.c | 204 +++++++++++++++++++---
5 files changed, 244 insertions(+), 24 deletions(-)
base-commit: a6325ad47bc808aeb4c69ae36e0236c2c6d400b5
--
2.44.0
next reply other threads:[~2024-04-23 21:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 21:32 Adrián Larumbe [this message]
2024-04-23 21:32 ` [PATCH v2 1/3] drm/panthor: introduce job cycle and timestamp accounting Adrián Larumbe
2024-04-24 6:48 ` Boris Brezillon
2024-04-24 15:48 ` Liviu Dudau
2024-04-23 21:32 ` [PATCH v2 2/3] drm/panthor: Add DRM fdinfo support Adrián Larumbe
2024-04-23 21:32 ` [PATCH v2 3/3] drm/panthor: Enable fdinfo for memory stats Adrián Larumbe
2024-04-24 17:34 ` Liviu Dudau
2024-05-16 22:33 ` 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=20240423213240.91412-1-adrian.larumbe@collabora.com \
--to=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=daniel@ffwll.ch \
--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=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®