Quoting Tvrtko Ursulin (2020-11-19 13:18:10) > > On 19/11/2020 12:24, Chris Wilson wrote: > > We plan to expand upon the number of available statuses for when we > > pretty-print the requests along the timelines, and so need a new set of > > flags. We have settled upon: > > > > Unready [U] > > - initial status after being submitted, the request is not > > ready for execution as it is waiting for external fences > > > > Ready [R] > > - all fences the request was waiting on have been signaled, > > and the request is now ready for execution and will be > > in a backend queue > > > > - a ready request may still need to wait on semaphores > > [internal fences] > > > > Ready/virtual [V] > > - same as ready, but queued over multiple backends > > > > You do not like my idea of R/Rv? I think it would be more intuitive, but > anyway patch looks good. Started with Rv, but then thought restricting it to a single character and constant width was more important for the vertical alignment. That may not be that much of an issue in practice. ~o~ -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx