[Intel-gfx] [PATCH 02/10] drm/i915: Add missing trace point to LRC execbuff code path
John.C.Harrison at Intel.com
John.C.Harrison at Intel.com
Tue Dec 9 04:59:05 PST 2014
From: John Harrison <John.C.Harrison at Intel.com>
There is a trace point in the legacy execbuffer execution path that is missing
from the execlist path. Trace points are extremely useful for debugging and are
used by various automated validation tests. Hence, this patch adds the missing
trace point back in.
Change-Id: I8bc80a892e5f7effbe3a0883a58a828d59c10c07
For: VIZ-1587
Signed-off-by: John Harrison <John.C.Harrison at Intel.com>
---
drivers/gpu/drm/i915/intel_lrc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/i915/intel_lrc.c b/drivers/gpu/drm/i915/intel_lrc.c
index b8baf11..82a47e3 100644
--- a/drivers/gpu/drm/i915/intel_lrc.c
+++ b/drivers/gpu/drm/i915/intel_lrc.c
@@ -736,6 +736,8 @@ int intel_execlists_submission(struct drm_device *dev, struct drm_file *file,
if (ret)
return ret;
+ trace_i915_gem_ring_dispatch(intel_ring_get_request(ring), dispatch_flags);
+
i915_gem_execbuffer_move_to_active(vmas, ring);
i915_gem_execbuffer_retire_commands(dev, file, ring, batch_obj);
--
1.7.9.5
More information about the Intel-gfx
mailing list