From: Andi Shyti <andi.shyti@linux.intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Chris Wilson <chris.p.wilson@linux.intel.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Chris Wilson <chris@chris-wilson.co.uk>,
dri-devel@lists.freedesktop.org,
Andrzej Hajda <andrzej.hajda@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915/gt: Hold a wakeref for the active VM
Date: Tue, 4 Apr 2023 18:00:10 +0200 [thread overview]
Message-ID: <ZCxJitP+XtC2/run@ashyti-mobl2.lan> (raw)
In-Reply-To: <f193eb7f-19f9-b9a8-7edf-438dafb74da4@linux.intel.com>
Hi Tvrtko,
> > > diff --git a/drivers/gpu/drm/i915/gt/intel_context.h b/drivers/gpu/drm/i915/gt/intel_context.h
> > > index 0a8d553da3f439..48f888c3da083b 100644
> > > --- a/drivers/gpu/drm/i915/gt/intel_context.h
> > > +++ b/drivers/gpu/drm/i915/gt/intel_context.h
> > > @@ -14,6 +14,7 @@
> > > #include "i915_drv.h"
> > > #include "intel_context_types.h"
> > > #include "intel_engine_types.h"
> > > +#include "intel_gt_pm.h"
> > > #include "intel_ring_types.h"
> > > #include "intel_timeline_types.h"
> > > #include "i915_trace.h"
> > > @@ -207,8 +208,11 @@ void intel_context_exit_engine(struct intel_context *ce);
> > > static inline void intel_context_enter(struct intel_context *ce)
> > > {
> > > lockdep_assert_held(&ce->timeline->mutex);
> > > - if (!ce->active_count++)
> > > - ce->ops->enter(ce);
> > > + if (ce->active_count++)
> > > + return;
> > > +
> > > + ce->ops->enter(ce);
> > > + intel_gt_pm_get(ce->vm->gt);
> > > }
> > > static inline void intel_context_mark_active(struct intel_context *ce)
> > > @@ -222,8 +226,11 @@ static inline void intel_context_exit(struct intel_context *ce)
> > > {
> > > lockdep_assert_held(&ce->timeline->mutex);
> > > GEM_BUG_ON(!ce->active_count);
> > > - if (!--ce->active_count)
> > > - ce->ops->exit(ce);
> > > + if (--ce->active_count)
> > > + return;
> > > +
> > > + intel_gt_pm_put_async(ce->vm->gt);
> > > + ce->ops->exit(ce);
> >
> > shouldn't these two be swapped?
maybe I wasn't clear here... shouldn't it be
ce->ops->exit(ce);
intel_gt_pm_put_async(ce->vm->gt);
Don't we need to hold the pm until exiting?
> > > }
> > > static inline struct intel_context *intel_context_get(struct intel_context *ce)
> > > diff --git a/drivers/gpu/drm/i915/gt/intel_engine_pm.c b/drivers/gpu/drm/i915/gt/intel_engine_pm.c
> > > index e971b153fda976..ee531a5c142c77 100644
> > > --- a/drivers/gpu/drm/i915/gt/intel_engine_pm.c
> > > +++ b/drivers/gpu/drm/i915/gt/intel_engine_pm.c
> > > @@ -114,6 +114,15 @@ __queue_and_release_pm(struct i915_request *rq,
> > > ENGINE_TRACE(engine, "parking\n");
> > > + /*
> > > + * Open coded one half of intel_context_enter, which we have to omit
> > > + * here (see the large comment below) and because the other part must
> > > + * not be called due constructing directly with __i915_request_create
> > > + * which increments active count via intel_context_mark_active.
> > > + */
> > > + GEM_BUG_ON(rq->context->active_count != 1);
> > > + __intel_gt_pm_get(engine->gt);
> >
> > where is it's brother "put"?
>
> It's in request retire via intel_context_exit. Ie. request construction is
> special here, while retirement is standard.
Thank you!
Andi
next prev parent reply other threads:[~2023-04-04 16:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 14:16 [Intel-gfx] [PATCH v2] drm/i915/gt: Hold a wakeref for the active VM Andrzej Hajda
2023-03-31 14:51 ` Tvrtko Ursulin
2023-03-31 17:23 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gt: Hold a wakeref for the active VM (rev2) Patchwork
2023-03-31 17:33 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-04-01 18:02 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-04-03 8:58 ` Andrzej Hajda
2023-04-04 15:39 ` [Intel-gfx] [PATCH v2] drm/i915/gt: Hold a wakeref for the active VM Andi Shyti
2023-04-04 15:57 ` Tvrtko Ursulin
2023-04-04 16:00 ` Andi Shyti [this message]
2023-04-04 16:22 ` Tvrtko Ursulin
2023-04-04 16:29 ` Andi Shyti
2023-04-05 14:16 ` Andrzej Hajda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZCxJitP+XtC2/run@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=chris.p.wilson@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox