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 v2 15/21] drm/i915: Move context initialisation to first-use
Date: Sun, 24 Apr 2016 08:31:35 +0100	[thread overview]
Message-ID: <1461483101-10618-15-git-send-email-chris@chris-wilson.co.uk> (raw)
In-Reply-To: <1461483101-10618-1-git-send-email-chris@chris-wilson.co.uk>

Instead of allocating a new request when allocating a context, use the
request that initiated the allocation to emit the context
initialisation. This serves two purposes, it makes the initialisation
atomic with first use (simplifying scheduling and our own error
handling). Secondly, it enables us to remove the explicit context
allocation required by higher levels of GEM and make that property of
execlists opaque (in the next patch). There is also a minor step
forwards towards convergence of legacy/execlist contexts.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
---
 drivers/gpu/drm/i915/i915_drv.h  |  1 +
 drivers/gpu/drm/i915/intel_lrc.c | 49 +++++++++++++++++++++++-----------------
 2 files changed, 29 insertions(+), 21 deletions(-)

diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
index 2bf3a8f97d52..e4b510bcee62 100644
--- a/drivers/gpu/drm/i915/i915_drv.h
+++ b/drivers/gpu/drm/i915/i915_drv.h
@@ -868,6 +868,7 @@ struct intel_context {
 		struct i915_vma *lrc_vma;
 		u64 lrc_desc;
 		uint32_t *lrc_reg_state;
+		bool initialised;
 	} engine[I915_NUM_ENGINES];
 
 	struct list_head link;
diff --git a/drivers/gpu/drm/i915/intel_lrc.c b/drivers/gpu/drm/i915/intel_lrc.c
index 838abd4b42a3..eeb8be695288 100644
--- a/drivers/gpu/drm/i915/intel_lrc.c
+++ b/drivers/gpu/drm/i915/intel_lrc.c
@@ -672,9 +672,10 @@ static int execlists_move_to_gpu(struct drm_i915_gem_request *req,
 
 int intel_logical_ring_alloc_request_extras(struct drm_i915_gem_request *request)
 {
-	int ret = 0;
+	struct intel_engine_cs *engine = request->engine;
+	int ret;
 
-	request->ringbuf = request->ctx->engine[request->engine->id].ringbuf;
+	request->ringbuf = request->ctx->engine[engine->id].ringbuf;
 
 	if (i915.enable_guc_submission) {
 		/*
@@ -689,7 +690,30 @@ int intel_logical_ring_alloc_request_extras(struct drm_i915_gem_request *request
 			return ret;
 	}
 
-	return intel_lr_context_pin(request->ctx, request->engine);
+	ret = intel_lr_context_pin(request->ctx, engine);
+	if (ret)
+		return ret;
+
+	if (!request->ctx->engine[engine->id].initialised) {
+		ret = engine->init_context(request);
+		if (ret)
+			goto err_unpin;
+
+		request->ctx->engine[engine->id].initialised = true;
+	}
+
+	/* Note that after this point, we have committed to using
+	 * this request as it is being used to both track the
+	 * state of engine initialisation and liveness of the
+	 * golden renderstate above. Think twice before you try
+	 * to cancel/unwind this request now.
+	 */
+
+	return 0;
+
+err_unpin:
+	intel_lr_context_unpin(request->ctx, engine);
+	return ret;
 }
 
 static int logical_ring_wait_for_space(struct drm_i915_gem_request *req,
@@ -2634,25 +2658,8 @@ int intel_lr_context_deferred_alloc(struct intel_context *ctx,
 
 	ctx->engine[engine->id].ringbuf = ringbuf;
 	ctx->engine[engine->id].state = ctx_obj;
+	ctx->engine[engine->id].initialised = engine->init_context == NULL;
 
-	if (ctx != ctx->i915->kernel_context && engine->init_context) {
-		struct drm_i915_gem_request *req;
-
-		req = i915_gem_request_alloc(engine, ctx);
-		if (IS_ERR(req)) {
-			ret = PTR_ERR(req);
-			DRM_ERROR("ring create req: %d\n", ret);
-			goto error_ringbuf;
-		}
-
-		ret = engine->init_context(req);
-		i915_add_request_no_flush(req);
-		if (ret) {
-			DRM_ERROR("ring init context: %d\n",
-				ret);
-			goto error_ringbuf;
-		}
-	}
 	return 0;
 
 error_ringbuf:
-- 
2.8.1

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

  parent reply	other threads:[~2016-04-24  7:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-24  7:31 [PATCH v2 01/21] drm/i915/fbdev: Call intel_unpin_fb_obj() on release Chris Wilson
2016-04-24  7:31 ` [PATCH v2 02/21] drm/i915/overlay: Replace i915_gem_obj_ggtt_offset() with the known flip_addr Chris Wilson
2016-04-24  7:31 ` [PATCH v2 03/21] io-mapping: Specify mapping size for io_mapping_map_wc() Chris Wilson
2016-04-24  7:31   ` Chris Wilson
2016-04-24  7:31   ` Chris Wilson
2016-04-24  7:31 ` [PATCH v2 04/21] drm/i915: Introduce i915_vm_to_ggtt() Chris Wilson
2016-04-24  7:31 ` [PATCH v2 05/21] drm/i915: Move ioremap_wc tracking onto VMA Chris Wilson
2016-04-24  7:31 ` [PATCH v2 06/21] drm/i915: Use i915_vma_pin_iomap on the ringbuffer object Chris Wilson
2016-04-24  7:31 ` [PATCH v2 07/21] drm/i915: Mark the current context as lost on suspend Chris Wilson
2016-04-24  7:31 ` [PATCH v2 08/21] drm/i915: L3 cache remapping is part of context switching Chris Wilson
2016-04-24  7:31 ` [PATCH v2 09/21] drm/i915: Consolidate L3 remapping LRI Chris Wilson
2016-04-24  7:31 ` [PATCH v2 10/21] drm/i915: Remove early l3-remap Chris Wilson
2016-04-24  7:31 ` [PATCH v2 11/21] drm/i915: Rearrange switch_context to load the aliasing ppgtt on first use Chris Wilson
2016-04-24  7:31 ` [PATCH v2 12/21] drm/i915: Assign every HW context a unique ID Chris Wilson
2016-04-24  7:31 ` [PATCH v2 13/21] drm/i915: Replace the pinned context address with its " Chris Wilson
2016-04-24  7:31 ` [PATCH v2 14/21] drm/i915: Refactor execlists default context pinning Chris Wilson
2016-04-24  7:31 ` Chris Wilson [this message]
2016-04-24  7:31 ` [PATCH v2 16/21] drm/i915: Move the magical deferred context allocation into the request Chris Wilson
2016-04-24  7:31 ` [PATCH v2 17/21] drm/i915: Move releasing of the GEM request from free to retire/cancel Chris Wilson
2016-04-24  7:31 ` [PATCH v2 18/21] drm/i915: Track the previous pinned context inside the request Chris Wilson
2016-04-24  7:31 ` [PATCH v2 19/21] drm/i915: Store LRC hardware id in " Chris Wilson
2016-04-24  7:31 ` [PATCH v2 20/21] drm/i915: Stop tracking execlists retired requests Chris Wilson
2016-04-24  7:31 ` [PATCH v2 21/21] drm/i915: Unify GPU resets upon shutdown Chris Wilson
2016-04-24 11:51 ` ✗ Fi.CI.BAT: failure for series starting with [v2,01/21] drm/i915/fbdev: Call intel_unpin_fb_obj() on release Patchwork
2016-04-24 12:40   ` Chris Wilson

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=1461483101-10618-15-git-send-email-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.