summaryrefslogtreecommitdiff
path: root/lib/Kconfig
diff options
context:
space:
mode:
authorCliff Wickman <cpw@sgi.com>2013-02-22 16:35:58 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2013-02-23 17:50:23 -0800
commitfa794199e36a13063913e75487001b3038316e51 (patch)
tree2b3b250e0706e40978a6b8611b49f276517271aa /lib/Kconfig
parent240aadeedc4a89fc44623f8ce4ca46bda73db07e (diff)
downloadlinux-3.10-fa794199e36a13063913e75487001b3038316e51.tar.gz
linux-3.10-fa794199e36a13063913e75487001b3038316e51.tar.bz2
linux-3.10-fa794199e36a13063913e75487001b3038316e51.zip
mm: export mmu notifier invalidates
We at SGI have a need to address some very high physical address ranges with our GRU (global reference unit), sometimes across partitioned machine boundaries and sometimes with larger addresses than the cpu supports. We do this with the aid of our own 'extended vma' module which mimics the vma. When something (either unmap or exit) frees an 'extended vma' we use the mmu notifiers to clean them up. We had been able to mimic the functions __mmu_notifier_invalidate_range_start() and __mmu_notifier_invalidate_range_end() by locking the per-mm lock and walking the per-mm notifier list. But with the change to a global srcu lock (static in mmu_notifier.c) we can no longer do that. Our module has no access to that lock. So we request that these two functions be exported. Signed-off-by: Cliff Wickman <cpw@sgi.com> Acked-by: Robin Holt <holt@sgi.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'lib/Kconfig')
0 files changed, 0 insertions, 0 deletions