Re: [PATCH] x86: Add an explicit barrier() to clflushopt()
From: Linus Torvalds
Date: Wed Jan 13 2016 - 13:45:44 EST
On Wed, Jan 13, 2016 at 4:34 AM, Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> wrote:
> Forgive me for being dense, but if we overwrite the GPU data in the
> backing struct page with the cacheline from the CPU, how do we see the
> results from the GPU afterwards?
Hmm. Good point.
Ok, all the symptoms just say "writes from GPU are delayed and out of order".
Do you have access to the GPU hardware people?
I thought that all the modern Intel GPU's are cache-coherent. If this
is some castrated chip where coherence is removed (perhaps because it
is not working? perhaps config setting?) maybe it needs some extra
ghardware setting to make the GPU "flush" operation actually do
something. In a cache-coherent model, a flush could/should be a noop,
so maybe the hardware is set for that kind of "flush does nothing"
Or maybe the GPU is just a buggy pile of crap.