On Mon, Oct 26, 2015 at 11:50 AM, Ganapatrao Kulkarni <gpkulkarni@xxxxxxxxx> wrote: > On Mon, Oct 26, 2015 at 7:14 AM, Ming Lei <ming.lei@xxxxxxxxxxxxx> wrote: >> On Tue, Oct 20, 2015 at 6:45 PM, Ganapatrao Kulkarni >> <gkulkarni@xxxxxxxxxxxxxxxxxx> wrote: >>> Adding numa dt binding support for arm64 based platforms. >>> dt node parsing for numa topology is done using device property >>> proximity and device node distance-map. >>> >>> Reviewed-by: Robert Richter <rrichter@xxxxxxxxxx> >>> Signed-off-by: Ganapatrao Kulkarni <gkulkarni@xxxxxxxxxxxxxxxxxx> >>> --- >>> arch/arm64/Kconfig | 10 ++ >>> arch/arm64/include/asm/numa.h | 10 ++ >>> arch/arm64/kernel/Makefile | 1 + >>> arch/arm64/kernel/of_numa.c | 221 ++++++++++++++++++++++++++++++++++++++++++ >>> arch/arm64/kernel/smp.c | 1 + >>> arch/arm64/mm/numa.c | 10 +- >>> 6 files changed, 252 insertions(+), 1 deletion(-) >>> create mode 100644 arch/arm64/kernel/of_numa.c >>> >>> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig >>> index 0f9cdc7..6cf8d20 100644 >>> --- a/arch/arm64/Kconfig >>> +++ b/arch/arm64/Kconfig >>> @@ -426,6 +426,16 @@ config NUMA >>> local memory controller of the CPU and add some more >>> NUMA awareness to the kernel. >>> >>> +config OF_NUMA >>> + bool "Device Tree NUMA support" >>> + depends on NUMA >>> + depends on OF >>> + default y >>> + help >>> + Enable Device Tree NUMA support. >>> + This enables the numa mapping of cpu, memory, io and >>> + inter node distances using dt bindings. >> >> Enabling the above config option can cause numa_init() warning in >> numa-less arm64 system, please see the following report: > this is taken care. which version are you using? V5. > >> >> https://bugs.launchpad.net/bugs/1509221 >> >> Thanks, > > Thanks > Ganapat > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
