On Mon, Jun 19, 2017 at 2:48 PM, Nicolai Hähnle <[email protected]> wrote: > On 16.06.2017 14:58, Marek Olšák wrote: >> >> From: Marek Olšák <[email protected]> >> >> The kernel sort of does the same thing with fences. > > > The kernel sends an EVENT_WRITE_EOP with various TC flags. Is that > guaranteed to wait for shaders to finish and flush their data? I'm mostly > thinking about synchronizing with CPU reads here.
Yes, EOP events first wait and then they flush caches. > > While reading, I noticed that si_emit_cache_flush has a path where L1 is > invalidated _after_ L2 writeback. What's up with that? Couldn't it happen > that there's data in L1 which is not yet written to L2? Seems odd. I have a vague memory that all stores go to L2 either immediately or at the end of waves, but I'm not sure. Marek _______________________________________________ mesa-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/mesa-dev
