From: Daniel Vetter <daniel@ffwll.ch>
To: Rob Clark <robdclark@gmail.com>
Cc: dri-devel@lists.freedesktop.org,
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,
Emil Velikov <emil.l.velikov@gmail.com>,
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: Re: [PATCH v2 0/2] drm: fdinfo memory stats
Date: Tue, 11 Apr 2023 18:53:17 +0200 [thread overview]
Message-ID: <ZDWQfbUBhyJf1Ezx@phenom.ffwll.local> (raw)
In-Reply-To: <CAF6AEGvs4XMggPMthiJ89SiaUj3k+nY95OhxLZ5cD-01XPco4Q@mail.gmail.com>
On Tue, Apr 11, 2023 at 09:47:32AM -0700, Rob Clark wrote:
> On Mon, Apr 10, 2023 at 2:06 PM Rob Clark <robdclark@gmail.com> wrote:
> >
> > 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
>
> On a related topic, I'm wondering if it would make sense to report
> some more global things (temp, freq, etc) via fdinfo? Some of this,
> tools like nvtop could get by trawling sysfs or other driver specific
> ways. But maybe it makes sense to have these sort of things reported
> in a standardized way (even though they aren't really per-drm_file)
I think that's a bit much layering violation, we'd essentially have to
reinvent the hwmon sysfs uapi in fdinfo. Not really a business I want to
be in :-)
What might be needed is better glue to go from the fd or fdinfo to the
right hw device and then crawl around the hwmon in sysfs automatically. I
would not be surprised at all if we really suck on this, probably more
likely on SoC than pci gpus where at least everything should be under the
main pci sysfs device.
-Daniel
>
> BR,
> -R
>
>
> > [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
> >
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2023-04-11 16:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 21:06 [PATCH v2 0/2] drm: fdinfo memory stats Rob Clark
2023-04-10 21:06 ` [PATCH v2 1/2] drm: Add " 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-11 16:47 ` [PATCH v2 0/2] drm: " Rob Clark
2023-04-11 16:53 ` Daniel Vetter [this message]
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=ZDWQfbUBhyJf1Ezx@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--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=robdclark@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).