i965/miptree_map_blit: Don't do the initial copy if INVALIDATE_RANGE is set
authorJason Ekstrand <jason.ekstrand@intel.com>
Tue, 13 Jan 2015 01:10:22 +0000 (17:10 -0800)
committerJason Ekstrand <jason.ekstrand@intel.com>
Wed, 14 Jan 2015 06:06:51 +0000 (22:06 -0800)
commitae417957e04f5f52ac1a15f27c153bc2b426d7dd
treee407775217a7fc18f19b9542440e38bee77bbe2b
parentf52fe39d311f3b1988edaeb4765279bbe337b1b7
i965/miptree_map_blit: Don't do the initial copy if INVALIDATE_RANGE is set

Before we were always coping from the buffer being mapped into the
temporary buffer.  However, if INVALIDATE_RANGE is set, then we know that
the data is going to be junk after we unmap so there's no point in doing
the blit.  This is important because doing the blit will cause a stall 3
lines later when we map the buffer.

Signed-off-by: Jason Ekstrand <jason.ekstrand@intel.com>
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
src/mesa/drivers/dri/i965/intel_mipmap_tree.c