[Intel-gfx] [RFC 00/12] Per client engine busyness

2020-03-11 Thread Tvrtko Ursulin
From: Tvrtko Ursulin Another re-spin of the per-client engine busyness series. Highlights from this version: * Last two patches contain a hybrid method of tracking context runtime. PPHWSP tracked one is used as a baseline and then on top i915 tracks the start time of when context was

Re: [Intel-gfx] [RFC 00/12] Per client engine busyness

2020-03-09 Thread Tvrtko Ursulin
On 09/03/2020 22:02, Chris Wilson wrote: Quoting Tvrtko Ursulin (2020-03-09 18:31:17) From: Tvrtko Ursulin Another re-spin of the per-client engine busyness series. Highlights from this version: * Different way of tracking runtime of exited/unreachable context. This time round I

Re: [Intel-gfx] [RFC 00/12] Per client engine busyness

2020-03-09 Thread Chris Wilson
Quoting Tvrtko Ursulin (2020-03-09 18:31:17) > From: Tvrtko Ursulin > > Another re-spin of the per-client engine busyness series. Highlights from this > version: > > * Different way of tracking runtime of exited/unreachable context. This time >round I accumulate those per context/client

[Intel-gfx] [RFC 00/12] Per client engine busyness

2020-03-09 Thread Tvrtko Ursulin
From: Tvrtko Ursulin Another re-spin of the per-client engine busyness series. Highlights from this version: * Different way of tracking runtime of exited/unreachable context. This time round I accumulate those per context/client and engine class, but active contexts are kept in a list