Messages in this thread | ![/](/images/icornerl.gif) | | Subject | Re: [PATCH] Document Linux's memory barriers | From | Alan Cox <> | Date | Wed, 08 Mar 2006 22:05:14 +0000 |
| |
On Iau, 2006-03-09 at 08:49 +1100, Paul Mackerras wrote: > If the device accesses to memory are in response to an MMIO store, > then the code needs an explicit wmb() between the memory stores and > the MMIO store. Disabling interrupts isn't going to help here because > the device doesn't see the CPU interrupt enable state.
Interrupts are themselves entirely asynchronous anyway. The following can occur on SMP Pentium-PIII.
Device Raise IRQ
CPU writel(MASK_IRQ, &dev->ctrl); readl(&dev->ctrl);
IRQ arrives
CPU specific IRQ masking is synchronous, but IRQ delivery is not, including IPI delivery (which is asynchronous and not guaranteed to occur only once per IPI but can be replayed in obscure cases on x86).
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |