From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 12/18] drm/i915: Defer request emission
Date: Mon, 19 Sep 2016 15:06:21 +0300 [thread overview]
Message-ID: <1474286781.3344.31.camel@linux.intel.com> (raw)
In-Reply-To: <20160914065250.15482-13-chris@chris-wilson.co.uk>
On ke, 2016-09-14 at 07:52 +0100, Chris Wilson wrote:
> +static void gen8_emit_wa_tail(struct drm_i915_gem_request *request, u32 *out)
> {
> - struct intel_ring *ring = request->ring;
> - int ret;
> -
> - ret = intel_ring_begin(request, 6 + WA_TAIL_DWORDS);
> - if (ret)
> - return ret;
> + out[0] = MI_NOOP;
> + out[1] = MI_NOOP;
How about storing 'out' on the request and still using the emit
wrapper? I assume passing a separate variable might end up rather
fragile.
> -static int gen8_rcs_signal(struct drm_i915_gem_request *req)
> +static u32 *gen8_rcs_signal(struct drm_i915_gem_request *req, u32 *out)
> {
> - struct intel_ring *ring = req->ring;
> struct drm_i915_private *dev_priv = req->i915;
> struct intel_engine_cs *waiter;
> enum intel_engine_id id;
> - int ret, num_rings;
> -
> - num_rings = INTEL_INFO(dev_priv)->num_rings;
> - ret = intel_ring_begin(req, (num_rings-1) * 8);
> - if (ret)
> - return ret;
>
> for_each_engine_id(waiter, dev_priv, id) {
> u64 gtt_offset = req->engine->semaphore.signal_ggtt[id];
> if (gtt_offset == MI_SEMAPHORE_SYNC_INVALID)
> continue;
>
> - intel_ring_emit(ring, GFX_OP_PIPE_CONTROL(6));
> - intel_ring_emit(ring,
> - PIPE_CONTROL_GLOBAL_GTT_IVB |
> - PIPE_CONTROL_QW_WRITE |
> - PIPE_CONTROL_CS_STALL);
> - intel_ring_emit(ring, lower_32_bits(gtt_offset));
> - intel_ring_emit(ring, upper_32_bits(gtt_offset));
> - intel_ring_emit(ring, req->global_seqno);
> - intel_ring_emit(ring, 0);
> - intel_ring_emit(ring,
> - MI_SEMAPHORE_SIGNAL |
> - MI_SEMAPHORE_TARGET(waiter->hw_id));
> - intel_ring_emit(ring, 0);
> + *out++ = GFX_OP_PIPE_CONTROL(6);
> + *out++ = (PIPE_CONTROL_GLOBAL_GTT_IVB |
> + PIPE_CONTROL_QW_WRITE |
> + PIPE_CONTROL_CS_STALL);
> + *out++ = lower_32_bits(gtt_offset);
> + *out++ = upper_32_bits(gtt_offset);
> + *out++ = req->global_seqno;
> + *out++ = 0;
> + *out++ = (MI_SEMAPHORE_SIGNAL |
> + MI_SEMAPHORE_TARGET(waiter->hw_id));
> + *out++ = 0;
And this is mixing a different approach in... Pick one and convert
others to it. I like having the wrapper for easier grepping of emitted
commands, but YMMV.
> +static void gen6_sema_emit_request(struct drm_i915_gem_request *req,
> + u32 *out)
> {
> - int ret;
> -
> - ret = req->engine->semaphore.signal(req);
> - if (ret)
> - return ret;
> -
> - return i9xx_emit_request(req);
> + return i9xx_emit_request(req, req->engine->semaphore.signal(req, out));
Not sure if this chaining is beautiful, I'd split signal to its own
line of "out = ...".
Those addressed,
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
--
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
next prev parent reply other threads:[~2016-09-19 12:06 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 6:52 Tracking multiple timelines (full-ppgtt) Chris Wilson
2016-09-14 6:52 ` [PATCH 01/18] drm/i915: Support asynchronous waits on struct fence from i915_gem_request Chris Wilson
2016-09-14 7:37 ` Joonas Lahtinen
2016-09-19 11:26 ` Chris Wilson
2016-09-14 6:52 ` [PATCH 02/18] drm/i915: Allow i915_sw_fence_await_sw_fence() to allocate Chris Wilson
2016-09-14 7:51 ` Joonas Lahtinen
2016-09-14 8:46 ` Chris Wilson
2016-09-14 6:52 ` [PATCH 03/18] drm/i915: Rearrange i915_wait_request() accounting with callers Chris Wilson
2016-09-14 8:47 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 04/18] drm/i915: Remove unused i915_gem_active_wait() in favour of _unlocked() Chris Wilson
2016-09-14 8:48 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 05/18] drm/i915: Move GEM activity tracking into a common struct reservation_object Chris Wilson
2016-09-14 9:44 ` Joonas Lahtinen
2016-09-14 17:35 ` Chris Wilson
2016-09-15 9:38 ` Dave Gordon
2016-09-15 9:55 ` Jani Nikula
2016-09-16 11:40 ` Chris Wilson
2016-09-14 6:52 ` [PATCH 06/18] drm: Add reference counting to drm_atomic_state Chris Wilson
2016-09-14 6:52 ` [PATCH 07/18] drm/i915: Restore nonblocking awaits for modesetting Chris Wilson
2016-09-19 16:01 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 08/18] drm/i915: Combine seqno + tracking into a global timeline struct Chris Wilson
2016-09-14 15:42 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 09/18] drm/i915: Wait first for submission, before waiting for request completion Chris Wilson
2016-09-19 8:59 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 10/18] drm/i915: Introduce a global_seqno for each request Chris Wilson
2016-09-19 10:36 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 11/18] drm/i915: Record space required for request emission Chris Wilson
2016-09-14 13:30 ` Tvrtko Ursulin
2016-09-14 17:33 ` Chris Wilson
2016-09-15 8:59 ` Tvrtko Ursulin
2016-09-19 10:47 ` Joonas Lahtinen
2016-09-19 11:32 ` Chris Wilson
2016-09-19 16:09 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 12/18] drm/i915: Defer " Chris Wilson
2016-09-19 12:06 ` Joonas Lahtinen [this message]
2016-09-14 6:52 ` [PATCH 13/18] drm/i915: Move the global sync optimisation to the timeline Chris Wilson
2016-09-19 13:16 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 14/18] drm/i915: Create a unique name for the context Chris Wilson
2016-09-19 13:23 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 15/18] drm/i915: Reserve space in the global seqno during request allocation Chris Wilson
2016-09-19 13:47 ` Joonas Lahtinen
2016-09-19 15:35 ` Jani Nikula
2016-09-19 16:07 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 16/18] drm/i915: Enable multiple timelines Chris Wilson
2016-09-19 15:52 ` Joonas Lahtinen
2016-10-20 12:49 ` Chris Wilson
2016-10-20 15:25 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 17/18] drm/i915: Enable userspace to opt-out of implicit fencing Chris Wilson
2016-09-14 6:52 ` [PATCH 18/18] drm/i915: Support explicit fencing for execbuf Chris Wilson
2016-09-14 9:16 ` ✗ Fi.CI.BAT: failure for series starting with [01/18] drm/i915: Support asynchronous waits on struct fence from i915_gem_request 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=1474286781.3344.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;
as well as URLs for NNTP newsgroup(s).