On Sun, Feb 12, 2017 at 12:44:49AM +0000, Chris Wilson wrote: > The signal threads may be running concurrently with the GPU reset. The > completion from the GPU run asynchronous with the reset and two threads > may see different snapshots of the state, and the signaler may mark a > request as complete as we try to reset it. We don't tolerate 2 different > views of the same state and complain if we try to mark a request as > failed if it is already complete. Disable the signal threads during > reset to prevent this conflict (even though the conflict implies that > the state we resetting to is invalid, we have already made our > decision!). > > References: https://bugs.freedesktop.org/show_bug.cgi?id=99671 > Signed-off-by: Chris Wilson <ch...@chris-wilson.co.uk> > Cc: Mika Kuoppala <mika.kuopp...@intel.com> > Cc: Tvrtko Ursulin <tvrtko.ursu...@intel.com>
Also Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=99733 -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
