summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/i915/i915_gem.c
diff options
context:
space:
mode:
authorChris Wilson2013-09-25 12:43:28 +0200
committerDaniel Vetter2013-10-01 07:45:24 +0200
commitb52b89da097896ac265d1f875aeb0bfd92a9dd38 (patch)
tree16cb9ff966426839a8894ce0d974934ff878e7a0 /drivers/gpu/drm/i915/i915_gem.c
parentdrm/i915: Show WT caching in debugfs (diff)
downloadkernel-qcow2-linux-b52b89da097896ac265d1f875aeb0bfd92a9dd38.tar.gz
kernel-qcow2-linux-b52b89da097896ac265d1f875aeb0bfd92a9dd38.tar.xz
kernel-qcow2-linux-b52b89da097896ac265d1f875aeb0bfd92a9dd38.zip
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>
Diffstat (limited to 'drivers/gpu/drm/i915/i915_gem.c')
-rw-r--r--drivers/gpu/drm/i915/i915_gem.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
index 1a0b74d56cd7..3ae925b0045f 100644
--- a/drivers/gpu/drm/i915/i915_gem.c
+++ b/drivers/gpu/drm/i915/i915_gem.c
@@ -2625,6 +2625,7 @@ i915_gem_object_sync(struct drm_i915_gem_object *obj,
if (ret)
return ret;
+ trace_i915_gem_ring_sync_to(from, to, seqno);
ret = to->sync_to(to, from, seqno);
if (!ret)
/* We use last_read_seqno because sync_to()