From: Chris Wilson <chris@chris-wilson.co.uk>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/7] drm/i915: Unwrap top level fence-array
Date: Wed, 3 May 2017 10:14:26 +0100 [thread overview]
Message-ID: <20170503091426.GK19680@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <fe5b5974-84b8-4b1f-d4dc-829e9564a281@linux.intel.com>
On Wed, May 03, 2017 at 10:00:02AM +0100, Tvrtko Ursulin wrote:
>
> On 03/05/2017 00:41, Chris Wilson wrote:
> >By first unwrapping an incoming fence-array into its child fences, we
> >can simplify the internal branching, and so avoid triggering a potential
>
> Potential something?
+ bug
> >in the next patch when not squashing the child fences on the same timeline.
> >
> >It will also have the advantage of keeping the (top-level) fence arrays
> >out of any fence/timeline caching since these are unordered timelines
> >but with a random context id.
>
> Is it a random context id or just one not associated with any user
> contexts and not ever exported to userspace?
Yes, I was using random as a derogative ;) It has an unpredictable
one-off id, that is never repeated (this millenia, at least) and not tied
to anything real, either userspace or hw. We could reduce all such beasts
to a single unordered timeline...
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-05-03 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 23:41 [PATCH 1/7] drm/i915: Mark up clflushes as belonging to an unordered timeline Chris Wilson
2017-05-02 23:41 ` [PATCH 2/7] drm/i915: Unwrap top level fence-array Chris Wilson
2017-05-03 9:00 ` Tvrtko Ursulin
2017-05-03 9:14 ` Chris Wilson [this message]
2017-05-02 23:41 ` [PATCH 3/7] drm/i915: Lift timeline ordering to await_dma_fence Chris Wilson
2017-05-02 23:41 ` [PATCH 4/7] drm/i915: Squash repeated awaits on the same fence Chris Wilson
2017-05-02 23:41 ` [PATCH 5/7] drm/i915: Rename intel_timeline.sync_seqno[] to .global_sync[] Chris Wilson
2017-05-02 23:41 ` [PATCH 6/7] drm/i915: Do not record a successful syncpoint for a dma-await Chris Wilson
2017-05-02 23:41 ` [PATCH 7/7] drm/i915: Switch the global i915.semaphores check to a local predicate Chris Wilson
2017-05-03 0:02 ` ✓ Fi.CI.BAT: success for series starting with [1/7] drm/i915: Mark up clflushes as belonging to an unordered timeline 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=20170503091426.GK19680@nuc-i3427.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.