[Intel-gfx] [PATCH 1/4] drm/i915/gt: Do not schedule normal requests immediately along virtual
sashal at kernel.org
Tue May 26 00:23:57 UTC 2020
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: 6d06779e8672 ("drm/i915: Load balancing across a virtual engine").
The bot has tested the following trees: v5.6.14, v5.4.42.
v5.6.14: Build OK!
v5.4.42: Failed to apply! Possible dependencies:
0b718ba1e884 ("drm/i915/gtt: Downgrade Cherryview back to aliasing-ppgtt")
0f100b70487a ("drm/i915: Push the use-semaphore marker onto the intel_context")
2e0986a58cc4 ("drm/i915/gem: Cancel contexts when hangchecking is disabled")
4a3174152147 ("drm/i915/gem: Refine occupancy test in kill_context()")
5bf05dc58d65 ("drm/i915/tgl: Register state context definition for Gen12")
7dc56af5260e ("drm/i915/selftests: Verify the LRC register layout between init and HW")
8f8b1171e1a5 ("drm/i915/perf: Wean ourselves off dev_priv")
9cd20ef7803c ("drm/i915/perf: allow holding preemption on filtered ctx")
9f3ccd40acf4 ("drm/i915: Drop GEM context as a direct link from i915_request")
a0e047156cde ("drm/i915/gem: Make context persistence optional")
cdb736fa8b8b ("drm/i915: Use engine relative LRIs on context setup")
eaef5b3c4113 ("drm/i915: Refactor instdone loops on new subslice functions")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
More information about the Intel-gfx