From: Rob Clark <robdclark@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Rob Clark <robdclark@chromium.org>,
Akhil P Oommen <quic_akhilpo@quicinc.com>,
Chia-I Wu <olvaffe@gmail.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
freedreno@lists.freedesktop.org (open list:DRM DRIVER FOR MSM
ADRENO GPU), Konrad Dybcio <konrad.dybcio@linaro.org>,
linux-arm-msm@vger.kernel.org (open list:DRM DRIVER FOR MSM
ADRENO GPU), linux-doc@vger.kernel.org (open list:DOCUMENTATION),
linux-kernel@vger.kernel.org (open list),
Sean Paul <sean@poorly.run>
Subject: [RFC 0/3] drm: Add comm/cmdline fdinfo fields
Date: Mon, 17 Apr 2023 13:12:09 -0700 [thread overview]
Message-ID: <20230417201215.448099-1-robdclark@gmail.com> (raw)
From: Rob Clark <robdclark@chromium.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
next reply other threads:[~2023-04-17 20:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 20:12 Rob Clark [this message]
2023-04-17 20:12 ` [RFC 1/3] drm/doc: Relax fdinfo string constraints Rob Clark
2023-04-18 8:19 ` Tvrtko Ursulin
2023-04-17 20:12 ` [RFC 2/3] drm/msm: Rework get_comm_cmdline() helper Rob Clark
2023-04-18 8:27 ` Tvrtko Ursulin
2023-04-18 8:34 ` Daniel Vetter
2023-04-18 14:31 ` Rob Clark
2023-04-21 9:33 ` Emil Velikov
2023-04-21 14:47 ` Rob Clark
2023-04-27 9:39 ` Daniel Vetter
2023-04-27 14:31 ` Rob Clark
2023-04-17 20:12 ` [RFC 3/3] drm/msm: Add comm/cmdline fields Rob Clark
2023-04-18 8:53 ` Tvrtko Ursulin
2023-04-18 14:56 ` Rob Clark
2023-04-19 13:36 ` Tvrtko Ursulin
2023-04-19 15:00 ` Rob Clark
2023-04-17 20:45 ` [RFC 0/3] drm: Add comm/cmdline fdinfo fields Rob Clark
2023-04-18 9:33 ` Konrad Dybcio
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=20230417201215.448099-1-robdclark@gmail.com \
--to=robdclark@gmail.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olvaffe@gmail.com \
--cc=quic_akhilpo@quicinc.com \
--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