MMIO and gcc re-ordering issue
haavard.skinnemoen at atmel.com
Fri May 30 18:27:06 EST 2008
On Fri, 30 May 2008 17:24:27 +1000
Benjamin Herrenschmidt <benh at kernel.crashing.org> wrote:
> On Fri, 2008-05-30 at 08:07 +0200, Haavard Skinnemoen wrote:
> > I think the drivers I've written have the necessary barriers (or dma
> > ops with implicit barriers) that they don't actually depend on any
> > DMA vs. MMIO ordering guarantees. I hope MMIO vs. MMIO ordering is
> > guaranteed though?
> Only to the same address I'd say.
Right, I sort of suspected that.
Now, I'm pretty sure the architectures that can actually run those
drivers (ARM9 and AVR32 AP7) provide stronger guarantees than that, and
I suspect the same is true on most other embedded architectures that
use __raw_* in their drivers. So I don't think adding barriers is the
right thing to do because they won't do anything useful in practice, so
it's hard to tell whether they are used "correctly". And it will hurt
performance at least on AVR32 since wmb() evaluates to a "sync"
instruction, which flushes the write buffer to RAM. Since MMIO writes
are unbuffered, that's pure overhead.
Maybe we need another interface that does not do byteswapping but
provides stronger ordering guarantees?
More information about the Linuxppc-dev