From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915/gem: Take a copy of the engines for context_barrier_task
Date: Wed, 11 Mar 2020 13:02:55 +0000 [thread overview]
Message-ID: <158393177543.10732.233554342691472095@build.alporthouse.com> (raw)
In-Reply-To: <20200311125903.1982-1-chris@chris-wilson.co.uk>
Quoting Chris Wilson (2020-03-11 12:59:03)
> +static inline struct i915_gem_engines *
> +__context_engines_await(const struct i915_gem_context *ctx)
> +{
> + struct i915_gem_engines *engines;
> +
> + rcu_read_lock();
> + do {
> + engines = rcu_dereference(ctx->engines);
> + if (!unlikely(engines))
> + break;
> +
> + if (!unlikely(i915_sw_fence_await(&engines->fence)))
> + continue;
Pebkac.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-03-11 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 12:59 [Intel-gfx] [PATCH v2] drm/i915/gem: Take a copy of the engines for context_barrier_task Chris Wilson
2020-03-11 13:02 ` Chris Wilson [this message]
2020-03-11 17:15 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gem: Take a copy of the engines for context_barrier_task (rev2) Patchwork
2020-03-11 17:28 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-03-11 17:58 ` [Intel-gfx] [PATCH] drm/i915/gem: Take a copy of the engines for context_barrier_task Chris Wilson
2020-03-12 1:15 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gem: Take a copy of the engines for context_barrier_task (rev3) Patchwork
2020-03-12 1:39 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-03-12 18:53 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=158393177543.10732.233554342691472095@build.alporthouse.com \
--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 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).