[Intel-gfx] [PATCH 2/2] drm/i915/trace: Remove engine out of the context sandwich

Chris Wilson chris at chris-wilson.co.uk
Thu May 24 15:33:48 UTC 2018


Quoting Tvrtko Ursulin (2018-05-24 16:04:47)
> From: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
> 
> In the string tracepoint representation we ended up with the engine
> sandwiched between context hardware id and context fence id.
> 
> Move the two pieces of context data together and consolidate for
> redability using the format of ctx=hw_id:fence_context_id.

Grr, bring backs my memory of ctx being the most important!

In order of segregation, I think of it as device+context as being the
outer container (a user isn't meant to escape their context). The
timelines and engines they use are all contained within their context.

But what we call ctx here isn't really context, but timeline; how about
if we switch to the fence=%llx:%d representation we've mostly settled on
for the debug messages?
-Chris


More information about the Intel-gfx mailing list