From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/5] drm/i915: Mark up "sentinel" requests
Date: Tue, 06 Aug 2019 17:29:58 +0300 [thread overview]
Message-ID: <871rxyicyh.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20190806134725.25321-3-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Sometimes we want to emit a terminator request, a request that flushes
> the pipeline and allows no request to come after it. This can be used
> for a "preempt-to-idle" to ensure that upon processing the
> context-switch to that request, all other active contexts have been
> flushed.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/gt/intel_lrc.c | 6 ++++++
> drivers/gpu/drm/i915/i915_request.h | 10 ++++++++--
> 2 files changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c
> index 4e45cd972267..59a7e4eb7e2a 100644
> --- a/drivers/gpu/drm/i915/gt/intel_lrc.c
> +++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
> @@ -759,6 +759,9 @@ static bool can_merge_rq(const struct i915_request *prev,
> GEM_BUG_ON(prev == next);
> GEM_BUG_ON(!assert_priority_queue(prev, next));
>
> + if (i915_request_has_sentinel(prev))
> + return false;
> +
> if (!can_merge_ctx(prev->hw_context, next->hw_context))
> return false;
>
> @@ -1250,6 +1253,9 @@ static void execlists_dequeue(struct intel_engine_cs *engine)
> if (last->hw_context == rq->hw_context)
> goto done;
>
> + if (i915_request_has_sentinel(last))
> + goto done;
> +
> /*
> * If GVT overrides us we only ever submit
> * port[0], leaving port[1] empty. Note that we
> diff --git a/drivers/gpu/drm/i915/i915_request.h b/drivers/gpu/drm/i915/i915_request.h
> index 313df3c37158..c41ecbe0bd0c 100644
> --- a/drivers/gpu/drm/i915/i915_request.h
> +++ b/drivers/gpu/drm/i915/i915_request.h
> @@ -217,8 +217,9 @@ struct i915_request {
> unsigned long emitted_jiffies;
>
> unsigned long flags;
> -#define I915_REQUEST_WAITBOOST BIT(0)
> -#define I915_REQUEST_NOPREEMPT BIT(1)
> +#define I915_REQUEST_WAITBOOST BIT(0)
> +#define I915_REQUEST_NOPREEMPT BIT(1)
> +#define I915_REQUEST_SENTINEL BIT(2)
Would it be possible to use 'empty' ie non payloadable
requests as a sentinel? (using the request->postfix).
Or is the advantage here that by attaching it as
a property, you avoid submitting an extra (empty)?
-Mika
>
> /** timeline->request entry for this request */
> struct list_head link;
> @@ -443,6 +444,11 @@ static inline bool i915_request_has_nopreempt(const struct i915_request *rq)
> return unlikely(rq->flags & I915_REQUEST_NOPREEMPT);
> }
>
> +static inline bool i915_request_has_sentinel(const struct i915_request *rq)
> +{
> + return unlikely(rq->flags & I915_REQUEST_SENTINEL);
> +}
> +
> bool i915_retire_requests(struct drm_i915_private *i915);
>
> #endif /* I915_REQUEST_H */
> --
> 2.23.0.rc1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-08-06 14:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 13:47 [PATCH 1/5] drm/i915: Only enqueue already completed requests Chris Wilson
2019-08-06 13:47 ` [PATCH 2/5] drm/i915/execlists: Force preemption Chris Wilson
2019-08-06 13:47 ` [PATCH 3/5] drm/i915: Mark up "sentinel" requests Chris Wilson
2019-08-06 14:29 ` Mika Kuoppala [this message]
2019-08-06 14:47 ` Chris Wilson
2019-08-06 13:47 ` [PATCH 4/5] drm/i915/execlists: Cancel banned contexts on schedule-out Chris Wilson
2019-08-06 13:47 ` [PATCH 5/5] drm/i915: Cancel non-persistent contexts on close Chris Wilson
2019-08-06 14:11 ` Chris Wilson
2019-08-06 14:26 ` Bloomfield, Jon
2019-08-06 14:41 ` Chris Wilson
2019-08-07 13:22 ` Chris Wilson
2019-08-07 14:04 ` Bloomfield, Jon
2019-08-07 14:14 ` Chris Wilson
2019-08-07 14:33 ` Bloomfield, Jon
2019-08-07 15:08 ` Chris Wilson
2019-08-07 15:29 ` Bloomfield, Jon
2019-08-07 15:38 ` Chris Wilson
2019-08-07 16:51 ` Chris Wilson
2019-08-07 17:12 ` Bloomfield, Jon
2019-08-09 23:34 ` Chris Wilson
2019-08-12 14:39 ` Bloomfield, Jon
2019-08-12 14:51 ` Chris Wilson
2019-08-06 14:25 ` [PATCH 1/5] drm/i915: Only enqueue already completed requests Mika Kuoppala
2019-08-06 14:44 ` Chris Wilson
2019-08-06 14:51 ` ✗ Fi.CI.BAT: failure for series starting with [1/5] " Patchwork
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=871rxyicyh.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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