The kworker threads are used for flip handling and other non-userspace
driver tasks. They are non-blocking and so do not impact upon how
userspace performs, but they do obscure that information in the
overview.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
This required me to contract the per-process information considerably,
hopefully readability is not sacrificed too much.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
For seqno completion, the events are too coarse i.e. one event may
signal the completion of a few seqno. We will need to sort the events to
properly compute the busy times.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Since the events may be processed out of order (due to per-cpu
ringbuffers) we need to be careful to associated wait pairs in order to
compute the correct elapsed time.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
We can now record when a pageflip occurs by listening for the flip
tracepoint. Merely proof of principle at this point.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
