From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org,
Akash Goel <akash.goel@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Unconditionally flush writes before execbuffer
Date: Mon, 11 May 2015 12:34:37 +0200 [thread overview]
Message-ID: <20150511103437.GA15256@phenom.ffwll.local> (raw)
In-Reply-To: <1431330696-15379-1-git-send-email-chris@chris-wilson.co.uk>
On Mon, May 11, 2015 at 08:51:36AM +0100, Chris Wilson wrote:
> With the advent of mmap(wc), we have a path to write directly into
> active GPU buffers. When combined with async updates (i.e. avoiding the
> explicit domain management along with the memory barriers and GPU
> stalls) we start to see the GPU read the wrong values from memory - i.e.
> we have insufficient memory barriers along the execbuffer path. Writes
> through the GTT should have been naturally serialised with execution
> through the GTT as well and so the impact only seems to be from the WC
> paths.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Akash Goel <akash.goel@intel.com>
> Cc: stable@vger.kernel.org
Do we have a nasty igt for this? Bugzilla?
-Daniel
> ---
> drivers/gpu/drm/i915/i915_gem_execbuffer.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem_execbuffer.c b/drivers/gpu/drm/i915/i915_gem_execbuffer.c
> index 650ae02484b0..4f97275ba799 100644
> --- a/drivers/gpu/drm/i915/i915_gem_execbuffer.c
> +++ b/drivers/gpu/drm/i915/i915_gem_execbuffer.c
> @@ -1127,8 +1127,12 @@ i915_gem_execbuffer_move_to_gpu(struct intel_engine_cs *ring,
> if (flush_chipset)
> i915_gem_chipset_flush(ring->dev);
>
> - if (flush_domains & I915_GEM_DOMAIN_GTT)
> - wmb();
> + /* Unconditionally flush out writes to memory as the user may be
> + * doing asynchronous streaming writes to active buffers (i.e.
> + * lazy domain management to avoid serialisation) directly into
> + * the physical pages and so not naturally serialised by the GTT.
> + */
> + wmb();
>
> /* Unconditionally invalidate gpu caches and ensure that we do flush
> * any residual writes from the previous batch.
> --
> 2.1.4
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-05-11 10:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 7:51 [PATCH] drm/i915: Unconditionally flush writes before execbuffer Chris Wilson
2015-05-11 10:34 ` Daniel Vetter [this message]
2015-05-11 10:37 ` [Intel-gfx] " Chris Wilson
2015-05-11 15:25 ` Chris Wilson
2015-05-12 10:19 ` [Intel-gfx] " Chris Wilson
2015-05-19 14:41 ` Chris Wilson
2015-05-21 13:00 ` Chris Wilson
2015-05-21 13:07 ` Daniel Vetter
2015-05-21 13:13 ` Chris Wilson
2015-05-21 14:21 ` Daniel Vetter
2015-05-21 15:22 ` [Intel-gfx] " Chris Wilson
2015-05-21 15:30 ` Daniel Vetter
2015-05-26 8:00 ` Daniel Vetter
2015-05-21 20:29 ` Jesse Barnes
2015-05-14 11:52 ` shuang.he
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=20150511103437.GA15256@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=akash.goel@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.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