From 6404fcb266753a2fd8243210b3553bfe846ce104 Mon Sep 17 00:00:00 2001 From: Eric Anholt Date: Tue, 27 Aug 2013 12:30:39 -0700 Subject: i965: Directly call intel_batchbuffer_flush() after i915 split. intel_flush() now did nothing except call through (and intel_batchbuffer_flush() does the no-op check, too!) Reviewed-by: Kenneth Graunke Reviewed-by: Paul Berry --- src/mesa/drivers/dri/i965/intel_buffer_objects.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/mesa/drivers/dri/i965/intel_buffer_objects.c') diff --git a/src/mesa/drivers/dri/i965/intel_buffer_objects.c b/src/mesa/drivers/dri/i965/intel_buffer_objects.c index 663cc29..21d3727 100644 --- a/src/mesa/drivers/dri/i965/intel_buffer_objects.c +++ b/src/mesa/drivers/dri/i965/intel_buffer_objects.c @@ -291,7 +291,7 @@ intel_bufferobj_map_range(struct gl_context * ctx, } else { perf_debug("Stalling on the GPU for mapping a busy buffer " "object\n"); - intel_flush(ctx); + intel_batchbuffer_flush(brw); } } else if (drm_intel_bo_busy(intel_obj->buffer) && (access & GL_MAP_INVALIDATE_BUFFER_BIT)) { -- cgit v1.1