Re: [PATCH] mm, proc: Make the task_mmu walk_page_range() limit in clear_refs_write() obvious

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Aug 31, 2016 at 04:03:12PM +0100, James Morse wrote:
> Trying to walk all of virtual memory requires architecture specific
> knowledge. On x86_64, addresses must be sign extended from bit 48,
> whereas on arm64 the top VA_BITS of address space have their own set
> of page tables.
> 
> clear_refs_write() calls walk_page_range() on the range 0 to ~0UL, it
> provides a test_walk() callback that only expects to be walking over
> VMAs. Currently walk_pmd_range() will skip memory regions that don't
> have a VMA, reporting them as a hole.
> 
> As this call only expects to walk user address space, make it walk
> 0 to  'highest_vm_end'.
> 
> Signed-off-by: James Morse <james.morse@xxxxxxx>
> Cc: Naoya Horiguchi <n-horiguchi@xxxxxxxxxxxxx>

Makes sense to me.

Acked-by: Naoya Horiguchi <n-horiguchi@xxxxxxxxxxxxx>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]