mm, memory_hotplug: provide a more generic restrictions for memory hotplug
arch_add_memory, __add_pages take a want_memblock which controls whether the newly added memory should get the sysfs memblock user API (e.g. ZONE_DEVICE users do not want/need this interface). Some callers even want to control where do we allocate the memmap from by configuring altmap. Add a more generic hotplug context for arch_add_memory and __add_pages. struct mhp_restrictions contains flags which contains additional features to be enabled by the memory hotplug (MHP_MEMBLOCK_API currently) and altmap for alternative memmap allocator. This patch shouldn't introduce any functional change. [akpm@linux-foundation.org: build fix] Link: http://lkml.kernel.org/r/20190408082633.2864-3-osalvador@suse.de Signed-off-by:Michal Hocko <mhocko@suse.com> Signed-off-by:
Oscar Salvador <osalvador@suse.de> Cc: Dan Williams <dan.j.williams@intel.com> Cc: David Hildenbrand <david@redhat.com> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
Linus Torvalds <torvalds@linux-foundation.org>
Showing
- arch/arm64/mm/mmu.c 3 additions, 3 deletionsarch/arm64/mm/mmu.c
- arch/ia64/mm/init.c 3 additions, 3 deletionsarch/ia64/mm/init.c
- arch/powerpc/mm/mem.c 3 additions, 3 deletionsarch/powerpc/mm/mem.c
- arch/s390/mm/init.c 3 additions, 3 deletionsarch/s390/mm/init.c
- arch/sh/mm/init.c 3 additions, 3 deletionsarch/sh/mm/init.c
- arch/x86/mm/init_32.c 3 additions, 3 deletionsarch/x86/mm/init_32.c
- arch/x86/mm/init_64.c 5 additions, 5 deletionsarch/x86/mm/init_64.c
- include/linux/memory_hotplug.h 24 additions, 7 deletionsinclude/linux/memory_hotplug.h
- kernel/memremap.c 9 additions, 3 deletionskernel/memremap.c
- mm/memory_hotplug.c 7 additions, 4 deletionsmm/memory_hotplug.c
Loading
Please register or sign in to comment