From: Matthew Auld <matthew.auld@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915: Double check bumping after the spinlock
Date: Thu, 20 Feb 2020 13:02:19 +0000 [thread overview]
Message-ID: <6c039f03-0247-7cef-bcd1-48e366cd31da@intel.com> (raw)
In-Reply-To: <20200220123608.1666271-1-chris@chris-wilson.co.uk>
On 20/02/2020 12:36, Chris Wilson wrote:
> In preparation for making GEM execbuf parallel, we need to be prepared
> to handle very early declaration of dependencies -- even before our
> signaler has itself been submitted.
>
> References: a79ca656b648 ("drm/i915: Push the wakeref->count deferral to the backend")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-02-20 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 12:36 [Intel-gfx] [PATCH 1/2] drm/i915: Double check bumping after the spinlock Chris Wilson
2020-02-20 12:36 ` [Intel-gfx] [PATCH 2/2] drm/i915: Protect i915_request_await_start from early waits Chris Wilson
2020-02-20 13:02 ` Matthew Auld [this message]
2020-02-20 16:51 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915: Double check bumping after the spinlock Patchwork
2020-02-20 17:18 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-02-22 22:43 ` [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=6c039f03-0247-7cef-bcd1-48e366cd31da@intel.com \
--to=matthew.auld@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 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.