It's useful to know whether a clear is fast (MCS-based), using the
SIMD16 repdata message, or slow.

Signed-off-by: Kenneth Graunke <kenn...@whitecape.org>
Cc: Dylan Baker <baker.dyla...@gmail.com>
Cc: Keith Packard <kei...@keithp.com>
Cc: Eric Anholt <e...@anholt.net>
---
 src/mesa/drivers/dri/i965/brw_blorp_clear.cpp | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/src/mesa/drivers/dri/i965/brw_blorp_clear.cpp 
b/src/mesa/drivers/dri/i965/brw_blorp_clear.cpp
index 7e19c2c..d353f23 100644
--- a/src/mesa/drivers/dri/i965/brw_blorp_clear.cpp
+++ b/src/mesa/drivers/dri/i965/brw_blorp_clear.cpp
@@ -56,7 +56,6 @@ public:
    virtual uint32_t get_wm_prog(struct brw_context *brw,
                                 brw_blorp_prog_data **prog_data) const;
 
-protected:
    brw_blorp_const_color_prog_key wm_prog_key;
 };
 
@@ -545,7 +544,15 @@ do_single_blorp_clear(struct brw_context *brw, struct 
gl_framebuffer *fb,
       }
    }
 
-   DBG("%s to mt %p level %d layer %d\n", __FUNCTION__,
+   const char *clear_type;
+   if (is_fast_clear)
+      clear_type = "fast";
+   else if (params.wm_prog_key.use_simd16_replicated_data)
+      clear_type = "replicated";
+   else
+      clear_type = "slow";
+
+   DBG("%s (%s) to mt %p level %d layer %d\n", __FUNCTION__, clear_type,
        irb->mt, irb->mt_level, irb->mt_layer);
 
    brw_blorp_exec(brw, &params);
-- 
1.9.0

_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Reply via email to