Bug 26565

Summary:	drm/radeon Files in debugfs only available for first GPU
Product:	DRI	Reporter:	Rafael Monica <monraaf>
Component:	DRM/Radeon	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED MOVED	QA Contact:
Severity:	enhancement
Priority:	low
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Rafael Monica 2010-02-14 10:10:16 UTC

The radeon files in /sys/kernel/debug/dri/*/ are only available for the first GPU. Possible solution is to move the static _radeon_debugfs array into rdev, so that each GPU get its own.

ls -l  /sys/kernel/debug/dri/0/

-r--r--r-- 1 root root 0 2010-02-14 10:11 bufs
-r--r--r-- 1 root root 0 2010-02-14 10:11 clients
-r--r--r-- 1 root root 0 2010-02-14 10:11 gem_names
-r--r--r-- 1 root root 0 2010-02-14 10:11 gem_objects
-r--r--r-- 1 root root 0 2010-02-14 10:11 name
-r--r--r-- 1 root root 0 2010-02-14 10:11 queues
-r--r--r-- 1 root root 0 2010-02-14 10:11 r600_mc_info
-r--r--r-- 1 root root 0 2010-02-14 10:11 r600_ring_info
-r--r--r-- 1 root root 0 2010-02-14 10:11 radeon_fence_info
[...]
-r--r--r-- 1 root root 0 2010-02-14 10:11 vm
-r--r--r-- 1 root root 0 2010-02-14 10:11 vma

ls -l  /sys/kernel/debug/dri/1/

-r--r--r-- 1 root root 0 2010-02-14 10:11 bufs
-r--r--r-- 1 root root 0 2010-02-14 10:11 clients
-r--r--r-- 1 root root 0 2010-02-14 10:11 gem_names
-r--r--r-- 1 root root 0 2010-02-14 10:11 gem_objects
-r--r--r-- 1 root root 0 2010-02-14 10:11 name
-r--r--r-- 1 root root 0 2010-02-14 10:11 queues
-r--r--r-- 1 root root 0 2010-02-14 10:11 vm
-r--r--r-- 1 root root 0 2010-02-14 10:11 vma

Comment 1 Martin Peres 2019-11-19 08:10:17 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/100.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.