https://bugs.freedesktop.org/show_bug.cgi?id=103304
--- Comment #2 from Nicolai Hähnle <nhaeh...@gmail.com> ---
Oh wow, now that I've actually looked at the issue in more detail, I'm pretty
amazed that you actually managed to hit this issue! Congratulations! :)
The true analysis is a bit different, I would say. The flush ends up accessing
the texture because it does an automatic re-add of all resources when starting
a new CS. This should not affect the ability of the other thread to do a
texture invalidation (you'd just kill performance by introducing an unnecessary
stall).
The real solution is certainly different. I'm currently looking at other
texture-related races as well, this is just one additional one to take care of.
Thank you for the report!
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
