From: Sunil Khatri <sunil.khatri@amd.com>
To: "Christian König" <christian.koenig@amd.com>,
dri-devel@lists.freedesktop.org
Cc: amd-gfx@lists.freedesktop.org, simona@ffwll.ch,
tzimmermann@suse.de, tursulin@ursulin.net, phasta@kernel.org,
dakr@kernel.org, linux-kernel@vger.kernel.org,
Oded Gabbay <ogabbay@kernel.org>,
Jeff Hugo <jeff.hugo@oss.qualcomm.com>,
Sunil Khatri <sunil.khatri@amd.com>
Subject: [PATCH v9 0/4] Enable debugfs information based on client-id
Date: Tue, 1 Jul 2025 22:19:44 +0530 [thread overview]
Message-ID: <20250701164948.8105-1-sunil.khatri@amd.com> (raw)
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
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/amd/amdgpu/amdgpu_vm.c | 4 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h | 4 +-
drivers/gpu/drm/drm_debugfs.c | 113 ++++++++++++++++++--
drivers/gpu/drm/drm_drv.c | 14 +--
drivers/gpu/drm/drm_file.c | 9 ++
drivers/gpu/drm/drm_internal.h | 6 +-
include/drm/drm_accel.h | 5 -
include/drm/drm_debugfs.h | 11 ++
include/drm/drm_drv.h | 14 ++-
include/drm/drm_file.h | 7 ++
16 files changed, 265 insertions(+), 46 deletions(-)
--
2.34.1
next reply other threads:[~2025-07-01 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 16:49 Sunil Khatri [this message]
2025-07-01 16:49 ` [PATCH v9 1/4] drm: move drm based debugfs funcs to drm_debugfs.c Sunil Khatri
2025-07-01 16:49 ` [PATCH v9 2/4] drm: add debugfs support on per client-id basis Sunil Khatri
2025-07-01 16:49 ` [PATCH v9 3/4] drm/amdgpu: add debugfs support for VM pagetable per client Sunil Khatri
2025-07-03 8:00 ` Christian König
2025-07-04 6:52 ` Khatri, Sunil
2025-07-01 16:49 ` [PATCH v9 4/4] drm/amdgpu: add support of debugfs for mqd information Sunil Khatri
2025-07-02 6:21 ` [PATCH v9 0/4] Enable debugfs information based on client-id Philipp Stanner
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=20250701164948.8105-1-sunil.khatri@amd.com \
--to=sunil.khatri@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ogabbay@kernel.org \
--cc=phasta@kernel.org \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®