Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an option to print out raw counters in gputop-wrapper #175

Open
djdeath opened this issue Feb 22, 2018 · 2 comments
Open

Add an option to print out raw counters in gputop-wrapper #175

djdeath opened this issue Feb 22, 2018 · 2 comments

Comments

@djdeath
Copy link
Collaborator

djdeath commented Feb 22, 2018

This would be useful for debugging purposes.

@zzzunes
Copy link

zzzunes commented Jul 11, 2018

Hello, I would like to try approaching this issue. What do you specifically mean by raw counters? I can kind of see the flow printing the counters of context in gputop-wrapper-main, but I'm not sure how the process is obtaining the metric counters / where to fetch the raw counters. Do you know where in the source I could look to learn more about this? Thank you!

@djdeath
Copy link
Collaborator Author

djdeath commented Jul 17, 2018

Before the counters are printed out on the console, they have to be computed.
There are equations that compute their values using variables describing features of the system as well as "raw counters" meaning the values provided by the hardware.

For example the percentage of busyness of the execution unit : https://github.com/rib/gputop/blob/master/data/oa-sklgt3.xml#L23
Is computed using the following equation (reverse polish notation) : A 7 READ $EuCoresTotalCount UDIV 100 UMUL $GpuCoreClocks FDIV
What this feature is about is printing out the raw counters feeding that equation, in this case it's counter A7 : A 7 READ
Those counters are accumulated here : https://github.com/rib/gputop/blob/master/lib/gputop-oa-counters.h#L63

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants