powerpc/mm/book3s64: Fix build error with SPARSEMEM disabled
PATCH 1/2 powerpc/mm/book3s64: Fix build error with SPARSEMEM disabled
With CONFIG_SPARSEMEM disabled the below kernel build error is observed.
arch/powerpc/mm/init_64.c:477:38: error: use of undeclared identifier 'SECTION_SIZE_BITS'
CONFIG_MEMORY_HOTPLUG depends on CONFIG_SPARSEMEM and it is more clear to describe the code dependency in terms of MEMORY_HOTPLUG. Outside memory hotplug the kernel uses memory_block_size for kernel directmap. Instead of depending on SECTION_SIZE_BITS to compute the direct map page size, add a new #define which defaults to 16M(same as existing SECTION_SIZE)
--- arch/powerpc/mm/init_64.c | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-)
arch/powerpc/mm/init_64.c +15 -4
@@ -472,12 +472,23 @@ static int __init dt_scan_mmu_pid_width(unsigned long node,return 1 ; } +/* +* Outside hotplug the kernel uses this value to map the kernel direct map +* with radix. To be compatible with older kernels, let's keep this value +* as 16M which is also SECTION_SIZE with SPARSEMEM. We can ideally map +* things with 1GB size in the case where we don't support hotplug. +*/ +#ifndef CONFIG_MEMORY_HOTPLUG +#define DEFAULT_MEMORY_BLOCK_SIZE SZ_16M +#else +#define DEFAULT_MEMORY_BLOCK_SIZE MIN_MEMORY_BLOCK_SIZE +#endif +static void update_memory_block_size (unsigned long *block_size,unsigned long mem_size) { -unsigned long section_size =1UL <<SECTION_SIZE_BITS ; - -for (; *block_size > section_size; *block_size >>=2 ) { +unsigned long min_memory_block_size =DEFAULT_MEMORY_BLOCK_SIZE ; +for (; *block_size > min_memory_block_size; *block_size >>=2 ) {if ((mem_size & *block_size) ==0 )break ; }
@@ -507,7 +518,7 @@ static int __init probe_memory_block_size(unsigned long node, const char *uname,/* * Nothing in the device tree */ - *block_size =MIN_MEMORY_BLOCK_SIZE ; + *block_size =DEFAULT_MEMORY_BLOCK_SIZE ; else *block_size =of_read_number (prop, dt_root_size_cells);/*
Signature · 1 line
2.41.0
PATCH 2/2 powerpc/mm/book3s64: Use 256M as the upper limit with coherent device memory attached
commit 4d15721177d5 ("powerpc/mm: Cleanup memory block size probing") used 256MB as the memory block size when we have ibm,coherent-device-memory device tree node present. Instead of returning with 256MB memory block size, continue to check the rest of the memory regions and make sure we can still map them using a 256MB memory block size.
--- arch/powerpc/mm/init_64.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
arch/powerpc/mm/init_64.c +6 -2
@@ -569,8 +569,12 @@ static int __init probe_memory_block_size(unsigned long node, const char *uname,*/ compatible =of_get_flat_dt_prop (node,"compatible" ,NULL );if (compatible && !strcmp (compatible,"ibm,coherent-device-memory" )) { - *block_size =SZ_256M ; -return 1 ; +if (*block_size >SZ_256M ) + *block_size =SZ_256M ; +/* +* We keep 256M as the upper limit with GPU present. +*/ +return 0 ; } }/* continue looking for other memory device types */
Signature · 1 line
2.41.0
Quoted 11 lines · Aneesh Kumar K.V
With
CONFIG_SPARSEMEMdisabled the below kernel build error is observed.
arch/powerpc/mm/init_64.c:477:38: error: use of undeclared identifier 'SECTION_SIZE_BITS'
CONFIG_MEMORY_HOTPLUGdepends onCONFIG_SPARSEMEMand it is more clear to describe the code dependency in terms ofMEMORY_HOTPLUG. Outside memory hotplug the kernel usesmemory_block_sizefor kernel directmap. Instead of depending onSECTION_SIZE_BITSto compute the direct map page size, add a new #define which defaults to 16M(same as existingSECTION_SIZE)
Quoted 46 lines
Fixes 4d15721177d5 ("powerpc/mm: Cleanup memory block size probing")Signed-off-by Aneesh Kumar K.V <[email protected]>--- arch/powerpc/mm/init_64.c | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-)arch/powerpc/mm/init_64.c +15
-4@@ -472,12 +472,23 @@ static int __init dt_scan_mmu_pid_width(unsigned long node,return 1 ; } +/* +* Outside hotplug the kernel uses this value to map the kernel direct map +* with radix. To be compatible with older kernels, let's keep this value +* as 16M which is also SECTION_SIZE with SPARSEMEM. We can ideally map +* things with 1GB size in the case where we don't support hotplug. +*/ +#ifndef CONFIG_MEMORY_HOTPLUG +#define DEFAULT_MEMORY_BLOCK_SIZE SZ_16M +#else +#define DEFAULT_MEMORY_BLOCK_SIZE MIN_MEMORY_BLOCK_SIZE +#endif +static void update_memory_block_size (unsigned long *block_size,unsigned long mem_size) { -unsigned long section_size =1UL <<SECTION_SIZE_BITS ; - -for (; *block_size > section_size; *block_size >>=2 ) { +unsigned long min_memory_block_size =DEFAULT_MEMORY_BLOCK_SIZE ; +for (; *block_size > min_memory_block_size; *block_size >>=2 ) {if ((mem_size & *block_size) ==0 )break ; }@@ -507,7 +518,7 @@ static int __init probe_memory_block_size(unsigned long node, const char *uname,/* * Nothing in the device tree */ - *block_size =MIN_MEMORY_BLOCK_SIZE ; + *block_size =DEFAULT_MEMORY_BLOCK_SIZE ; else *block_size =of_read_number (prop, dt_root_size_cells);/*
Michael Ellerman
AppliedQuoted 4 lines · Aneesh Kumar K.V
With
CONFIG_SPARSEMEMdisabled the below kernel build error is observed.
arch/powerpc/mm/init_64.c:477:38: error: use of undeclared identifier 'SECTION_SIZE_BITS'
Quoted 8 lines
CONFIG_MEMORY_HOTPLUGdepends onCONFIG_SPARSEMEMand it is more clear to describe the code dependency in terms ofMEMORY_HOTPLUG. Outside memory hotplug the kernel usesmemory_block_sizefor kernel directmap. Instead of depending onSECTION_SIZE_BITSto compute the direct map page size, add a new #define which defaults to 16M(same as existingSECTION_SIZE)[...]
Applied to powerpc/next.
[1/2] powerpc/mm/book3s64: Fix build error with SPARSEMEM disabled
https://git.kernel.org/powerpc/c/f1424755db913c5971686537381588261cdfd1ee [2/2] powerpc/mm/book3s64: Use 256M as the upper limit with coherent device memory attached https://git.kernel.org/powerpc/c/4c33bf147249ebbf3dded016996a8a24c5737254
cheers