Announcing radeontop, a tool for viewing the GPU usage

[chithanh]

Your issue and other problems with the Makefile (with suggested fix) have been reported already on github https://github.com/clbr/radeontop/pull/2

[Flynn]

Switching obj and LDFLAGS in the Makefile did the trick.
Senk ju ferrie matsch.

Great to see there is already a fix in the pipeline.

[entropy]

Didn't watch the vid, but in general the accuracy depends on the samples per sec. The default (60) is a low number pulled out of my backside, at least it has no measurable overhead.

But to get more accurate numbers, try "-t 1000" for example.

I completely missed that parameter, thanks.

Indeed, even increasing it slightly from 60 to 70 Hz results in a comparably steady state.
Not sure if this can be generalized, but maybe it's not a good idea to poll registers with 60 Hz while
your 3d app runs v-synched at 60 Hz also. Just an idea, where that "beating" might result from.

[curaga]

0.5.3 tagged, with various build fixes and default ticks upped to 120. Thanks for the feedback!

[curaga]

I have to two radeon graphic cards and one is blacklisted via xen pcihide. It seems that radeontop picks this graphic card. Everything is on 100%.

It would be nice to choose the graphic card.

Are they the same model (pci id) or different models? Currently it just picks the first Radeon GPU it finds, I wonder what would be a good interface that would handle many cards with the same pci id.

[Xaseron]

01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Barts XT [ATI Radeon HD 6800 Series]
09:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV710 [Radeon HD 4550]

I use the second one for displaying my desktop.

[curaga]

OK, perhaps the first number (slot?) is the answer. I'll put it on my todo list.

[not.sure]

Is all of this specific to radeon hardware?
It would be nice to get similar information from nouveau/intel drivers; merge it all into one tool and then we can call it "dritop"...

[Khudsa]

Ohhh! Great Curaga! Thanks!

[whizse]

Is all of this specific to radeon hardware?
It would be nice to get similar information from nouveau/intel drivers; merge it all into one tool and then we can call it "dritop"...

There's already a similar tool for intel, that's the inspiration for this one.