x86, NUMA: Drop @start/last_pfn from initmem_init()
initmem_init() extensively accesses and modifies global data
structures and the parameters aren't even followed depending on which
path is being used. Drop @start/last_pfn and let it deal with
@max_pfn directly. This is in preparation for further NUMA init
cleanups.
- v2: x86-32 initmem_init() weren't updated breaking 32bit builds.
Fixed. Found by Yinghai.
Signed-off-by:
Tejun Heo <tj@kernel.org>
Cc: Yinghai Lu <yinghai@kernel.org>
Cc: Brian Gerst <brgerst@gmail.com>
Cc: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Shaohui Zheng <shaohui.zheng@intel.com>
Cc: David Rientjes <rientjes@google.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: H. Peter Anvin <hpa@linux.intel.com>
Showing
- arch/x86/include/asm/page_types.h 1 addition, 2 deletionsarch/x86/include/asm/page_types.h
- arch/x86/kernel/setup.c 1 addition, 1 deletionarch/x86/kernel/setup.c
- arch/x86/mm/init_32.c 1 addition, 2 deletionsarch/x86/mm/init_32.c
- arch/x86/mm/init_64.c 2 additions, 3 deletionsarch/x86/mm/init_64.c
- arch/x86/mm/numa_32.c 1 addition, 2 deletionsarch/x86/mm/numa_32.c
- arch/x86/mm/numa_64.c 8 additions, 13 deletionsarch/x86/mm/numa_64.c
Loading
Please register or sign in to comment