[Intel-gfx] [PATCH 0/9] Per client engine busyness

From: Tvrtko Ursulin Another re-spin of the per-client engine busyness series. Highlights from this version: * Make sure i915_gem_context is fully initialized before adding to gem.contexts.list. * A couple checkpatch warnings. Internally we track time spent on engines for each struct intel

[Intel-gfx] [PATCH 0/9] Per client engine busyness

From: Tvrtko Ursulin Another re-spin of the per-client engine busyness series. Highlights from this version: * Small fix for cyclic client id allocation. * Otherwise just a rebase to catch up with drm-tip. Internally we track time spent on engines for each struct intel_context. This can serve

[Intel-gfx] [PATCH 0/9] Per client engine busyness

From: Tvrtko Ursulin Another re-spin of the per-client engine busyness series. Highlights from this version: * One patch got merged in the meantime, otherwise just a rebase. Internally we track time spent on engines for each struct intel_context. This can serve as a building block for several

Re: [Intel-gfx] [PATCH 0/9] Per client engine busyness

On 18/03/2020 11:01, Tvrtko Ursulin wrote: From: Tvrtko Ursulin Another re-spin of the per-client engine busyness series. Highlights from this version: Broken version with one patch missing, apologies for the spam. Regards, Tvrtko * Checkpatch cleanup and bits of review feedback only.

[Intel-gfx] [PATCH 0/9] Per client engine busyness

From: Tvrtko Ursulin Another re-spin of the per-client engine busyness series. Highlights from this version: * Checkpatch cleanup and bits of review feedback only. Internally we track time spent on engines for each struct intel_context. This can serve as a building block for several features f