Sent out on Thursday along with [1]Intel's huge Xe driver pull request with new features was the drm-misc-next material for the week. Notable with the drm-misc-next code were actually a set of AMDGPU driver patches to enhance the debugging with the information exposed via the DebugFS interface.

This week's drm-misc-next pull brought some improvements to the ASpeed AST driver, adapting VKMS to use [2]the faux interface , and then DebugFS improvements for AMDGPU.

The AMDGPU DebugFS work is for enabling the debug information access based on the unique client ID. AMD engineer Sunil Khatri summed up in that DebugFS client-id patch series work for this AMDGPU Direct Rendering Manager driver:

"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."

The queued patches for drm-misc-next add that DebugFS support on a per client-ID basis and then wiring up DebugFS support for VM pagetable per-client information, support for MQD information, and various fixes. In turn useful for use with user-space solutions like [3]the AMD UMR debugger .

[4]

See [5]this pull request for the full list of drm-misc-next material for the week that is destined for introduction in the upcoming Linux 6.17 cycle.



[1] https://www.phoronix.com/news/Intel-Xe-Driver-Linux-6.17-Big

[2] https://www.phoronix.com/news/Linux-6.14-Faux-Bus-Merged

[3] https://www.phoronix.com/news/AMDGPU-UMR-Debugger-Opens

[4] https://www.phoronix.com/image-viewer.php?id=2025&image=amdgpu_debugfs_lrg

[5] https://lore.kernel.org/dri-devel/20250710-observant-elite-dingo-acfd6d@houat/