From: Chris Wilson Date: Fri, 20 Jul 2012 11:41:07 +0000 (+0100) Subject: drm/i915: Clear the pending_gpu_fenced_access flag at the start of execbuffer X-Git-Tag: v3.7-rc1~118^2~61^2~33 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=016fd0c1aee31902d82c1ac32312f1cc32298b66;p=profile%2Fivi%2Fkernel-adaptation-intel-automotive.git drm/i915: Clear the pending_gpu_fenced_access flag at the start of execbuffer Otherwise once we use the buffer with a BLT command on gen2/3, we will always regard future command submissions as continuing the fenced access. However, now that we flush/invalidate between every batch we can drop this pessimism. Signed-off-by: Chris Wilson Signed-off-by: Daniel Vetter --- diff --git a/drivers/gpu/drm/i915/i915_gem_execbuffer.c b/drivers/gpu/drm/i915/i915_gem_execbuffer.c index 6c81079..55a94c1 100644 --- a/drivers/gpu/drm/i915/i915_gem_execbuffer.c +++ b/drivers/gpu/drm/i915/i915_gem_execbuffer.c @@ -413,6 +413,7 @@ i915_gem_execbuffer_reserve(struct intel_ring_buffer *ring, obj->base.pending_read_domains = 0; obj->base.pending_write_domain = 0; + obj->pending_fenced_gpu_access = false; } list_splice(&ordered_objects, objects);