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

Explain how to get process from context id better #182

Open
eero-t opened this issue Apr 27, 2018 · 2 comments
Open

Explain how to get process from context id better #182

eero-t opened this issue Apr 27, 2018 · 2 comments

Comments

@eero-t
Copy link

eero-t commented Apr 27, 2018

Currently gputop-ui lists just context ID, so user doesn't know which process he's actually monitoring. It should list also process name/PID (PID in case there are multiple processes with same name).

User needs debugfs, root and this to see what the contexts actually are:
# grep context /sys/kernel/debug/dri/0/i915_context_status

Related to #179.

@djdeath
Copy link
Collaborator

djdeath commented Apr 27, 2018

If you enable the default tracepoints from the initial window, gputop will use the tracepoint information to infer the process name/id from the context id based on who emitted what.

Eventually we want to have the i915 driver to do that work for us so that information is captured at submission rather after the fact (when the process might have died already).

@eero-t
Copy link
Author

eero-t commented Apr 27, 2018

So it seems. I think GUI should indicate that somehow.

E.g. in "Select contexts" pop up a text saying "select default tracepoints to see process names".

@djdeath djdeath changed the title Context IDs should list also process name Explain how to get process from context id better Apr 27, 2018
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