Quoting Tvrtko Ursulin (2020-11-17 13:06:22)
>
> On 17/11/2020 11:30, Chris Wilson wrote:
> > From: Tvrtko Ursulin <tvrtko.ursulin@xxxxxxxxx>
> >
> > Include the signalers each request in the timeline is waiting on, as a
> > means to try and identify the cause of a stall. This can be quite
> > verbose, even as for now we only show each request in the timeline and
> > its immediate antecedents.
> >
> > This generates output like:
> >
> > Timeline 886: { count 1, ready: 0, inflight: 0, seqno: { current: 664, last: 666 }, engine: rcs0 }
>
> Applies to earlier patch:
>
> I am still tempted to suggest replacing "current: %d, last: %d" with
> "seqno: %d/%d" for compactness and which is still completely intuitive
> to me.
>
> And maybe instead of "engine: %s" just append the engine name direct as tag.
>
> But up to you.
I trying to indoctrinate myself into using yaml for info dumps. With the
end goal being all the major files being yaml
> > U 886:29a- prio=0 @ 134ms: gem_exec_parall<4621>
> > - U bc1:27a- prio=0 @ 134ms: gem_exec_parall[4917]
And this admittedly is not yaml. A long way to go before it is second
nature.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
