From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Chris Wilson <chris.p.wilson@linux.intel.com>,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [PATCH v2] drm/i915/gt: Hold a wakeref for the active VM
Date: Tue, 4 Apr 2023 17:22:39 +0100 [thread overview]
Message-ID: <74add824-76b6-96eb-b4b2-67d908474c8b@linux.intel.com> (raw)
In-Reply-To: <ZCxJitP+XtC2/run@ashyti-mobl2.lan>
On 04/04/2023 17:00, Andi Shyti wrote:
> 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
I missed this one.
> ce->ops->exit(ce);
> intel_gt_pm_put_async(ce->vm->gt);
>
> Don't we need to hold the pm until exiting?
I think it doesn't matter. The problematic edge case this is fixing is
when ce->engine->gt is different from ce->vm->gt but at this point if it
is safe to release one it must be safe to release the other too.
Regards,
Tvrtko
>
>>>> }
>>>> 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:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 14:16 [PATCH v2] drm/i915/gt: Hold a wakeref for the active VM Andrzej Hajda
2023-03-31 14:51 ` Tvrtko Ursulin
2023-04-04 15:39 ` Andi Shyti
2023-04-04 15:57 ` Tvrtko Ursulin
2023-04-04 16:00 ` Andi Shyti
2023-04-04 16:22 ` Tvrtko Ursulin [this message]
2023-04-04 16:29 ` Andi Shyti
2023-04-05 14:16 ` [Intel-gfx] " 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=74add824-76b6-96eb-b4b2-67d908474c8b@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=airlied@gmail.com \
--cc=andi.shyti@linux.intel.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=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@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