drm/i915: Add a tracepoint for using a semaphore
authorChris Wilson <chris@chris-wilson.co.uk>
Wed, 25 Sep 2013 10:43:28 +0000 (11:43 +0100)
committerDaniel Vetter <daniel.vetter@ffwll.ch>
Tue, 1 Oct 2013 05:45:24 +0000 (07:45 +0200)
commitb52b89da097896ac265d1f875aeb0bfd92a9dd38
tree16cb9ff966426839a8894ce0d974934ff878e7a0
parentf56383cb9fc8d7165bd7d2136b4c4af98c41177c
drm/i915: Add a tracepoint for using a semaphore

So that we can find the callers who introduce a ring stall. A single
ring stall is not too unwelcome, the right issue becomes when they start
to interlock and prevent any concurrent work. That, however, is a little
tricker to detect with a mere tracepoint!

v2: Rebrand it as a ring event, rather than an object event.
v3: Include the seqno in the tracepoint for posterity or something.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
drivers/gpu/drm/i915/i915_gem.c
drivers/gpu/drm/i915/i915_trace.h