Quoting Mika Kuoppala (2017-08-10 12:13:14) > Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> writes: > > > In the initial selftest, we didn't care what the engine->id was, just > > that it could uniquely identify it. Later though, we started tracking in > > the fixed size arrays around the drm_i915_private and so we now require > > it to be appropriate. This becomes an issue when using the standalone > > harness of running all available tests at module load as we quickly > > assign an out-of-bounds index to an engine as repeatedly reallocate the > > mock GEM device (and doesn't show up in igt/drv_selftest as that ran > > each subtest individually). > > > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=102045 > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> > > Reviewed-by: Mika Kuoppala <mika.kuoppala@xxxxxxxxx> Proof-read my bad grammar and pushed, thanks. -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
