On Mon May 18, 2026 at 9:39 AM CEST, Alvin Sun wrote: > A generic Debug impl for GemObject? Other drivers like Nova might need > different > output in a different style.
Why is any of Tyr or Nova special here? There's already a lot of common debugfs code in DRM [1] (which is per DRM device), including some GEM info. If that is not enough, why can't we extend it / add another entry? > How about a dedicated debugfs data structure for GEM Object instead? Say, a > get_debugfs_info() method that handles synchronization internally and avoids > exposing unnecessary interfaces? It would need to be guarded with a debugfs config, otherwise we'd still expose information a driver should never touch directly, which can easily become a bit messy. But again, why do we expect any of those drivers to be special? I think this can just be common code. [1] https://elixir.bootlin.com/linux/v7.0.8/source/drivers/gpu/drm/drm_debugfs.c
