<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 14, 2017 at 3:38 PM, Chad Versace <span dir="ltr"><<a href="mailto:chadversary@chromium.org" target="_blank">chadversary@chromium.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Wed 12 Jul 2017, Jason Ekstrand wrote:<br>
> ---<br>
> src/mesa/drivers/dri/i965/<wbr>intel_screen.c | 11 ++++++++++-<br>
> 1 file changed, 10 insertions(+), 1 deletion(-)<br>
<br>
</span><span class="">> + /* We request that the bufmgr zero the buffer for us for two reasons:<br>
> + *<br>
> + * 1) If a buffer gets re-used from the pool, we don't want to leak random<br>
> + * garbage from our process to some other.<br>
> + *<br>
> + * 2) For images with CCS_E, we want to ensure that the CCS starts off in<br>
> + * a valid state. A CCS value of 0 indicates that the given block is<br>
> + * in the pass-through state which is what we want.<br>
> + */<br>
<br>
</span>Bullet #2 should be postponed to a later patch, as the bo here does not<br>
contain an aux surface until later in the series.<br></blockquote><div><br></div><div>I moved it.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
But that's a small nit. This is<br>
Reviewed-by: Chad Versace <<a href="mailto:chadversary@chromium.org">chadversary@chromium.org</a>><br><div class="HOEnZb"><div class="h5"></div></div></blockquote><div><br></div><div>Thanks!<br><br></div><div>--Jason<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
> image->bo = brw_bo_alloc_tiled(screen-><wbr>bufmgr, "image", surf.size,<br>
> isl_tiling_to_i915_tiling(mod_<wbr>info->tiling),<br>
> - surf.row_pitch, 0);<br>
> + surf.row_pitch, BO_ALLOC_ZEROED);<br>
</div></div></blockquote></div><br></div></div>