Comment # 34
on bug 68451
from Alexandre Demers
(In reply to comment #33) > (In reply to comment #27) > > fun observation: > > > > Instead of reverting, setting this at the end of r600_cp_dma_copy_buffer() > > appears to fix it for me: > > rctx->b.flags |= R600_CONTEXT_INV_VERTEX_CACHE; > > > > (R600_CONTEXT_INV_CONST_CACHE will also work) > > > > Well, if we are using CP DMA to update a constant buffer or vertex buffer, > we need to flush the the apprortiate shader read caches. So, if I understand correctly what you mean, before reverting commit 7948ed1250cae78ae1b22dbce4ab23aceacc6159, the problem was that we were not flushing correctly (read "when expected") caches. Am I understanding correctly? Why would adding either rctx->b.flags |= R600_CONTEXT_INV_VERTEX_CACHE or rctx->b.flags |= R600_CONTEXT_INV_CONST_CACHE work in fixing the texture glitch (which are coming from an unknown buffer type for now) if they are not intended for the same buffer type? Also, I'm still interested in benchmarking with and without commit 7948ed1250cae78ae1b22dbce4ab23aceacc6159, so I'll gladly run any suggestion. Would something like Phoronix test suite be of any interest?
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
