mm: Move change_prot_numa outside CONFIG_ARCH_USES_NUMA_PROT_NONE
authorAneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Thu, 5 Dec 2013 18:38:22 +0000 (00:08 +0530)
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>
Mon, 9 Dec 2013 00:40:23 +0000 (11:40 +1100)
commit5877231f646bbd6d1d545e7af83aaa6e6b746013
treed0ca877cb929b73087aafa19ca884409391f0ebc
parent2c49195b6aedd21ff1cd1e095fab9866fba3411b
mm: Move change_prot_numa outside CONFIG_ARCH_USES_NUMA_PROT_NONE

change_prot_numa should work even if _PAGE_NUMA != _PAGE_PROTNONE.
On archs like ppc64 that don't use _PAGE_PROTNONE and also have
a separate page table outside linux pagetable, we just need to
make sure that when calling change_prot_numa we flush the
hardware page table entry so that next page access  result in a numa
fault.

We still need to make sure we use the numa faulting logic only
when CONFIG_NUMA_BALANCING is set. This implies the migrate-on-fault
(Lazy migration) via mbind will only work if CONFIG_NUMA_BALANCING
is set.

Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Reviewed-by: Rik van Riel <riel@redhat.com>
Acked-by: Mel Gorman <mgorman@suse.de>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
include/linux/mm.h
mm/mempolicy.c