From: Tvrtko Ursulin <tursulin@igalia.com>
To: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: kernel-dev@igalia.com, Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
Subject: [PATCH 0/2] DRM fdinfo legacy drm-memory- clarification and amdgpu update
Date: Tue, 13 Aug 2024 14:57:10 +0100 [thread overview]
Message-ID: <20240813135712.82611-1-tursulin@igalia.com> (raw)
From: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
Re-sending these two since they garnered little attention last time round.
First patch clarifies what drm-memory- is, and that it is legacy, and second
patch updates amdgpu to start emitting new keys together with the legacy (by
using the common DRM helper).
With that gputop will show the resident usage (not just total) and as bonus I
added active and purgeable.
Tvrtko Ursulin (2):
Documentation/gpu: Document the situation with unqualified drm-memory-
drm/amdgpu: Use drm_print_memory_stats helper from fdinfo
Documentation/gpu/drm-usage-stats.rst | 25 +++++-
drivers/gpu/drm/amd/amdgpu/amdgpu_fdinfo.c | 48 +++++++----
drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 96 +++++++++++++++-------
drivers/gpu/drm/amd/amdgpu/amdgpu_object.h | 35 +++-----
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.h | 1 +
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 20 +++--
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h | 3 +-
7 files changed, 144 insertions(+), 84 deletions(-)
--
2.44.0
next reply other threads:[~2024-08-13 13:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 13:57 Tvrtko Ursulin [this message]
2024-08-13 13:57 ` [PATCH 1/2] Documentation/gpu: Document the situation with unqualified drm-memory- Tvrtko Ursulin
2024-08-13 18:47 ` Rob Clark
2024-08-15 8:37 ` Tvrtko Ursulin
2024-08-19 14:20 ` Daniel Vetter
2024-08-21 20:47 ` Alex Deucher
2024-09-04 8:36 ` Tvrtko Ursulin
2024-09-06 18:12 ` Alex Deucher
2024-09-09 9:13 ` Tvrtko Ursulin
2024-08-13 13:57 ` [PATCH 2/2] drm/amdgpu: Use drm_print_memory_stats helper from fdinfo Tvrtko Ursulin
2024-08-21 20:43 ` Alex Deucher
2024-08-21 20:48 ` Alex Deucher
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=20240813135712.82611-1-tursulin@igalia.com \
--to=tursulin@igalia.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-dev@igalia.com \
--cc=tvrtko.ursulin@igalia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.