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: [PATCH 09/11] drm/i915: Wait for engines to idle before retiring
Date: Thu, 31 May 2018 19:52:02 +0100	[thread overview]
Message-ID: <20180531185204.19520-10-chris@chris-wilson.co.uk> (raw)
In-Reply-To: <20180531185204.19520-1-chris@chris-wilson.co.uk>

In the next patch, we will start to defer retiring the request from the
engine list if it is still active on the submission backend. To preserve
the semantics that after wait-for-idle completes the system is idle and
fully retired, we need to therefore wait for the backends to idle before
calling i915_retire_requests().

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
---
 drivers/gpu/drm/i915/i915_gem.c | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
index 550fa8288c45..3e442c3094e7 100644
--- a/drivers/gpu/drm/i915/i915_gem.c
+++ b/drivers/gpu/drm/i915/i915_gem.c
@@ -3768,10 +3768,13 @@ int i915_gem_wait_for_idle(struct drm_i915_private *i915, unsigned int flags)
 			if (err)
 				return err;
 		}
+
+		err = wait_for_engines(i915);
+		if (err)
+			return err;
+
 		i915_retire_requests(i915);
 		GEM_BUG_ON(i915->gt.active_requests);
-
-		return wait_for_engines(i915);
 	} else {
 		struct intel_engine_cs *engine;
 		enum intel_engine_id id;
@@ -3782,9 +3785,9 @@ int i915_gem_wait_for_idle(struct drm_i915_private *i915, unsigned int flags)
 			if (err)
 				return err;
 		}
-
-		return 0;
 	}
+
+	return 0;
 }
 
 static void __i915_gem_object_flush_for_display(struct drm_i915_gem_object *obj)
-- 
2.17.1

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

  parent reply	other threads:[~2018-05-31 18:52 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 18:51 ksoftirqd avoidance Chris Wilson
2018-05-31 18:51 ` [PATCH 01/11] drm/i915: Be irqsafe inside reset Chris Wilson
2018-06-01 13:44   ` Tvrtko Ursulin
2018-05-31 18:51 ` [PATCH 02/11] drm/i915/execlists: Reset the CSB head tracking on reset/sanitization Chris Wilson
2018-06-01 13:54   ` Tvrtko Ursulin
2018-05-31 18:51 ` [PATCH 03/11] drm/i915/execlists: Pull submit after dequeue under timeline lock Chris Wilson
2018-06-01 14:02   ` Tvrtko Ursulin
2018-06-01 14:07     ` Chris Wilson
2018-06-04  9:25       ` Tvrtko Ursulin
2018-06-04 10:12         ` Chris Wilson
2018-06-04 10:58           ` Tvrtko Ursulin
2018-06-04 11:15             ` Chris Wilson
2018-06-04 14:19   ` Tvrtko Ursulin
2018-05-31 18:51 ` [PATCH 04/11] drm/i915/execlists: Pull CSB reset under the timeline.lock Chris Wilson
2018-06-04 14:25   ` Tvrtko Ursulin
2018-06-04 15:29     ` Chris Wilson
2018-06-05  8:25       ` Tvrtko Ursulin
2018-05-31 18:51 ` [PATCH 05/11] drm/i915/execlists: Process one CSB interrupt at a time Chris Wilson
2018-06-04 14:27   ` Tvrtko Ursulin
2018-06-04 15:32     ` Chris Wilson
2018-06-05  8:30       ` Tvrtko Ursulin
2018-05-31 18:51 ` [PATCH 06/11] drm/i915/execlists: Unify CSB access pointers Chris Wilson
2018-06-04 14:53   ` Tvrtko Ursulin
2018-06-04 16:58     ` Daniele Ceraolo Spurio
2018-06-05  8:38       ` Tvrtko Ursulin
2018-05-31 18:52 ` [PATCH 07/11] drm/i915/execlists: Direct submission of new requests (avoid tasklet/ksoftirqd) Chris Wilson
2018-05-31 19:57   ` [PATCH] " Chris Wilson
2018-05-31 18:52 ` [PATCH 08/11] drm/i915: Move rate-limiting request retire to after submission Chris Wilson
2018-05-31 18:52 ` Chris Wilson [this message]
2018-05-31 18:52 ` [PATCH 10/11] drm/i915: Move engine request retirement to intel_engine_cs Chris Wilson
2018-05-31 18:52 ` [PATCH 11/11] drm/i915: Hold request reference for submission until retirement Chris Wilson
2018-05-31 20:21   ` [PATCH] " Chris Wilson
2018-05-31 19:30 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/11] drm/i915: Be irqsafe inside reset Patchwork
2018-05-31 19:48 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-05-31 20:14 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/11] drm/i915: Be irqsafe inside reset (rev2) Patchwork
2018-05-31 20:33 ` ✓ Fi.CI.BAT: success " Patchwork
2018-05-31 20:37 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/11] drm/i915: Be irqsafe inside reset (rev3) Patchwork
2018-05-31 20:54 ` ✓ Fi.CI.BAT: success " Patchwork
2018-05-31 21:54 ` ✗ 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=20180531185204.19520-10-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.