CI is still unstable whenever we enable more than one engine, and we
have not yet found a better hack than restricting it to using just rcs0.

However, to allow testing to continue on the other engines by
developers, we allow the available set of engines to be overridden on
the command line with just the default set limited to [rcs0].

Signed-off-by: Chris Wilson <ch...@chris-wilson.co.uk>
Cc: Andi Shyti <andi.sh...@intel.com>
Cc: Mika Kuoppala <mika.kuopp...@linux.intel.com>
---
 drivers/gpu/drm/i915/gt/intel_engine_cs.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/drivers/gpu/drm/i915/gt/intel_engine_cs.c 
b/drivers/gpu/drm/i915/gt/intel_engine_cs.c
index 690da64ec256..9c8c7c8af394 100644
--- a/drivers/gpu/drm/i915/gt/intel_engine_cs.c
+++ b/drivers/gpu/drm/i915/gt/intel_engine_cs.c
@@ -406,6 +406,10 @@ static bool engine_available(struct drm_i915_private 
*i915, int id)
        if (!HAS_ENGINE(i915, id))
                return false;
 
+       /* XXX reduced by default for CI stability XXX */
+       if (IS_TIGERLAKE(i915) && i915_modparams.engines == -1u)
+               return id == RCS0;
+
        if (!(i915_modparams.engines & param_bit[id]))
                return false;
 
-- 
2.23.0

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Reply via email to