Messages in this thread Patch in this message | | | From | guoren@kernel ... | Subject | [PATCH 29/29] csky: Fixup pfn_valid error with wrong max_mapnr | Date | Thu, 21 Jan 2021 14:53:49 +0800 |
| |
From: Guo Ren <guoren@linux.alibaba.com>
The max_mapnr is the number of PFNs, not absolute PFN offset.
Signed-off-by: Guo Ren <guoren@linux.alibaba.com> --- arch/csky/mm/init.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/csky/mm/init.c b/arch/csky/mm/init.c index 03970f4408f5..81e4e5e78f38 100644 --- a/arch/csky/mm/init.c +++ b/arch/csky/mm/init.c @@ -86,9 +86,9 @@ void __init mem_init(void) #ifdef CONFIG_HIGHMEM unsigned long tmp; - set_max_mapnr(highend_pfn); + set_max_mapnr(highend_pfn - ARCH_PFN_OFFSET); #else - set_max_mapnr(max_low_pfn); + set_max_mapnr(max_low_pfn - ARCH_PFN_OFFSET); #endif high_memory = (void *) __va(max_low_pfn << PAGE_SHIFT); -- 2.17.1
| |