All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Intel-gfx@lists.freedesktop.org,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Subject: Re: [PATCH 4/7] drm/i915: Add timeline barrier support
Date: Fri, 14 Dec 2018 13:26:34 +0000	[thread overview]
Message-ID: <154479399422.11001.6020778395942261561@skylake-alporthouse-com> (raw)
In-Reply-To: <20181214123449.23847-5-tvrtko.ursulin@linux.intel.com>

Quoting Tvrtko Ursulin (2018-12-14 12:34:46)
> diff --git a/drivers/gpu/drm/i915/i915_timeline.h b/drivers/gpu/drm/i915/i915_timeline.h
> index ebd71b487220..6ee301f20bab 100644
> --- a/drivers/gpu/drm/i915/i915_timeline.h
> +++ b/drivers/gpu/drm/i915/i915_timeline.h
> @@ -72,6 +72,16 @@ struct i915_timeline {
>          */
>         u32 global_sync[I915_NUM_ENGINES];
>  
> +       /**
> +        * Barrier provides the ability to serialize ordering between different
> +        * timelines.
> +        *
> +        * Users can call i915_timeline_set_barrier which will make all
> +        * subsequent submissions be executed only after this barrier has been

submissions on/to this timeline
then s/this barrier/the barrier/ to avoid repitation of this.

> +        * completed.
> +        */
> +       struct i915_gem_active barrier;
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-12-14 13:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14 12:34 [PATCH 0/7] Per context dynamic (sub)slice power-gating Tvrtko Ursulin
2018-12-14 12:34 ` [PATCH 1/7] drm/i915/execlists: Move RPCS setup to context pin Tvrtko Ursulin
2018-12-14 12:34 ` [PATCH 2/7] drm/i915: Record the sseu configuration per-context & engine Tvrtko Ursulin
2018-12-14 12:34 ` [PATCH 3/7] drm/i915/perf: lock powergating configuration to default when active Tvrtko Ursulin
2018-12-14 12:34 ` [PATCH 4/7] drm/i915: Add timeline barrier support Tvrtko Ursulin
2018-12-14 13:26   ` Chris Wilson [this message]
2018-12-14 12:34 ` [PATCH 5/7] drm/i915: Expose RPCS (SSEU) configuration to userspace (Gen11 only) Tvrtko Ursulin
2018-12-14 13:33   ` Chris Wilson
2018-12-31 15:21     ` Tvrtko Ursulin
2018-12-31 15:33       ` Chris Wilson
2018-12-31 15:39         ` Tvrtko Ursulin
2018-12-14 12:34 ` [PATCH 6/7] drm/i915/icl: Support co-existence between per-context SSEU and OA Tvrtko Ursulin
2018-12-14 12:34 ` [PATCH 7/7] drm/i915/selftests: Context SSEU reconfiguration tests Tvrtko Ursulin
2018-12-14 13:04   ` Chris Wilson
2018-12-14 13:22   ` Chris Wilson
2018-12-14 12:55 ` ✗ Fi.CI.CHECKPATCH: warning for Per context dynamic (sub)slice power-gating (rev8) Patchwork
2018-12-14 12:58 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-12-14 13:11 ` ✓ Fi.CI.BAT: success " Patchwork
2018-12-14 15:07 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-12-31 16:06 [PATCH 0/7] Per context dynamic (sub)slice power-gating Tvrtko Ursulin
2018-12-31 16:06 ` [PATCH 4/7] drm/i915: Add timeline barrier support Tvrtko Ursulin
2019-01-08 11:22 [PATCH 0/7] Per context dynamic (sub)slice power-gating Tvrtko Ursulin
2019-01-08 11:22 ` [PATCH 4/7] drm/i915: Add timeline barrier support Tvrtko Ursulin

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=154479399422.11001.6020778395942261561@skylake-alporthouse-com \
    --to=chris@chris-wilson.co.uk \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=tvrtko.ursulin@linux.intel.com \
    /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.