Direct page mapping in bottom-up way will allocate memory from low address for page structures in a range, which is the *bottom*, not the *end*.
Signed-off-by: Cao jin <jojin...@gmail.com> --- arch/x86/mm/init.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c index e26f5c5c6565..bc2f871c75f1 100644 --- a/arch/x86/mm/init.c +++ b/arch/x86/mm/init.c @@ -663,7 +663,7 @@ static void __init memory_map_bottom_up(unsigned long map_start, /* * We start from the bottom (@map_start) and go to the top (@map_end). * The memblock_find_in_range() gets us a block of RAM from the - * end of RAM in [min_pfn_mapped, max_pfn_mapped) used as new pages + * bottom of RAM in [min_pfn_mapped, max_pfn_mapped) used as new pages * for page table. */ while (start < map_end) { -- 2.30.1