From: James Bottomley <jejb@xxxxxxxxxxxxxxx> After looking through all the feedback, here's the next version of the patch. This one is based on a new api: flush/invalidate_kernel_vmap_range() making it clear that the fs/driver is the entity managing the vmaps ... it also drops the block inputs because coherency management is now the responsibility of the user. The xfs interface is nicely simplified with this approach. Could someone check this on arm and sh? Thanks, James --- James Bottomley (5): mm: add coherence API for DMA to vmalloc/vmap areas parisc: add mm API for DMA to vmalloc/vmap areas arm: add mm API for DMA to vmalloc/vmap areas sh: add mm API for DMA to vmalloc/vmap areas xfs: fix xfs to work with Virtually Indexed architectures Documentation/cachetlb.txt | 27 +++++++++++++++++++++++++++ arch/arm/include/asm/cacheflush.h | 10 ++++++++++ arch/parisc/include/asm/cacheflush.h | 12 ++++++++++++ arch/sh/include/asm/cacheflush.h | 8 ++++++++ fs/xfs/linux-2.6/xfs_buf.c | 20 +++++++++++++++++++- include/linux/highmem.h | 6 ++++++ 6 files changed, 82 insertions(+), 1 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
