From: Eric Anholt <eric@anholt.net>
Date: Mon, 26 Oct 2009 16:37:53 +0000 (-0700)
Subject: intel: Don't bother MI_FLUSHing on glFlush in the DRI2 case.
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=6eb6a0e9cbed6ba5543d54e277f7ac11a0612070;p=mesa.git

intel: Don't bother MI_FLUSHing on glFlush in the DRI2 case.

We only need it when drawing to the front buffer, which we never do for
DRI2.  No significant performance difference, but the flush is definitely
gone from the end of every batchbuffer.
---

diff --git a/src/mesa/drivers/dri/intel/intel_context.c b/src/mesa/drivers/dri/intel/intel_context.c
index c3432497cad..a7d94ced9a9 100644
--- a/src/mesa/drivers/dri/intel/intel_context.c
+++ b/src/mesa/drivers/dri/intel/intel_context.c
@@ -484,7 +484,7 @@ intel_flush(GLcontext *ctx, GLboolean needs_mi_flush)
     * lands onscreen in a timely manner, even if the X Server doesn't trigger
     * a flush for us.
     */
-   if (needs_mi_flush)
+   if (!intel->driScreen->dri2.enabled && needs_mi_flush)
       intel_batchbuffer_emit_mi_flush(intel->batch);
 
    if (intel->batch->map != intel->batch->ptr)