On Thu, Dec 10, 2015 at 11:45:54AM +0100, Daniel Vetter wrote: > On Thu, Dec 10, 2015 at 12:19:29PM +0200, Mika Kuoppala wrote: > > Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> writes: > > > > > Following a GPU reset, we may leave the context in a poorly defined > > > state, and reloading from that context will leave the GPU flummoxed. For > > > secondary contexts, this will lead to that context being banned - but > > > currently it is also causing the default context to become banned, > > > leading to turmoil in the shared state. > > > > > > This is a regression from > > > > > > commit 6702cf16e0ba8b0129f5aa1b6609d4e9c70bc13b [v4.1] > > > Author: Ben Widawsky <benjamin.widawsky@xxxxxxxxx> > > > Date: Mon Mar 16 16:00:58 2015 +0000 > > > > > > drm/i915: Initialize all contexts > > > > > > which quietly introduced the removal of the MI_RESTORE_INHIBIT on the > > > default context. > > > > > > v2: Mark the global default context as uninitialized on GPU reset so > > > that the context-local workarounds are reloaded upon re-enabling. > > > > > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> > > > > Reviewed-by: Mika Kuoppala <mika.kuoppala@xxxxxxxxx> > > Queued for -next, thanks for the patch. I guess I dropped this one again, but now merged again since it fixes a suspend/resume regression. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
