On Wed, Jun 18, 2014 at 01:59:15PM +0200, Daniel Vetter wrote: > Chris and I also had some discussions about mark_busy and whether it > is appropriate to call from flush. But mark busy is a state which > should be derived from the 3 events (invalidate, flush, flip) we now > have by the users, like psr does by tracking relevant information in > psr.busy_frontbuffer_bits. DRRS (the only real use of mark_busy for > frontbuffer) needs to have similar logic. With that the overall > mark_busy in the core could be removed. Just as a reminder, Daniel has an addendum to put more of what we discussed into practice. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
