linux-kernel - [PATCH v10 0/4] Enable debugfs information based on client-id

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20250704075548.1549849-1-sunil.khatri@amd.com>
Date: Fri,  4 Jul 2025 13:25:44 +0530
From: Sunil Khatri <sunil.khatri@....com>
To: Christian König <christian.koenig@....com>,
        dri-devel@...ts.freedesktop.org
Cc: amd-gfx@...ts.freedesktop.org, simona@...ll.ch, tzimmermann@...e.de,
        tursulin@...ulin.net, phasta@...nel.org, dakr@...nel.org,
        linux-kernel@...r.kernel.org, Oded Gabbay <ogabbay@...nel.org>,
        Jeff Hugo <jeff.hugo@....qualcomm.com>,
        Jonas Karlman <jonas@...boo.se>,
        Laurent Pinchart <Laurent.pinchart@...asonboard.com>,
        Andrzej Hajda <andrzej.hajda@...el.com>,
        Luca Ceresoli <luca.ceresoli@...tlin.com>,
        Sunil Khatri <sunil.khatri@....com>
Subject: [PATCH v10 0/4] Enable debugfs information based on client-id

client-id is a unique id across the system no matter if its from a VM
or on a host system. This unique id is a good base to use create
client-id based dentry in debugfs in the root directory.

This directory could be a unique directory where drivers could dump
the debug information.

For amdgpu driver, we want to dump the VM PTBASE address and MQD for
userqueue which can be used by a tool like amd umr to dump the memory
and that is really important to debug userqueues and VM related issues.

One of the challenge in this how to access the root directory which is
beyond the drm_device hence moving the debugfs related information to
drm_debugfs.c

v10: rebase patch 1 and patch 3 on the drm-misc-next. In the process
move the drm bridge code to have access to drm root node for patch 1.
for patch 3 remove drm_file from amdgpu_vm_init and call the vm debugfs
function directly before calling the amdgpu_vm_init

Sunil Khatri (4):
  drm: move drm based debugfs funcs to drm_debugfs.c
  drm: add debugfs support on per client-id basis
  drm/amdgpu: add debugfs support for VM pagetable per client
  drm/amdgpu: add support of debugfs for mqd information

 drivers/accel/drm_accel.c                   |  16 ---
 drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c |  52 +++++++++
 drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.h |   1 +
 drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c     |   2 +
 drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c   |  52 +++++++++
 drivers/gpu/drm/amd/amdgpu/amdgpu_userq.h   |   1 +
 drivers/gpu/drm/drm_debugfs.c               | 118 +++++++++++++++++++-
 drivers/gpu/drm/drm_drv.c                   |  16 +--
 drivers/gpu/drm/drm_file.c                  |  11 ++
 drivers/gpu/drm/drm_internal.h              |   6 +-
 include/drm/drm_accel.h                     |   5 -
 include/drm/drm_debugfs.h                   |  11 ++
 include/drm/drm_drv.h                       |  19 +++-
 include/drm/drm_file.h                      |   7 ++
 14 files changed, 273 insertions(+), 44 deletions(-)

-- 
2.34.1