public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	Emil Velikov <emil.l.velikov@gmail.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: [PATCH v2 0/2] drm: fdinfo memory stats
Date: Mon, 10 Apr 2023 14:06:05 -0700	[thread overview]
Message-ID: <20230410210608.1873968-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.

Basic gputop support: https://patchwork.freedesktop.org/series/116236/
And already nvtop support: https://github.com/Syllo/nvtop/pull/204

[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         | 25 ++++++++-
 drivers/gpu/drm/msm/msm_gpu.c         |  2 -
 include/drm/drm_file.h                | 10 ++++
 5 files changed, 134 insertions(+), 3 deletions(-)

-- 
2.39.2


             reply	other threads:[~2023-04-10 21:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10 21:06 Rob Clark [this message]
2023-04-10 21:06 ` [PATCH v2 1/2] drm: Add fdinfo memory stats Rob Clark
2023-04-11 10:43   ` Daniel Vetter
2023-04-11 15:02     ` Rob Clark
2023-04-11 15:10       ` Daniel Vetter
2023-04-10 21:06 ` [PATCH v2 2/2] drm/msm: Add memory stats to fdinfo Rob Clark
2023-04-11 16:47 ` [PATCH v2 0/2] drm: fdinfo memory stats Rob Clark
2023-04-11 16:53   ` Daniel Vetter
2023-04-11 17:13     ` Rob Clark
2023-04-11 17:35       ` [Freedreno] " Dmitry Baryshkov
2023-04-11 18:26         ` Daniel Vetter
2023-04-11 22:27           ` Dmitry Baryshkov
2023-04-11 18:28         ` Rob Clark
2023-04-11 22:36           ` Dmitry Baryshkov
2023-04-12  8:11             ` Daniel Vetter
2023-04-12 12:47               ` Rodrigo Vivi
2023-04-12 20:09                 ` Rob Clark
2023-04-12 20:19                   ` Dmitry Baryshkov
2023-04-12 20:34                     ` Rob Clark
2023-04-13  0:27                       ` Dmitry Baryshkov
2023-04-12 20:23                   ` 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=20230410210608.1873968-1-robdclark@gmail.com \
    --to=robdclark@gmail.com \
    --cc=boris.brezillon@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox