On Wed, Feb 17, 2010 at 08:11:35PM +1100, Benjamin Herrenschmidt wrote: > In that case, I would recommend you look at how this is already dealt > with on existing archs such as powerpc, using PG_arch1 in struct page to > keep track of whether a given page is clean for execution and mapping > pages that aren't non-exec so the kernel gets a chance to clean them > once when execution happens. That would be fine if we weren't already using PG_arch_1 for delaying D-cache flushes for pages which aren't mapped, in the same way that Sparc64 does. That doesn't cover this case though - the problem is not I/D cache coherency - the problem has manifested itself as data corruption when userspace reads the page. -- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
