On Tue, Nov 26, 2013 at 11:23:50PM -0800, Ben Widawsky wrote: > On Tue, Nov 26, 2013 at 11:23:15AM +0000, Chris Wilson wrote: > > As the execbuffer dispatch grows ever more complex and involves multiple > > stages of moving objects into the aperture, we need to take greater care > > that we do not evict our execbuffer objects prior to dispatch. This is > > relatively simple as we can just keep the objects pinned for not just > > the relocation but until we are finished. > > > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> > > Cc: Ben Widawsky <benjamin.widawsky@xxxxxxxxx> > > Cc: Daniel Vetter <daniel@xxxxxxxx> > > Cc: stable@xxxxxxxxxxxxxxx > > To be honest, I don't quite see the actual issue, but the problem > description, and solution make sense to me. I've also been running with > the patch quite a bit on HSW. > > Acked-by: Ben Widawsky <ben@xxxxxxxxxxxx> > Tested-by: Ben Widawsky <ben@xxxxxxxxxxxx> Picked up for -fixes, thanks for the patch. -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
