| Message ID | 20230417201215.448099-1-robdclark@gmail.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | drm: Add comm/cmdline fdinfo fields | expand |
On Mon, Apr 17, 2023 at 1:12 PM Rob Clark <robdclark@gmail.com> wrote: > > 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. I should have also mentioned, in the VM/proxy scenario we have a single process with separate drm_file's for each guest VM process. So it isn't an option to just change the proxy process's name to match the client. > 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 >
Looks like the 'PATCH' part of your subject was cut off! Konrad On 17.04.2023 22:12, Rob Clark wrote: > 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(-) >
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(-)