[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230417201215.448099-1-robdclark@gmail.com>
Date: Mon, 17 Apr 2023 13:12:09 -0700
From: Rob Clark <robdclark@...il.com>
To: dri-devel@...ts.freedesktop.org
Cc: Tvrtko Ursulin <tvrtko.ursulin@...ux.intel.com>,
Rob Clark <robdclark@...omium.org>,
Akhil P Oommen <quic_akhilpo@...cinc.com>,
Chia-I Wu <olvaffe@...il.com>,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
freedreno@...ts.freedesktop.org (open list:DRM DRIVER FOR MSM ADRENO
GPU), Konrad Dybcio <konrad.dybcio@...aro.org>,
linux-arm-msm@...r.kernel.org (open list:DRM DRIVER FOR MSM ADRENO GPU),
linux-doc@...r.kernel.org (open list:DOCUMENTATION),
linux-kernel@...r.kernel.org (open list),
Sean Paul <sean@...rly.run>
Subject: [RFC 0/3] drm: Add comm/cmdline fdinfo fields
From: Rob Clark <robdclark@...omium.org>
When many of the things using the GPU are processes in a VM guest, the
actual client process is just a proxy. The msm driver has a way to let
the proxy tell the kernel the actual VM client process's executable name
and command-line, which has until now been used simply for GPU crash
devcore dumps. Lets also expose this via fdinfo so that tools can
expose who the actual user of the GPU is.
Rob Clark (3):
drm/doc: Relax fdinfo string constraints
drm/msm: Rework get_comm_cmdline() helper
drm/msm: Add comm/cmdline fields
Documentation/gpu/drm-usage-stats.rst | 37 +++++++++++++++----------
drivers/gpu/drm/msm/adreno/adreno_gpu.c | 4 +--
drivers/gpu/drm/msm/msm_drv.c | 2 ++
drivers/gpu/drm/msm/msm_gpu.c | 27 +++++++++++++-----
drivers/gpu/drm/msm/msm_gpu.h | 12 ++++++--
drivers/gpu/drm/msm/msm_submitqueue.c | 1 +
6 files changed, 58 insertions(+), 25 deletions(-)
--
2.39.2
Powered by blists - more mailing lists