public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 19/25] drm/i915/lrc: Update function names to match request flow
Date: Fri, 22 Jul 2016 12:23:27 +0300	[thread overview]
Message-ID: <1469179407.5916.31.camel@linux.intel.com> (raw)
In-Reply-To: <1469178232-7574-19-git-send-email-chris@chris-wilson.co.uk>

On pe, 2016-07-22 at 10:03 +0100, Chris Wilson wrote:
> With adding engine->submit_request, we now have a bunch of functions
> with similar names used at different stages of the execlist submission.
> Try a different coat of paint, to hopefully reduce confusion between the
> requests, intel_engine_cs and the actual execlists submision process.
> 

Better,

Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>

> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_lrc.c | 16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_lrc.c b/drivers/gpu/drm/i915/intel_lrc.c
> index a9ca31c113c3..149a0dc7aeed 100644
> --- a/drivers/gpu/drm/i915/intel_lrc.c
> +++ b/drivers/gpu/drm/i915/intel_lrc.c
> @@ -384,8 +384,8 @@ static void execlists_update_context(struct drm_i915_gem_request *rq)
>  		execlists_update_context_pdps(ppgtt, reg_state);
>  }
>  
> -static void execlists_submit_requests(struct drm_i915_gem_request *rq0,
> -				      struct drm_i915_gem_request *rq1)
> +static void execlists_elsp_submit_contexts(struct drm_i915_gem_request *rq0,
> +					   struct drm_i915_gem_request *rq1)
>  {
>  	struct drm_i915_private *dev_priv = rq0->i915;
>  	unsigned int fw_domains = rq0->engine->fw_domains;
> @@ -418,7 +418,7 @@ static inline void execlists_context_status_change(
>  	atomic_notifier_call_chain(&rq->ctx->status_notifier, status, rq);
>  }
>  
> -static void execlists_context_unqueue(struct intel_engine_cs *engine)
> +static void execlists_unqueue(struct intel_engine_cs *engine)
>  {
>  	struct drm_i915_gem_request *req0 = NULL, *req1 = NULL;
>  	struct drm_i915_gem_request *cursor, *tmp;
> @@ -486,7 +486,7 @@ static void execlists_context_unqueue(struct intel_engine_cs *engine)
>  		req0->tail &= req0->ring->size - 1;
>  	}
>  
> -	execlists_submit_requests(req0, req1);
> +	execlists_elsp_submit_contexts(req0, req1);
>  }
>  
>  static unsigned int
> @@ -597,7 +597,7 @@ static void intel_lrc_irq_handler(unsigned long data)
>  	if (submit_contexts) {
>  		if (!engine->disable_lite_restore_wa ||
>  		    (csb[i][0] & GEN8_CTX_STATUS_ACTIVE_IDLE))
> -			execlists_context_unqueue(engine);
> +			execlists_unqueue(engine);
>  	}
>  
>  	spin_unlock(&engine->execlist_lock);
> @@ -606,7 +606,7 @@ static void intel_lrc_irq_handler(unsigned long data)
>  		DRM_ERROR("More than two context complete events?\n");
>  }
>  
> -static void execlists_context_queue(struct drm_i915_gem_request *request)
> +static void execlists_submit_request(struct drm_i915_gem_request *request)
>  {
>  	struct intel_engine_cs *engine = request->engine;
>  	struct drm_i915_gem_request *cursor;
> @@ -637,7 +637,7 @@ static void execlists_context_queue(struct drm_i915_gem_request *request)
>  	list_add_tail(&request->execlist_link, &engine->execlist_queue);
>  	request->ctx_hw_id = request->ctx->hw_id;
>  	if (num_elements == 0)
> -		execlists_context_unqueue(engine);
> +		execlists_unqueue(engine);
>  
>  	spin_unlock_bh(&engine->execlist_lock);
>  }
> @@ -1908,7 +1908,7 @@ logical_ring_default_vfuncs(struct intel_engine_cs *engine)
>  	engine->init_hw = gen8_init_common_ring;
>  	engine->emit_flush = gen8_emit_flush;
>  	engine->emit_request = gen8_emit_request;
> -	engine->submit_request = execlists_context_queue;
> +	engine->submit_request = execlists_submit_request;
>  
>  	engine->irq_enable = gen8_logical_ring_enable_irq;
>  	engine->irq_disable = gen8_logical_ring_disable_irq;
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-07-22  9:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-22  9:03 [PATCH v2 01/25] drm/i915/cmdparser: Remove stray intel_engine_cs *ring Chris Wilson
2016-07-22  9:03 ` [PATCH v2 02/25] drm/i915: Use engine to refer to the user's BSD intel_engine_cs Chris Wilson
2016-07-22  9:03 ` [PATCH v2 03/25] drm/i915: Avoid using intel_engine_cs *ring for GPU error capture Chris Wilson
2016-07-22  9:03 ` [PATCH v2 04/25] drm/i915: Remove stray intel_engine_cs ring identifiers from i915_gem.c Chris Wilson
2016-07-22  9:03 ` [PATCH v2 05/25] drm/i915: Update a couple of hangcheck comments to talk about engines Chris Wilson
2016-07-22  9:03 ` [PATCH v2 06/25] drm/i915: Unify intel_logical_ring_emit and intel_ring_emit Chris Wilson
2016-07-22  9:03 ` [PATCH v2 07/25] drm/i915: Rename request->ringbuf to request->ring Chris Wilson
2016-07-22  9:03 ` [PATCH v2 08/25] drm/i915: Rename backpointer from intel_ringbuffer to intel_engine_cs Chris Wilson
2016-07-22  9:03 ` [PATCH v2 09/25] drm/i915: Rename intel_context[engine].ringbuf Chris Wilson
2016-07-22  9:03 ` [PATCH v2 10/25] drm/i915: Rename struct intel_ringbuffer to struct intel_ring Chris Wilson
2016-07-22  9:03 ` [PATCH v2 11/25] drm/i915: Rename residual ringbuf parameters Chris Wilson
2016-07-22  9:03 ` [PATCH v2 12/25] drm/i915: Rename intel_pin_and_map_ring() Chris Wilson
2016-07-22  9:03 ` [PATCH v2 13/25] drm/i915: Remove obsolete engine->gpu_caches_dirty Chris Wilson
2016-07-22  9:03 ` [PATCH v2 14/25] drm/i915: Simplify request_alloc by returning the allocated request Chris Wilson
2016-07-22  9:03 ` [PATCH v2 15/25] drm/i915: Unify legacy/execlists emission of MI_BATCHBUFFER_START Chris Wilson
2016-07-22  9:03 ` [PATCH v2 16/25] drm/i915: Remove intel_ring_get_tail() Chris Wilson
2016-07-22  9:03 ` [PATCH v2 17/25] drm/i915: Convert engine->write_tail to operate on a request Chris Wilson
2016-07-22  9:03 ` [PATCH v2 18/25] drm/i915: Unify request submission Chris Wilson
2016-07-22  9:03 ` [PATCH v2 19/25] drm/i915/lrc: Update function names to match request flow Chris Wilson
2016-07-22  9:23   ` Joonas Lahtinen [this message]
2016-07-22  9:03 ` [PATCH v2 20/25] drm/i915: Stop passing caller's num_dwords to engine->semaphore.signal() Chris Wilson
2016-07-22  9:03 ` [PATCH v2 21/25] drm/i915: Reuse legacy breadcrumbs + tail emission Chris Wilson
2016-07-22  9:03 ` [PATCH v2 22/25] drm/i915/ringbuffer: Specialise SNB+ request emission for semaphores Chris Wilson
2016-07-22  9:03 ` [PATCH v2 23/25] drm/i915: Remove duplicate golden render state init from execlists Chris Wilson
2016-07-22  9:03 ` [PATCH v2 24/25] drm/i915: Unify legacy/execlists submit_execbuf callbacks Chris Wilson
2016-07-22  9:03 ` [PATCH v2 25/25] drm/i915: Simplify calling engine->sync_to Chris Wilson
2016-07-22  9:36 ` ✗ Ro.CI.BAT: failure for series starting with [v2,01/25] drm/i915/cmdparser: Remove stray intel_engine_cs *ring 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=1469179407.5916.31.camel@linux.intel.com \
    --to=joonas.lahtinen@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