From: "Christian König" <christian.koenig@amd.com>
To: Rob Clark <robdclark@gmail.com>, dri-devel@lists.freedesktop.org
Cc: "open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
"Michel Dänzer" <mdaenzer@redhat.com>,
"YiPeng Chai" <YiPeng.Chai@amd.com>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Rob Clark" <robdclark@chromium.org>,
"Guchun Chen" <guchun.chen@amd.com>,
"open list:RADEON and AMDGPU DRM DRIVERS"
<amd-gfx@lists.freedesktop.org>,
"Russell King" <linux+etnaviv@armlinux.org.uk>,
"Arunpravin Paneer Selvam" <Arunpravin.PaneerSelvam@amd.com>,
linux-arm-msm@vger.kernel.org, intel-gfx@lists.freedesktop.org,
"moderated list:DRM DRIVERS FOR VIVANTE GPU IP"
<etnaviv@lists.freedesktop.org>,
"Christian Gmeiner" <christian.gmeiner@gmail.com>,
"Evan Quan" <evan.quan@amd.com>,
"Christopher Healy" <healych@amazon.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
freedreno@lists.freedesktop.org,
"Hawking Zhang" <Hawking.Zhang@amd.com>
Subject: Re: [Intel-gfx] [PATCH v3 0/7] drm: fdinfo memory stats
Date: Wed, 12 Apr 2023 11:34:44 +0200 [thread overview]
Message-ID: <bbbbbf34-2ea5-5344-30db-f976c5198d75@amd.com> (raw)
In-Reply-To: <20230411225725.2032862-1-robdclark@gmail.com>
Am 12.04.23 um 00:56 schrieb Rob Clark:
> 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/
I think the extra client id looks a bit superfluous since the ino of the
file should already be unique and IIRC we have been already using that one.
Apart from that looks good to me,
Christian.
PS: For some reason only the two patches I was CCed on ended up in my
inbox, dri-devel swallowed all the rest and hasn't spit it out yet. Had
to dig up the rest from patchwork.
>
> Rob Clark (7):
> drm: Add common fdinfo helper
> drm/msm: Switch to fdinfo helper
> drm/amdgpu: Switch to fdinfo helper
> drm/i915: Switch to fdinfo helper
> drm/etnaviv: Switch to fdinfo helper
> drm: Add fdinfo memory stats
> drm/msm: Add memory stats to fdinfo
>
> Documentation/gpu/drm-usage-stats.rst | 21 ++++
> drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 3 +-
> drivers/gpu/drm/amd/amdgpu/amdgpu_fdinfo.c | 16 ++-
> drivers/gpu/drm/amd/amdgpu/amdgpu_fdinfo.h | 2 +-
> drivers/gpu/drm/drm_file.c | 115 +++++++++++++++++++++
> drivers/gpu/drm/etnaviv/etnaviv_drv.c | 10 +-
> drivers/gpu/drm/i915/i915_driver.c | 3 +-
> drivers/gpu/drm/i915/i915_drm_client.c | 18 +---
> drivers/gpu/drm/i915/i915_drm_client.h | 2 +-
> drivers/gpu/drm/msm/msm_drv.c | 11 +-
> drivers/gpu/drm/msm/msm_gem.c | 15 +++
> drivers/gpu/drm/msm/msm_gpu.c | 2 -
> include/drm/drm_drv.h | 7 ++
> include/drm/drm_file.h | 5 +
> include/drm/drm_gem.h | 19 ++++
> 15 files changed, 208 insertions(+), 41 deletions(-)
>
next prev parent reply other threads:[~2023-04-12 9:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 22:56 [Intel-gfx] [PATCH v3 0/7] drm: fdinfo memory stats Rob Clark
2023-04-11 22:56 ` [Intel-gfx] [PATCH v3 4/7] drm/i915: Switch to fdinfo helper Rob Clark
2023-04-12 12:32 ` Tvrtko Ursulin
2023-04-12 13:51 ` Daniel Vetter
2023-04-12 15:12 ` Tvrtko Ursulin
2023-04-12 18:13 ` Daniel Vetter
2023-04-12 9:34 ` Christian König [this message]
2023-04-12 12:10 ` [Intel-gfx] [PATCH v3 0/7] drm: fdinfo memory stats Tvrtko Ursulin
2023-04-12 12:22 ` Christian König
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=bbbbbf34-2ea5-5344-30db-f976c5198d75@amd.com \
--to=christian.koenig@amd.com \
--cc=Arunpravin.PaneerSelvam@amd.com \
--cc=Hawking.Zhang@amd.com \
--cc=YiPeng.Chai@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.gmeiner@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=evan.quan@amd.com \
--cc=freedreno@lists.freedesktop.org \
--cc=guchun.chen@amd.com \
--cc=healych@amazon.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux+etnaviv@armlinux.org.uk \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mdaenzer@redhat.com \
--cc=robdclark@chromium.org \
--cc=robdclark@gmail.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