From: Matthew Auld <matthew.william.auld@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Fix up FORCE_GPU_RELOC (debug) to flush CPU write domains
Date: Mon, 3 Sep 2018 17:49:10 +0100 [thread overview]
Message-ID: <CAM0jSHP+DXqYPrbsop7rxSpDHJHQYGuPa17PUwScCs_kH2mTOg@mail.gmail.com> (raw)
In-Reply-To: <20180903150216.19965-1-chris@chris-wilson.co.uk>
On Mon, 3 Sep 2018 at 16:04, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>
> We currently assert that if the target is in a CPU write domain, we use
> a CPU path rather than the GPU path. However, we have a debug override
> to force the GPU path and that unfortunately hits the assert. Include
> the async clflush under the debug option.
>
> 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
prev parent reply other threads:[~2018-09-03 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 15:02 [PATCH] drm/i915: Fix up FORCE_GPU_RELOC (debug) to flush CPU write domains Chris Wilson
2018-09-03 15:31 ` ✗ Fi.CI.BAT: failure for " Patchwork
2018-09-03 16:49 ` Matthew Auld [this message]
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=CAM0jSHP+DXqYPrbsop7rxSpDHJHQYGuPa17PUwScCs_kH2mTOg@mail.gmail.com \
--to=matthew.william.auld@gmail.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.