[Intel-gfx] [PATCH] drm/i915: Supply the engine-id for our mock_engine()
Chris Wilson
chris at chris-wilson.co.uk
Thu Aug 10 11:21:29 UTC 2017
Quoting Mika Kuoppala (2017-08-10 12:13:14)
> Chris Wilson <chris at chris-wilson.co.uk> 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 at chris-wilson.co.uk>
>
> Reviewed-by: Mika Kuoppala <mika.kuoppala at intel.com>
Proof-read my bad grammar and pushed, thanks.
-Chris
More information about the Intel-gfx
mailing list