On Wed, Jun 18, 2014 at 03:50:20PM +0100, Chris Wilson wrote: > On Wed, Jun 18, 2014 at 02:46:49PM +0200, Daniel Vetter wrote: > > Can be useful to figure out imbalances and bugs in the frontbuffer > > tracking. > > > > Signed-off-by: Daniel Vetter <daniel.vetter@xxxxxxxx> > > Reviewed-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> > > I don't think this will be useful for error state. All the failure modes > here I think relate to display coherency, unless you can think of > something else? No, should really only be relevant for display coherency bugs, not unhappy gpus. I think the biggest risk there is that flushing at inopportune times might upset the hardware. But since these operations happen at few times per frame we can't dump a tracing stream of debug noise by default. So nothing to add here until we have dynamic debugging or some other means for more fine-grained debug logging. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
