From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/i915: Mark concurrent submissions with a weak-dependency
Date: Thu, 7 May 2020 15:53:08 +0100 [thread overview]
Message-ID: <f5d72c82-7a9e-3142-f297-b2231f2e9b9f@linux.intel.com> (raw)
In-Reply-To: <20200507082124.1673-1-chris@chris-wilson.co.uk>
On 07/05/2020 09:21, Chris Wilson wrote:
> We recorded the dependencies for WAIT_FOR_SUBMIT in order that we could
> correctly perform priority inheritance from the parallel branches to the
> common trunk. However, for the purpose of timeslicing and reset
> handling, the dependency is weak -- as we the pair of requests are
> allowed to run in parallel and not in strict succession. So for example
> we do need to suspend one if the other hangs.
>
> The real significance though is that this allows us to rearrange
> groups of WAIT_FOR_SUBMIT linked requests along the single engine, and
> so can resolve user level inter-batch scheduling dependencies from user
> semaphores.
>
> Fixes: c81471f5e95c ("drm/i915: Copy across scheduler behaviour flags across submit fences")
> Testcase: igt/gem_exec_fence/submit
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: <stable@vger.kernel.org> # v5.6+
> ---
> drivers/gpu/drm/i915/gt/intel_lrc.c | 9 +++++++++
> drivers/gpu/drm/i915/i915_request.c | 8 ++++++--
> drivers/gpu/drm/i915/i915_scheduler.c | 6 +++---
> drivers/gpu/drm/i915/i915_scheduler.h | 3 ++-
> drivers/gpu/drm/i915/i915_scheduler_types.h | 1 +
> 5 files changed, 21 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c
> index dc3f2ee7136d..10109f661bcb 100644
> --- a/drivers/gpu/drm/i915/gt/intel_lrc.c
> +++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
> @@ -1880,6 +1880,9 @@ static void defer_request(struct i915_request *rq, struct list_head * const pl)
> struct i915_request *w =
> container_of(p->waiter, typeof(*w), sched);
>
> + if (p->flags & I915_DEPENDENCY_WEAK)
> + continue;
> +
I did not quite get it - submit fence dependency would mean different
engines, so the below check (w->engine != rq->engine) would effectively
have the same effect. What am I missing?
Regards,
Tvrtko
> /* Leave semaphores spinning on the other engines */
> if (w->engine != rq->engine)
> continue;
> @@ -2726,6 +2729,9 @@ static void __execlists_hold(struct i915_request *rq)
> struct i915_request *w =
> container_of(p->waiter, typeof(*w), sched);
>
> + if (p->flags & I915_DEPENDENCY_WEAK)
> + continue;
> +
> /* Leave semaphores spinning on the other engines */
> if (w->engine != rq->engine)
> continue;
> @@ -2850,6 +2856,9 @@ static void __execlists_unhold(struct i915_request *rq)
> struct i915_request *w =
> container_of(p->waiter, typeof(*w), sched);
>
> + if (p->flags & I915_DEPENDENCY_WEAK)
> + continue;
> +
> /* Propagate any change in error status */
> if (rq->fence.error)
> i915_request_set_error_once(w, rq->fence.error);
> diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c
> index 4d18f808fda2..3c38d61c90f8 100644
> --- a/drivers/gpu/drm/i915/i915_request.c
> +++ b/drivers/gpu/drm/i915/i915_request.c
> @@ -1040,7 +1040,9 @@ i915_request_await_request(struct i915_request *to, struct i915_request *from)
> }
>
> if (to->engine->schedule) {
> - ret = i915_sched_node_add_dependency(&to->sched, &from->sched);
> + ret = i915_sched_node_add_dependency(&to->sched,
> + &from->sched,
> + I915_DEPENDENCY_EXTERNAL);
> if (ret < 0)
> return ret;
> }
> @@ -1202,7 +1204,9 @@ __i915_request_await_execution(struct i915_request *to,
>
> /* Couple the dependency tree for PI on this exposed to->fence */
> if (to->engine->schedule) {
> - err = i915_sched_node_add_dependency(&to->sched, &from->sched);
> + err = i915_sched_node_add_dependency(&to->sched,
> + &from->sched,
> + I915_DEPENDENCY_WEAK);
> if (err < 0)
> return err;
> }
> diff --git a/drivers/gpu/drm/i915/i915_scheduler.c b/drivers/gpu/drm/i915/i915_scheduler.c
> index 37cfcf5b321b..6e2d4190099f 100644
> --- a/drivers/gpu/drm/i915/i915_scheduler.c
> +++ b/drivers/gpu/drm/i915/i915_scheduler.c
> @@ -462,7 +462,8 @@ bool __i915_sched_node_add_dependency(struct i915_sched_node *node,
> }
>
> int i915_sched_node_add_dependency(struct i915_sched_node *node,
> - struct i915_sched_node *signal)
> + struct i915_sched_node *signal,
> + unsigned long flags)
> {
> struct i915_dependency *dep;
>
> @@ -473,8 +474,7 @@ int i915_sched_node_add_dependency(struct i915_sched_node *node,
> local_bh_disable();
>
> if (!__i915_sched_node_add_dependency(node, signal, dep,
> - I915_DEPENDENCY_EXTERNAL |
> - I915_DEPENDENCY_ALLOC))
> + flags | I915_DEPENDENCY_ALLOC))
> i915_dependency_free(dep);
>
> local_bh_enable(); /* kick submission tasklet */
> diff --git a/drivers/gpu/drm/i915/i915_scheduler.h b/drivers/gpu/drm/i915/i915_scheduler.h
> index d1dc4efef77b..6f0bf00fc569 100644
> --- a/drivers/gpu/drm/i915/i915_scheduler.h
> +++ b/drivers/gpu/drm/i915/i915_scheduler.h
> @@ -34,7 +34,8 @@ bool __i915_sched_node_add_dependency(struct i915_sched_node *node,
> unsigned long flags);
>
> int i915_sched_node_add_dependency(struct i915_sched_node *node,
> - struct i915_sched_node *signal);
> + struct i915_sched_node *signal,
> + unsigned long flags);
>
> void i915_sched_node_fini(struct i915_sched_node *node);
>
> diff --git a/drivers/gpu/drm/i915/i915_scheduler_types.h b/drivers/gpu/drm/i915/i915_scheduler_types.h
> index d18e70550054..7186875088a0 100644
> --- a/drivers/gpu/drm/i915/i915_scheduler_types.h
> +++ b/drivers/gpu/drm/i915/i915_scheduler_types.h
> @@ -78,6 +78,7 @@ struct i915_dependency {
> unsigned long flags;
> #define I915_DEPENDENCY_ALLOC BIT(0)
> #define I915_DEPENDENCY_EXTERNAL BIT(1)
> +#define I915_DEPENDENCY_WEAK BIT(2)
> };
>
> #endif /* _I915_SCHEDULER_TYPES_H_ */
>
next prev parent reply other threads:[~2020-05-07 14:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 8:21 [PATCH 1/3] drm/i915: Mark concurrent submissions with a weak-dependency Chris Wilson
2020-05-07 14:53 ` Tvrtko Ursulin [this message]
2020-05-07 15:00 ` [Intel-gfx] " Chris Wilson
2020-05-07 15:23 ` Tvrtko Ursulin
2020-05-07 15:34 ` Chris Wilson
2020-05-07 17:55 ` Tvrtko Ursulin
2020-05-07 18:05 ` Chris Wilson
-- strict thread matches above, loose matches on Subject: below --
2020-05-07 15:23 Chris Wilson
2020-05-07 17:56 ` [Intel-gfx] " Tvrtko Ursulin
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=f5d72c82-7a9e-3142-f297-b2231f2e9b9f@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).