Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> writes: > Since we may be attempting to reset an active engine, we try to freeze > it in place before resetting -- to be on the safe side. We can go one > step further if we are using the CS flow semaphore to prevent the > context switching into the next. > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> Reviewed-by: Mika Kuoppala <mika.kuoppala@xxxxxxxxxxxxxxx> > --- > drivers/gpu/drm/i915/gt/intel_lrc.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c > index 9fff4e02cee6..9e18c0896a83 100644 > --- a/drivers/gpu/drm/i915/gt/intel_lrc.c > +++ b/drivers/gpu/drm/i915/gt/intel_lrc.c > @@ -3669,6 +3669,7 @@ static void execlists_reset_prepare(struct intel_engine_cs *engine) > * > * FIXME: Wa for more modern gens needs to be validated > */ > + ring_set_paused(engine, 1); > intel_engine_stop_cs(engine); > } > > -- > 2.20.1 _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
