All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 16/17] drm/i915/execlists: Check the sentinel is alone in the ELSP
Date: Wed, 26 Feb 2020 09:43:13 +0000	[thread overview]
Message-ID: <20200226094314.1500667-16-chris@chris-wilson.co.uk> (raw)
In-Reply-To: <20200226094314.1500667-1-chris@chris-wilson.co.uk>

We only use sentinel requests for "preempt-to-idle" passes, so assert
that they are the only request in a new submission.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
---
 drivers/gpu/drm/i915/gt/intel_lrc.c | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c
index 253e89fecd95..d907b5ebc1a4 100644
--- a/drivers/gpu/drm/i915/gt/intel_lrc.c
+++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
@@ -1448,6 +1448,7 @@ assert_pending_valid(const struct intel_engine_execlists *execlists,
 {
 	struct i915_request * const *port, *rq;
 	struct intel_context *ce = NULL;
+	bool sentinel = false;
 
 	trace_ports(execlists, msg, execlists->pending);
 
@@ -1481,6 +1482,26 @@ assert_pending_valid(const struct intel_engine_execlists *execlists,
 		}
 		ce = rq->context;
 
+		/*
+		 * Sentinels are supposed to be lonely so they flush the
+		 * current exection off the HW. Check that they are the
+		 * only request in the pending submission.
+		 */
+		if (sentinel) {
+			GEM_TRACE_ERR("context:%llx after sentinel in pending[%zd]\n",
+				      ce->timeline->fence_context,
+				      port - execlists->pending);
+			return false;
+		}
+
+		sentinel = i915_request_has_sentinel(rq);
+		if (sentinel && port != execlists->pending) {
+			GEM_TRACE_ERR("sentinel context:%llx not in prime position[%zd]\n",
+				      ce->timeline->fence_context,
+				      port - execlists->pending);
+			return false;
+		}
+
 		/* Hold tightly onto the lock to prevent concurrent retires! */
 		if (!spin_trylock_irqsave(&rq->lock, flags))
 			continue;
-- 
2.25.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2020-02-26  9:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-26  9:42 [Intel-gfx] [PATCH 01/17] drm/i915/gt: Reset queue_priority_hint after wedging Chris Wilson
2020-02-26  9:42 ` [Intel-gfx] [PATCH 02/17] drm/i915/perf: Mark up the racy use of perf->exclusive_stream Chris Wilson
2020-02-26  9:43 ` [Intel-gfx] [PATCH 03/17] drm/i915: Manually acquire engine-wakeref around use of kernel_context Chris Wilson
2020-02-26  9:43 ` [Intel-gfx] [PATCH 04/17] drm/i915/gt: Pull marking vm as closed underneath the vm->mutex Chris Wilson
2020-02-26  9:43 ` [Intel-gfx] [PATCH 05/17] drm/i915: Protect i915_request_await_start from early waits Chris Wilson
2020-02-26  9:43 ` [Intel-gfx] [PATCH 06/17] drm/i915/selftests: Verify LRC isolation Chris Wilson
2020-02-26  9:43 ` [Intel-gfx] [PATCH 07/17] drm/i915/selftests: Check recovery from corrupted LRC Chris Wilson
2020-02-26  9:43 ` [Intel-gfx] [PATCH 08/17] drm/i915/selftests: Wait for the kernel context switch Chris Wilson
2020-02-26  9:43 ` [Intel-gfx] [PATCH 09/17] drm/i915/selftests: Be a little more lenient for reset workers Chris Wilson
2020-02-26  9:43 ` [Intel-gfx] [PATCH 10/17] drm/i915/selftests: Add request throughput measurement to perf Chris Wilson
2020-02-26  9:43 ` [Intel-gfx] [PATCH 11/17] drm/i915/gem: Consolidate ctx->engines[] release Chris Wilson
2020-02-26  9:43 ` [Intel-gfx] [PATCH 12/17] drm/i915/gt: Prevent allocation on a banned context Chris Wilson
2020-02-26  9:43 ` [Intel-gfx] [PATCH 13/17] drm/i915/gem: Check that the context wasn't closed during setup Chris Wilson
2020-02-26  9:43 ` [Intel-gfx] [PATCH 14/17] drm/i915/gt: Declare when we enabled timeslicing Chris Wilson
2020-02-26  9:43 ` [Intel-gfx] [PATCH 15/17] drm/i915/gt: Yield the timeslice if caught waiting on a user semaphore Chris Wilson
2020-02-26  9:43 ` Chris Wilson [this message]
2020-02-26  9:43 ` [Intel-gfx] [PATCH 17/17] drm/i915/execlists: Reduce preempt-to-busy roundtrip delay Chris Wilson
2020-02-26 19:12 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/17] drm/i915/gt: Reset queue_priority_hint after wedging Patchwork
2020-02-26 19:39 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-02-27 10:25 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=20200226094314.1500667-16-chris@chris-wilson.co.uk \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.