On Mon, 3 Sep 2018 at 16:04, Chris Wilson 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
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
---