This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM5728: Understanding the outputs from /sys/kernel/debug/dri/0/gem

Part Number: AM5728


Hello! May I get some explanations for each column from the DRI debug directory?


# cat /sys/kernel/debug/dri/0/gem
All Objects:
02000003: 26 ( 3) 000154c4 0x7a379000 ( 2) (null) 0 7528448
02000003: 27 ( 3) 00014d96 0x7aaa7000 ( 2) (null) 0 7528448
02000003: 4 ( 3) 0001326f 0x7c2f1000 ( 2) (null) 0 2985984
02000003: 3 ( 3) 0001235e 0x7c5ca000 ( 2) (null) 0 2985984
02000003: 24 ( 3) 00012dfa 0x7c8a3000 ( 2) (null) 0 4673536
02000003: 25 ( 3) 00011ee9 0x7cd18000 ( 2) (null) 0 4673536
02000003: 20 ( 3) 00014bce 0x7d18d000 ( 2) (null) 0 1867776
02000003: 21 ( 3) 00014a06 0x7d355000 ( 2) (null) 0 1867776
02000003: 22 ( 3) 0001483e 0x7d51d000 ( 2) (null) 0 1867776
02000003: 23 ( 3) 00014676 0x7d6e5000 ( 2) (null) 0 1867776
02000003: 18 ( 3) 0001289c 0x7dc41000 ( 2) (null) 0 1875968
02000003: 19 ( 3) 000126d2 0x7de0b000 ( 2) (null) 0 1875968
0100000b: 17 ( 3) 000117bb 0xc3200000 ( 0) f637b000 0 7528448
0100000b: 16 ( 2) 00000000 0xc2e00000 ( 0) f5f85000 0 4149248
0100000b: 15 ( 2) 00000000 0xc2a00000 ( 0) f5b8f000 0 4149248
0100000b: 14 ( 2) 00000000 0xc2600000 ( 0) f5799000 0 4149248
0100000b: 13 ( 2) 00000000 0xc2200000 ( 0) f53a3000 0 4149248
0100000b: 12 ( 2) 00000000 0xc1e00000 ( 0) f4fad000 0 4149248
0100000b: 11 ( 2) 00000000 0xc1a00000 ( 0) f4bb7000 0 4149248
0100000b: 10 ( 2) 00000000 0xc1600000 ( 0) f47c1000 0 4149248
0100000b: 9 ( 2) 00000000 0xc1200000 ( 0) f43cb000 0 4149248
0100000b: 8 ( 2) 00000000 0xc0e00000 ( 0) f3fd5000 0 4149248
0100000b: 7 ( 2) 00000000 0xc0a00000 ( 0) f3bdf000 0 4149248
0100000b: 2 ( 2) 00000000 0xc0600000 ( 0) f37e9000 0 4149248
0100000b: 1 ( 2) 00000000 0xc0200000 ( 0) f33f3000 0 4149248
02000003: 5 ( 3) 00013e8d 0x7b1d5000 ( 2) (null) 0 8294400
02000003: 6 ( 3) 000136a4 0x7b9be000 ( 2) (null) 0 8294400
02000003: 0 ( 4) 00010fd2 0x7dfd5000 ( 1) (null) 0 8294400
02000003: 0 ( 4) 000107e9 0x7e7be000 ( 1) (null) 0 8294400
02000003: 0 ( 4) 00010000 0x7efa7000 ( 2) (null) 0 8294400
02000003: 0 ( 1) 00000000 0x7f790000 ( 1) f1bda000 0 8847360
Total 31 objects, 149237760 bytes

# cat /sys/kernel/debug/dri/0/gem_names
name size handles refcount
1 4149248 2 2
2 4149248 2 2
3 2985984 2 3
4 2985984 2 3
5 8294400 2 3
6 8294400 2 3
7 4149248 2 2
8 4149248 2 2
9 4149248 2 2
10 4149248 2 2
11 4149248 2 2
12 4149248 2 2
13 4149248 2 2
14 4149248 2 2
15 4149248 2 2
16 4149248 2 2
17 7528448 2 3
18 1875968 2 3
19 1875968 2 3
20 1867776 2 3
21 1867776 2 3
22 1867776 2 3
23 1867776 2 3
24 4673536 2 3
25 4673536 2 3
26 7528448 2 3
27 7528448 2 3

# cat /sys/kernel/debug/dri/0/clients
command pid dev master a uid magic
weston 1964 0 y y 0 1
Update 2668 0 n y 0 3
S2D 3124 0 n y 0 2
Ui 3359 0 n y 0 4
Video 3738 0 n y 0 0
Kesl 3158 0 n y 0 5
SDI 3134 0 n y 0 6
SSI 3566 0 n y 0 7
S360 3671 0 n y 0 8

I think I am looking to relate the application names from the clients output back to the gem_names.

  • Hi Adam Lee5

    The "gem" file is omapdrm specific one, you can find that in omap_gem.c omap_gem_describe().

     gem_names and clients are standard ones, and can be found from drm_debugfs.c.

    Please let us know if you need additional details on top of the source level details shared.

    Thanks & Regards,

    Sunita.