<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Jan 23, 2017 at 7:47 AM, Pohjolainen, Topi <span dir="ltr"><<a href="mailto:topi.pohjolainen@gmail.com" target="_blank">topi.pohjolainen@gmail.com</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 Fri, Jan 20, 2017 at 08:40:50AM -0800, Jason Ekstrand wrote:<br>
> On Thu, Jan 19, 2017 at 11:48 PM, Pohjolainen, Topi<br>
</span><span class="">> <[1]<a href="mailto:topi.pohjolainen@gmail.com">topi.pohjolainen@gmail.com</a><wbr>> wrote:<br>
><br>
> On Thu, Jan 19, 2017 at 01:39:49PM -0800, Jason Ekstrand wrote:<br>
> > On Thu, Jan 19, 2017 at 12:40 PM, Francisco Jerez<br>
</span>> > <[1][2]<a href="mailto:currojerez@riseup.net">currojerez@riseup.net</a>> wrote:<br>
> ><br>
> > "Pohjolainen, Topi" <[2][3]<a href="mailto:topi.pohjolainen@gmail.com">topi.pohjolainen@gmail.<wbr>com</a>><br>
<span class="">> writes:<br>
> > > On Thu, Jan 19, 2017 at 12:10:02PM -0800, Francisco Jerez<br>
> wrote:<br>
</span>> > >> Topi Pohjolainen <[3][4]<a href="mailto:topi.pohjolainen@gmail.com">topi.pohjolainen@gmail.<wbr>com</a>><br>
> writes:<br>
> > >><br>
> > >> > CC: Francisco Jerez <[4][5]<a href="mailto:currojerez@riseup.net">currojerez@riseup.net</a>><br>
> > >> > CC: Kenneth Graunke <[5][6]<a href="mailto:kenneth@whitecape.org">kenneth@whitecape.org</a>><br>
> > >> > CC: Jason Ekstrand <[6][7]<a href="mailto:jason@jlekstrand.net">jason@jlekstrand.net</a>><br>
> > >> > Signed-off-by: Topi Pohjolainen<br>
> <[7][8]<a href="mailto:topi.pohjolainen@intel.com">topi.pohjolainen@intel.<wbr>com</a>><br>
<div><div class="h5">><br>
> > >> > ---<br>
> > >> > src/mesa/drivers/dri/i965/<wbr>genX_blorp_exec.c | 3 +++<br>
> > >> > 1 file changed, 3 insertions(+)<br>
> > >> ><br>
> > >> > diff --git a/src/mesa/drivers/dri/i965/<wbr>genX_blorp_exec.c<br>
> > b/src/mesa/drivers/dri/i965/<wbr>genX_blorp_exec.c<br>
> > >> > index 647a362..594bd5a 100644<br>
> > >> > --- a/src/mesa/drivers/dri/i965/<wbr>genX_blorp_exec.c<br>
> > >> > +++ b/src/mesa/drivers/dri/i965/<wbr>genX_blorp_exec.c<br>
> > >> > @@ -261,4 +261,7 @@ retry:<br>
> > >> ><br>
> > >> > if (params->dst.enabled)<br>
> > >> > brw_render_cache_set_add_bo(<wbr>brw,<br>
> > params->dst.addr.buffer);<br>
> > >> > +<br>
> > >> > + if (params->depth.enabled)<br>
> > >> > + brw_render_cache_set_add_bo(<wbr>brw,<br>
> > params->depth.addr.buffer);<br>
> > >><br>
> > >> What about the stencil buffer? Stencil texturing is likely<br>
> to be<br>
> > >> unhappy unless you mark it as pending flush as well...<br>
> > ><br>
> > > As far as I know i965 only clears depth and color using blorp,<br>
> > stencil gets<br>
> > > cleared using meta. Blits in turn have it as destination.<br>
> > ><br>
> > That doesn't sound like a safe assumption to rely on looking<br>
> forward<br>
> > if<br>
> > the blorp api already exposes support for stencil writes --<br>
> Tracking<br>
> > down the ultimate cause of a memory coherency bugs can be really<br>
> > hard,<br>
> > why make our future lives more intentionally difficult by<br>
> > introducing<br>
> > buggy corner cases like this? The extra check is not going to<br>
> hurt<br>
> > performance or cause any other harmful side effects unless<br>
> stencil<br>
> > writes are used...<br>
> ><br>
> > Agreed. Let's stick it in there for stencil too. I've got<br>
> patches to<br>
> > switch i965 over to blorp for depth/stencil blits. I never landed<br>
> them<br>
> > because of what was most likely flushing bugs. I'm hoping that<br>
> you've<br>
> > fixed those and I'll revive the patches.<br>
> > Also, please make sure these fixes hit stable.<br>
><br>
> This sits on top the four earlier patches. Rebasing this alone<br>
> against stable<br>
> requires manual work but can be done. How do you want to handle<br>
> that?<br>
><br>
> Ken, Curro, and I had a little chat about this in the office. I think<br>
> the conclusion we came to was the following:<br>
> 1) The patches to add flushing around HiZ ops and fast clear ops should<br>
> get back-ported all the way to 13.0. They fix potentially serious bugs<br>
> that could cause problems.<br>
<br>
</div></div>You mean thse two? They apply on 13.0 without any tweaks:<br>
<br>
i965/gen6: Issue direct depth stall and flush after depth clear<br>
i965: Make depth clear flushing more explicit<span class=""><br></span></blockquote><div><br></div><div>Yes, those.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
> 2) The patches that switch us over to the render cache should get<br>
> backported to 17.0. They aren't so much a bug fix as an enhancement<br>
> but keeping 17.0 consistent with future will help in backporting other<br>
> fixes. For the record, this was me and Ken; Curro preferred to not<br>
> backport these.<br>
<br>
</span>And all the four apply clean on 17.0.<br></blockquote><div><br></div><div>Cool<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
><br>
> References<br>
><br>
> 1. mailto:<a href="mailto:topi.pohjolainen@gmail.com">topi.pohjolainen@gmail.<wbr>com</a><br>
> 2. mailto:<a href="mailto:currojerez@riseup.net">currojerez@riseup.net</a><br>
> 3. mailto:<a href="mailto:topi.pohjolainen@gmail.com">topi.pohjolainen@gmail.<wbr>com</a><br>
> 4. mailto:<a href="mailto:topi.pohjolainen@gmail.com">topi.pohjolainen@gmail.<wbr>com</a><br>
> 5. mailto:<a href="mailto:currojerez@riseup.net">currojerez@riseup.net</a><br>
> 6. mailto:<a href="mailto:kenneth@whitecape.org">kenneth@whitecape.org</a><br>
> 7. mailto:<a href="mailto:jason@jlekstrand.net">jason@jlekstrand.net</a><br>
> 8. mailto:<a href="mailto:topi.pohjolainen@intel.com">topi.pohjolainen@intel.<wbr>com</a><br>
</blockquote></div><br></div></div>