summaryrefslogtreecommitdiffstats
path: root/Documentation/gpu
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2017-08-09 17:39:30 +0100
committerChris Wilson <chris@chris-wilson.co.uk>2017-08-10 12:18:35 +0100
commit3ec0af7f223bab9503c4ed57d00ed34b137df476 (patch)
treea620ca7fbfc6247b9baefae9ef87c7138398c5f6 /Documentation/gpu
parent912d64123d354dd2e4ced479e1d93e74ea4c99a8 (diff)
downloadlinux-stable-3ec0af7f223bab9503c4ed57d00ed34b137df476.tar.gz
linux-stable-3ec0af7f223bab9503c4ed57d00ed34b137df476.tar.bz2
linux-stable-3ec0af7f223bab9503c4ed57d00ed34b137df476.zip
drm/i915: Supply the engine-id for our mock_engine()
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>
Diffstat (limited to 'Documentation/gpu')
0 files changed, 0 insertions, 0 deletions