Re: mmu_notifier: invalidate_range for move_page_tables

2008-01-31 Thread Christoph Lameter
On Thu, 31 Jan 2008, Robin Holt wrote: > On Thu, Jan 31, 2008 at 05:57:25PM -0800, Christoph Lameter wrote: > > Move page tables also needs to invalidate the external references > > and hold new references off while moving page table entries. > > I must admit to not having spent any time thinking

Re: mmu_notifier: invalidate_range for move_page_tables

2008-01-31 Thread Robin Holt
On Thu, Jan 31, 2008 at 05:57:25PM -0800, Christoph Lameter wrote: > Move page tables also needs to invalidate the external references > and hold new references off while moving page table entries. I must admit to not having spent any time thinking about this, but aren't we moving the entries from

mmu_notifier: invalidate_range for move_page_tables

2008-01-31 Thread Christoph Lameter
mmu_notifier: Provide invalidate_range for move_page_tables Move page tables also needs to invalidate the external references and hold new references off while moving page table entries. This is already guaranteed by holding a writelock on mmap_sem for get_user_pages() but follow_page() is not su