Quoting Tvrtko Ursulin (2019-06-27 13:25:52) > From: Tvrtko Ursulin <tvrtko.ursulin@xxxxxxxxx> > > If request is to verify all engines work, use the new engine discovery API > so we can actually test all. > > There is a sporadic and mysterious, possibly memory corruption issue > surronding this area so lets see if this changes the pattern. While I do not think the purely on-stack parameters here are subject to memory corruption, nor should the validation path for the execbuf parameters be affected by suspend, if this makes the problem go away, I can be blissfully ignorant as to what was the actual cause. > It is easy to do in this function due it re-opening the driver and > throwing it away. So there are no concerns that the modified default > context can affect any other test. > > Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@xxxxxxxxx> > References: https://bugzilla.freedesktop.org/show_bug.cgi?id=110667 Reviewed-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
