Messages in this thread | | | Date | Tue, 10 Jan 2006 01:18:44 -0800 | From | Andrew Morton <> | Subject | Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32 |
| |
"Bryan O'Sullivan" <bos@pathscale.com> wrote: > > This arch-independent routine copies data to a memory-mapped I/O region, > using 32-bit accesses. It does not guarantee access ordering, nor does > it perform a memory barrier afterwards. This style of access is required > by some devices.
Not providing orderingor barriers makes this a rather risky thing to export - people might use it, find their driver "works" on one architecture, but fails on another.
I guess the "__" is a decent warning of this, and the patch anticipates a higher-level raw_memcpy_toio32() which implements those things, yes?
How come __raw_memcpy_toio32() is inlined? - 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/
| |