On Wed, Jul 01, 2015 at 05:15:26PM -0300, Paulo Zanoni wrote: > From: Paulo Zanoni <paulo.r.zanoni@xxxxxxxxx> > > Everything is covered either by fbc.lock or mm.stolen_lock, and > intel_fbc.c is already responsible for grabbing the appropriate locks > when it needs them. > > Signed-off-by: Paulo Zanoni <paulo.r.zanoni@xxxxxxxxx> 5-7 Reviewed-by: Chris wilson <chris@xxxxxxxxxxxxxxxxxx> They all look to be safely guarded by a specific mutex now. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
