On Fri, Jul 13, 2012 at 02:14:08PM +0100, Chris Wilson wrote: > If we drop the breadcrumb request after a batch due to a signal for > example we aim to fix it up at the next opportunity. In this case we > emit a second batchbuffer with no waits upon the first and so no > opportunity to insert the missing request, so we need to emit the > missing flush for coherency. (Note that that invalidating the render > cache is the same as flushing it, so there should have been no > observable corruption.) > > Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk> Ok, now that I've got some more clue about how this all blows up, I've merged this patch here (with a rather decently pimped commit message). Thanks for digging into this & feeding me the lacking clue. Cheers, Daniel -- Daniel Vetter Mail: daniel at ffwll.ch Mobile: +41 (0)79 365 57 48
