Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> writes: > The engine->kernel_context is a special case for request emission. Since > it is used as the barrier within the engine's wakeref, we must acquire the > wakeref before submitting a request to the kernel_context. I am a bit surprised that the kernel ctx is used in this capacity... > > Reported-by: Lionel Landwerlin <lionel.g.landwerlin@xxxxxxxxx> > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> > Cc: Lionel Landwerlin <lionel.g.landwerlin@xxxxxxxxx> Reviewed-by: Mika Kuoppala <mika.kuoppala@xxxxxxxxxxxxxxx> > --- > drivers/gpu/drm/i915/i915_perf.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i915_perf.c > index 0838a12e2dc5..2334c45f1d08 100644 > --- a/drivers/gpu/drm/i915/i915_perf.c > +++ b/drivers/gpu/drm/i915/i915_perf.c > @@ -2196,7 +2196,9 @@ static int gen8_modify_self(struct intel_context *ce, > struct i915_request *rq; > int err; > > + intel_engine_pm_get(ce->engine); > rq = i915_request_create(ce); > + intel_engine_pm_put(ce->engine); > if (IS_ERR(rq)) > return PTR_ERR(rq); > > -- > 2.25.1 > > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@xxxxxxxxxxxxxxxxxxxxx > https://lists.freedesktop.org/mailman/listinfo/intel-gfx _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
