x86/mm: Introduce CONFIG_NUMA_KEEP_MEMINFO
authorDan Williams <dan.j.williams@intel.com>
Sun, 16 Feb 2020 20:01:04 +0000 (12:01 -0800)
committerDan Williams <dan.j.williams@intel.com>
Mon, 17 Feb 2020 18:49:06 +0000 (10:49 -0800)
commit1e5d8e1e47afde23e3249aed25d7d124feff5c1c
tree59913aad124869f0a39a972a025d9331865e7383
parent575e23b6e13c5f575a65144579a233b76f5ca86b
x86/mm: Introduce CONFIG_NUMA_KEEP_MEMINFO

Currently x86 numa_meminfo is marked __initdata in the
CONFIG_MEMORY_HOTPLUG=n case. In support of a new facility to allow
drivers to map reserved memory to a 'target_node'
(phys_to_target_node()), add support for removing the __initdata
designation for those users. Both memory hotplug and
phys_to_target_node() users select CONFIG_NUMA_KEEP_MEMINFO to tell the
arch to maintain its physical address to NUMA mapping infrastructure
post init.

Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Borislav Petkov <bp@alien8.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: <x86@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: David Hildenbrand <david@redhat.com>
Cc: Michal Hocko <mhocko@suse.com>
Reviewed-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/r/158188326422.894464.15742054998046628934.stgit@dwillia2-desk3.amr.corp.intel.com
arch/x86/mm/numa.c
include/linux/numa.h
mm/Kconfig