forked from Minki/linux
3ec0af7f22
In the original selftest, we didn't care what the engine->id was, just that it could uniquely identify it. Later though, we started tracking the mock engines in the fixed size arrays around the drm_i915_private and so we now require their indices to be correct. This becomes an issue when using the standalone harness which runs all available tests at module load, and so we quickly assign an out-of-bounds index to an engine as we reallocate the mock GEM device between tests. It doesn't show up in igt/drv_selftest as that runs each subtest individually. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=102045 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Link: https://patchwork.freedesktop.org/patch/msgid/20170809163930.26470-1-chris@chris-wilson.co.uk Reviewed-by: Mika Kuoppala <mika.kuoppala@intel.com> |
||
|---|---|---|
| .. | ||
| huge_gem_object.c | ||
| huge_gem_object.h | ||
| i915_gem_coherency.c | ||
| i915_gem_context.c | ||
| i915_gem_dmabuf.c | ||
| i915_gem_evict.c | ||
| i915_gem_gtt.c | ||
| i915_gem_object.c | ||
| i915_gem_request.c | ||
| i915_gem_timeline.c | ||
| i915_live_selftests.h | ||
| i915_mock_selftests.h | ||
| i915_random.c | ||
| i915_random.h | ||
| i915_selftest.c | ||
| i915_sw_fence.c | ||
| i915_syncmap.c | ||
| i915_vma.c | ||
| intel_breadcrumbs.c | ||
| intel_hangcheck.c | ||
| intel_uncore.c | ||
| mock_context.c | ||
| mock_context.h | ||
| mock_dmabuf.c | ||
| mock_dmabuf.h | ||
| mock_drm.c | ||
| mock_drm.h | ||
| mock_engine.c | ||
| mock_engine.h | ||
| mock_gem_device.c | ||
| mock_gem_device.h | ||
| mock_gem_object.h | ||
| mock_gtt.c | ||
| mock_gtt.h | ||
| mock_request.c | ||
| mock_request.h | ||
| mock_timeline.c | ||
| mock_timeline.h | ||
| mock_uncore.c | ||
| mock_uncore.h | ||
| scatterlist.c | ||