From: Rob Clark <robdclark@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org,
Boris Brezillon <boris.brezillon@collabora.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Christopher Healy <healych@amazon.com>,
Rob Clark <robdclark@chromium.org>,
linux-doc@vger.kernel.org (open list:DOCUMENTATION),
linux-kernel@vger.kernel.org (open list),
Sean Paul <sean@poorly.run>
Subject: [RFC 0/2] drm: fdinfo memory stats
Date: Thu, 6 Apr 2023 14:59:15 -0700 [thread overview]
Message-ID: <20230406215917.1475704-1-robdclark@gmail.com> (raw)
From: Rob Clark <robdclark@chromium.org>
Similar motivation to other similar recent attempt[1]. But with an
attempt to have some shared code for this. As well as documentation.
It is probably a bit UMA-centric, I guess devices with VRAM might want
some placement stats as well. But this seems like a reasonable start.
TODO gputop support?
[1] https://patchwork.freedesktop.org/series/112397/
Rob Clark (2):
drm: Add fdinfo memory stats
drm/msm: Add memory stats to fdinfo
Documentation/gpu/drm-usage-stats.rst | 21 +++++++
drivers/gpu/drm/drm_file.c | 79 +++++++++++++++++++++++++++
drivers/gpu/drm/msm/msm_drv.c | 26 ++++++++-
drivers/gpu/drm/msm/msm_gpu.c | 2 -
include/drm/drm_file.h | 10 ++++
5 files changed, 135 insertions(+), 3 deletions(-)
--
2.39.2
WARNING: multiple messages have this Message-ID (diff)
From: Rob Clark <robdclark@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: Rob Clark <robdclark@chromium.org>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
linux-arm-msm@vger.kernel.org,
Christopher Healy <healych@amazon.com>,
open list <linux-kernel@vger.kernel.org>,
Sean Paul <sean@poorly.run>,
Boris Brezillon <boris.brezillon@collabora.com>,
freedreno@lists.freedesktop.org
Subject: [RFC 0/2] drm: fdinfo memory stats
Date: Thu, 6 Apr 2023 14:59:15 -0700 [thread overview]
Message-ID: <20230406215917.1475704-1-robdclark@gmail.com> (raw)
From: Rob Clark <robdclark@chromium.org>
Similar motivation to other similar recent attempt[1]. But with an
attempt to have some shared code for this. As well as documentation.
It is probably a bit UMA-centric, I guess devices with VRAM might want
some placement stats as well. But this seems like a reasonable start.
TODO gputop support?
[1] https://patchwork.freedesktop.org/series/112397/
Rob Clark (2):
drm: Add fdinfo memory stats
drm/msm: Add memory stats to fdinfo
Documentation/gpu/drm-usage-stats.rst | 21 +++++++
drivers/gpu/drm/drm_file.c | 79 +++++++++++++++++++++++++++
drivers/gpu/drm/msm/msm_drv.c | 26 ++++++++-
drivers/gpu/drm/msm/msm_gpu.c | 2 -
include/drm/drm_file.h | 10 ++++
5 files changed, 135 insertions(+), 3 deletions(-)
--
2.39.2
next reply other threads:[~2023-04-06 22:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 21:59 Rob Clark [this message]
2023-04-06 21:59 ` [RFC 0/2] drm: fdinfo memory stats Rob Clark
2023-04-06 21:59 ` [RFC 1/2] drm: Add " Rob Clark
2023-04-06 21:59 ` Rob Clark
2023-04-07 0:21 ` kernel test robot
2023-04-07 4:17 ` kernel test robot
2023-04-08 12:20 ` Emil Velikov
2023-04-08 12:20 ` Emil Velikov
2023-04-10 19:01 ` Rob Clark
2023-04-10 19:01 ` Rob Clark
2023-04-11 7:54 ` Boris Brezillon
2023-04-11 7:54 ` Boris Brezillon
2023-04-06 21:59 ` [RFC 2/2] drm/msm: Add memory stats to fdinfo Rob Clark
2023-04-06 21:59 ` Rob Clark
2023-04-08 12:28 ` Emil Velikov
2023-04-08 12:28 ` Emil Velikov
2023-04-09 15:59 ` Rob Clark
2023-04-09 15:59 ` Rob Clark
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=20230406215917.1475704-1-robdclark@gmail.com \
--to=robdclark@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=healych@amazon.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@chromium.org \
--cc=sean@poorly.run \
--cc=tvrtko.ursulin@linux.intel.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.