m68k/mm: switch from DISCONTIGMEM to SPARSEMEM
v3 cover m68k/mm: switch from DISCONTIGMEM to SPARSEMEM
From: Mike Rapoport <[email protected]>
Hi,
It took me a while to get back to this, but better late than never :)
These patches replace DISCONTIGMEM with SPARSEMEM on m68k for systems with !SINGLE_MEMORY_CHUNK set.
With SPARSEMEM there is a single node for the entire physical memory and to cope with holes in the physical address space it is divided to sections of several megabytes.
Each section has it's own memory map which size depends on actual populated memory.
The section size of 16M was chosen pretty much arbitrarily as I couldn't find specs for systems with e.g. Zorro memory extensions.
Yet, we cannot use smaller sections and still be able to address the entire 4G of the physical memory because the section number is encoded in the page flags and there are only 8 bits available.
For systems with several small memory chunks and with small (several megs) holes between them, 16M section size would cause wasted parts in the memory map and it is desirable to allow smaller section size at the expense of limiting the addressable memory.
I've hesitated between adding Kconfig option as Finn suggested [1] and other options like SPARSE_VMEMMAP or ARCH_HAS_HOLES_MEMORYMODEL. In the end, I think Kconfig is the simplest one from the implementation point of view and would work fine for people that run mainline kernels on vintage hardware.
For the systems with ST-RAM and FastRAM, the switch to SPARSEMEM does not change the limitation that if the kernel is loaded into the FastRam the ST-RAM remains unmapped. It only ensures that if the kernel is loaded in ST-RAM, the memory map is allocated from high physical addresses and then atari/stram.c is able to reserve the frame buffer memory. If the kernel is loaded to FastRAM, the ST-RAM remains unmapped as with DISCONTIGMEM and the atari/stram.c maps it as IOMEM.
[1] https://marc.info/?l=linux-m68k&m=156309170500921&w=2
v3 changes:
* rebase on the current upstream
* alias ARCH_PFN_BASE to m68k_memory[0].addr
* add configuration option to allow two variants of section size.
v2 changes:
* rebase on the current upstream
* make ColdFire MMU select SINGLE_MEMORY_CHUNK in Kconfig.cpu
Mike Rapoport (3):
m68k/mm: make node data and node setup depend on CONFIG_DISCONTIGMEM m68k/mm: enable use of generic memory_model.h for !DISCONTIGMEM m68k/mm: switch from DISCONTIGMEM to SPARSEMEM
arch/m68k/Kconfig.cpu | 14 ++++++-- arch/m68k/include/asm/page.h | 2 ++ arch/m68k/include/asm/page_mm.h | 6 +++- arch/m68k/include/asm/sparsemem.h | 8 +++++ arch/m68k/include/asm/virtconvert.h | 2 +- arch/m68k/mm/init.c | 8 ++--- arch/m68k/mm/motorola.c | 64 ++++++++++++++++++++++++++++++------- 7 files changed, 84 insertions(+), 20 deletions(-) create mode 100644 arch/m68k/include/asm/sparsemem.h
Signature · 20 lines
2.7.4 *** BLURB HERE *** Mike Rapoport (3): m68k/mm: make node data and node setup depend on CONFIG_DISCONTIGMEM m68k/mm: enable use of generic memory_model.h for !DISCONTIGMEM m68k/mm: switch from DISCONTIGMEM to SPARSEMEM arch/m68k/Kconfig.cpu | 23 ++++++++++++++--- arch/m68k/include/asm/page.h | 2 ++ arch/m68k/include/asm/page_mm.h | 7 +++++- arch/m68k/include/asm/virtconvert.h | 2 +- arch/m68k/mm/init.c | 8 +++--- arch/m68k/mm/motorola.c | 39 ++++++++++++++++++++++++++--- 6 files changed, 69 insertions(+), 12 deletions(-) -- 2.26.2
PATCH v3 1/3 m68k/mm: make node data and node setup depend on CONFIG_DISCONTIGMEM
From: Mike Rapoport <[email protected]>
The pg_data_t node structures and their initialization currently depends on !CONFIG_SINGLE_MEMORY_CHUNK. Since their are required only for DISCONTIGMEM make this dependency explicit and replace usage of CONFIG_SINGLE_MEMORY_CHUNK with CONFIG_DISCONTIGMEM where appropriate.
The CONFIG_SINGLE_MEMORY_CHUNK was implicitly disabled on the ColdFire MMU variant, although it always presumed a single memory bank. As there is no actual need for DISCONTIGMEM in this case, make sure that ColdFire MMU systems set CONFIG_SINGLE_MEMORY_CHUNK to 'y'.
--- arch/m68k/Kconfig.cpu | 6 +++--- arch/m68k/include/asm/page_mm.h | 2 +- arch/m68k/mm/init.c | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-)
arch/m68k/Kconfig.cpu +3 -3
@@ -20,6 +20,7 @@ choice config M68KCLASSIC bool "Classic M68K CPU family support" + select NEED_MULTIPLE_NODES if DISCONTIGMEM config COLDFIRE bool "Coldfire CPU family support"
@@ -373,8 +374,7 @@ config RMW_INSNS config SINGLE_MEMORY_CHUNK bool "Use one physical chunk of memory only" if ADVANCED && !SUN3 depends on MMU - default y if SUN3 - select NEED_MULTIPLE_NODES + default y if SUN3 || MMU_COLDFIRE help Ignore all but the first contiguous chunk of physical memory for VM purposes. This will save a few bytes kernel size and may speed up
@@ -406,7 +406,7 @@ config M68K_L2_CACHE config NODES_SHIFT int default "3" - depends on !SINGLE_MEMORY_CHUNK + depends on DISCONTIGMEM config CPU_HAS_NO_BITFIELDS bool
arch/m68k/include/asm/page_mm.h +1 -1
@@ -126,7 +126,7 @@ static inline void *__va(unsigned long x)extern int m68k_virt_to_node_shift; -#ifdef CONFIG_SINGLE_MEMORY_CHUNK +#ifndef CONFIG_DISCONTIGMEM #define __virt_to_node (addr) (&pg_data_map[0])#else extern struct pglist_data *pg_data_table[];
arch/m68k/mm/init.c +2 -2
@@ -47,14 +47,14 @@ EXPORT_SYMBOL(pg_data_map);int m68k_virt_to_node_shift; -#ifndef CONFIG_SINGLE_MEMORY_CHUNK +#ifdef CONFIG_DISCONTIGMEM pg_data_t *pg_data_table[65 ];EXPORT_SYMBOL (pg_data_table);#endif void __init m68k_setup_node (int node) { -#ifndef CONFIG_SINGLE_MEMORY_CHUNK +#ifdef CONFIG_DISCONTIGMEM struct m68k_mem_info *info = m68k_memory + node;int i, end;
Signature · 1 line
2.26.2
PATCH v3 2/3 m68k/mm: enable use of generic memory_model.h for !DISCONTIGMEM
In reply to Mike RapoportFrom: Mike Rapoport <[email protected]>
The pg_data_map and pg_data_table arrays as well as page_to_pfn() and pfn_to_page() are required only for DISCONTIGMEM. Other memory models can use the generic definitions in asm-generic/memory_model.h.
--- arch/m68k/include/asm/page.h | 2 ++ arch/m68k/include/asm/page_mm.h | 5 +++++ arch/m68k/include/asm/virtconvert.h | 2 +- arch/m68k/mm/init.c | 6 +++--- 4 files changed, 11 insertions(+), 4 deletions(-)
arch/m68k/include/asm/page.h +2 -0
@@ -62,8 +62,10 @@ extern unsigned long _ramend;#include <asm/page_no.h> #endif +#ifdef CONFIG_DISCONTIGMEM #define __phys_to_pfn (paddr) ((unsigned long)((paddr) >> PAGE_SHIFT))#define __pfn_to_phys (pfn) PFN_PHYS(pfn) +#endif #include <asm-generic/getorder.h>
arch/m68k/include/asm/page_mm.h +5 -0
@@ -153,6 +153,7 @@ static inline __attribute_const__ int __virt_to_node_shift(void)pfn_to_virt (page_to_pfn (page)); \ }) +#ifdef CONFIG_DISCONTIGMEM #define pfn_to_page (pfn) ({ \ unsigned long __pfn = (pfn); \ struct pglist_data *pgdat; \
@@ -165,6 +166,10 @@ static inline __attribute_const__ int __virt_to_node_shift(void) pgdat = &pg_data_map[page_to_nid (__p)]; \ ((__p) - pgdat->node_mem_map) + pgdat->node_start_pfn; \ }) +#else +#define ARCH_PFN_OFFSET (m68k_memory[0].addr) +#include <asm-generic/memory_model.h> +#endif #define virt_addr_valid (kaddr) ((void *)(kaddr) >= (void *)PAGE_OFFSET && (void *)(kaddr) < high_memory)#define pfn_valid (pfn) virt_addr_valid(pfn_to_virt(pfn))
arch/m68k/include/asm/virtconvert.h +1 -1
@@ -31,7 +31,7 @@ static inline void *phys_to_virt(unsigned long address)/* Permanent address of a page. */ #if defined(CONFIG_MMU ) && defined(CONFIG_SINGLE_MEMORY_CHUNK )#define page_to_phys (page) \ - __pa(PAGE_OFFSET + (((page) - pg_data_map[0].node_mem_map) << PAGE_SHIFT)) + __pa(PAGE_OFFSET + (((page) - mem_map) << PAGE_SHIFT))#else #define page_to_phys (page) (page_to_pfn(page) << PAGE_SHIFT)#endif
arch/m68k/mm/init.c +3 -3
@@ -42,12 +42,12 @@ EXPORT_SYMBOL(empty_zero_page);#ifdef CONFIG_MMU -pg_data_t pg_data_map[MAX_NUMNODES ]; -EXPORT_SYMBOL (pg_data_map); -int m68k_virt_to_node_shift;#ifdef CONFIG_DISCONTIGMEM +pg_data_t pg_data_map[MAX_NUMNODES ]; +EXPORT_SYMBOL (pg_data_map); +pg_data_t *pg_data_table[65 ];EXPORT_SYMBOL (pg_data_table);#endif
Signature · 1 line
2.26.2
PATCH v3 3/3 m68k/mm: switch from DISCONTIGMEM to SPARSEMEM
In reply to Mike RapoportFrom: Mike Rapoport <[email protected]>
Enable SPARSEMEM support for systems with !SINGLE_MEMORY_CHUNK. With SPARSEMEM there is a single node for the entire physical memory and to cope with holes in the physical address space it is divided to sections of up to 4M or 16M, depending on CONFIG_MEMORY_LIMIT_1G.
Each section has it's own memory map which size depends on actual populated memory.
The DISCONTIGMEM is marked BROKEN and will be removed in a couple of releases.
--- arch/m68k/Kconfig.cpu | 17 +++++++++++++++++ arch/m68k/mm/motorola.c | 39 ++++++++++++++++++++++++++++++++++++--- 2 files changed, 53 insertions(+), 3 deletions(-)
arch/m68k/Kconfig.cpu +17 -0
@@ -21,6 +21,7 @@ choice config M68KCLASSIC bool "Classic M68K CPU family support" select NEED_MULTIPLE_NODES if DISCONTIGMEM + select SPARSEMEM_STATIC if SPARSEMEM config COLDFIRE bool "Coldfire CPU family support"
@@ -380,9 +381,25 @@ config SINGLE_MEMORY_CHUNK purposes. This will save a few bytes kernel size and may speed up some operations. Say N if not sure. +config MEMORY_LIMIT_1G + bool "Limit maximal physical memory to 1G" + depends on MMU && !SINGLE_MEMORY_CHUNK + help + Limit the physical memory addressable by the kernel to 1G. + On systems that have several chunks of physical memory and the + hole between these chunks is less than 16M this will prevent + wasting memory on empty memory map. Say N if not sure. + config ARCH_DISCONTIGMEM_ENABLE + def_bool no + depends on BROKEN && MMU && !SINGLE_MEMORY_CHUNK + +config ARCH_SPARSEMEM_ENABLE def_bool MMU && !SINGLE_MEMORY_CHUNK +config HAVE_ARCH_PFN_VALID + def_bool SPARSEMEM + config 060_WRITETHROUGH bool "Use write-through caching for 68060 supervisor accesses" depends on ADVANCED && M68060
arch/m68k/mm/motorola.c +36 -3
@@ -384,6 +384,39 @@ static void __init map_node(int node)#endif } +#ifdef CONFIG_SPARSEMEM +static void mem_model_init (void ) +{ +m68k_setup_node (0 ); +node_set_state (0 ,N_NORMAL_MEMORY ); + +/* +* Make sure the memory map is allocated from top of the +* memory. +* Otherwise for systems with both ST-RAM and FastRam, ST-RAM +* gets filled with the memory map leaving no space for +* framebuffer +*/ +memblock_set_bottom_up (false); +memblocks_present (); +sparse_init (); +memblock_set_bottom_up (true); +} +#else +static void mem_model_init (void ) +{ +unsigned long zones_size[MAX_NR_ZONES ] = {0 , }; +int i; + +for (i =0 ; i < m68k_num_memory; i++) { +m68k_setup_node (i); +if (node_present_pages (i)) +node_set_state (i,N_NORMAL_MEMORY ); + } +} +#endif + +/* * paging_init() continues the virtual memory environment setup which * was begun by the code in arch/head.S.
@@ -449,10 +482,8 @@ void __init paging_init(void)*/ memblock_set_bottom_up (true); -for (i =0 ; i < m68k_num_memory; i++) { -m68k_setup_node (i); +for (i =0 ; i < m68k_num_memory; i++)map_node (i); - }flush_tlb_all ();
@@ -477,6 +508,8 @@ void __init paging_init(void)if (node_present_pages (i))node_set_state (i,N_NORMAL_MEMORY ); +mem_model_init (); + max_zone_pfn[ZONE_DMA ] =memblock_end_of_DRAM ();free_area_init (max_zone_pfn); }
Signature · 1 line
2.26.2
Gentle ping :)
Quoted 89 lines · Mike Rapoport
From: Mike Rapoport <[email protected]>
Hi,
It took me a while to get back to this, but better late than never :)
These patches replace DISCONTIGMEM with SPARSEMEM on m68k for systems with !SINGLE_MEMORY_CHUNK set.
With SPARSEMEM there is a single node for the entire physical memory and to cope with holes in the physical address space it is divided to sections of several megabytes.
Each section has it's own memory map which size depends on actual populated memory.
The section size of 16M was chosen pretty much arbitrarily as I couldn't find specs for systems with e.g. Zorro memory extensions.
Yet, we cannot use smaller sections and still be able to address the entire 4G of the physical memory because the section number is encoded in the page flags and there are only 8 bits available.For systems with several small memory chunks and with small (several megs) holes between them, 16M section size would cause wasted parts in the memory map and it is desirable to allow smaller section size at the expense of limiting the addressable memory.
I've hesitated between adding
Kconfigoption as Finn suggested [1] and other options likeSPARSE_VMEMMAPorARCH_HAS_HOLES_MEMORYMODEL. In the end, I thinkKconfigis the simplest one from the implementation point of view and would work fine for people that run mainline kernels on vintage hardware.For the systems with ST-RAM and FastRAM, the switch to SPARSEMEM does not change the limitation that if the kernel is loaded into the FastRam the ST-RAM remains unmapped. It only ensures that if the kernel is loaded in ST-RAM, the memory map is allocated from high physical addresses and then
atari/stram.cis able to reserve the frame buffer memory. If the kernel is loaded to FastRAM, the ST-RAM remains unmapped as with DISCONTIGMEM and theatari/stram.cmaps it as IOMEM.[1] https://marc.info/?l=linux-m68k&m=156309170500921&w=2
v3 changes:
* rebase on the current upstream
* aliasARCH_PFN_BASEto m68k_memory[0].addr
* add configuration option to allow two variants of section size.v2 changes:
* rebase on the current upstream
* make ColdFire MMU selectSINGLE_MEMORY_CHUNKinKconfig.cpuMike Rapoport (3):
m68k/mm: make node data and node setup depend onCONFIG_DISCONTIGMEMm68k/mm: enable use of genericmemory_model.hfor !DISCONTIGMEM m68k/mm: switch from DISCONTIGMEM to SPARSEMEMarch/m68k/Kconfig.cpu | 14 ++++++-- arch/m68k/include/asm/page.h | 2 ++ arch/m68k/include/asm/page_mm.h | 6 +++- arch/m68k/include/asm/sparsemem.h | 8 +++++ arch/m68k/include/asm/virtconvert.h | 2 +- arch/m68k/mm/init.c | 8 ++--- arch/m68k/mm/motorola.c | 64 ++++++++++++++++++++++++++++++------- 7 files changed, 84 insertions(+), 20 deletions(-) create mode 100644 arch/m68k/include/asm/sparsemem.hSignature · 20 lines
2.7.4 *** BLURB HERE *** Mike Rapoport (3): m68k/mm: make node data and node setup depend on CONFIG_DISCONTIGMEM m68k/mm: enable use of generic memory_model.h for !DISCONTIGMEM m68k/mm: switch from DISCONTIGMEM to SPARSEMEM arch/m68k/Kconfig.cpu | 23 ++++++++++++++--- arch/m68k/include/asm/page.h | 2 ++ arch/m68k/include/asm/page_mm.h | 7 +++++- arch/m68k/include/asm/virtconvert.h | 2 +- arch/m68k/mm/init.c | 8 +++--- arch/m68k/mm/motorola.c | 39 ++++++++++++++++++++++++++--- 6 files changed, 69 insertions(+), 12 deletions(-) -- 2.26.2
Signature · 2 lines
Sincerely yours, Mike.
Hi Mike,
Sorry, I had seen those but didn't get around to test in time.
Applying your patch series to Geert's v5.9-rc1, I get this:
Quoted 10 lines
CC
kernel/bounds.s
CCarch/m68k/kernel/asm-offsets.s
In file included from./include/linux/mmzone.h:19,
from./include/linux/topology.h:33,
from./include/linux/irq.h:19,
from./include/asm-generic/hardirq.h:13, from./arch/m68k/include/generated/asm/hardirq.h:1, from./include/linux/hardirq.h:10,
from./include/linux/interrupt.h:11, from./include/linux/kernel_stat.h:9,
Quoted 8 lines
from
arch/m68k/kernel/asm-offsets.c:16:./include/linux/page-flags-layout.h:28:10: fatal error:asm/sparsemem.h: No such file or directory #include <asm/sparsemem.h>
^~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [arch/m68k/kernel/asm-offsets.s] Error 1
make[1]: *** [prepare0] Error 2
make: *** [__sub-make] Error 2
Your patch announcement blurb hat sparsemem.h listed among the changed files, but none of the three patches stats reference that file. Am I missing a prerequisite here?
Cheers,
Michael
Quoted 92 lines · Mike Rapoport
Gentle ping :)
Quoted 89 lines · Mike Rapoport
From: Mike Rapoport <[email protected]>
Hi,
It took me a while to get back to this, but better late than never :)
These patches replace DISCONTIGMEM with SPARSEMEM on m68k for systems with !SINGLE_MEMORY_CHUNK set.
With SPARSEMEM there is a single node for the entire physical memory and to cope with holes in the physical address space it is divided to sections of several megabytes.
Each section has it's own memory map which size depends on actual populated memory.
The section size of 16M was chosen pretty much arbitrarily as I couldn't find specs for systems with e.g. Zorro memory extensions.
Yet, we cannot use smaller sections and still be able to address the entire 4G of the physical memory because the section number is encoded in the page flags and there are only 8 bits available.For systems with several small memory chunks and with small (several megs) holes between them, 16M section size would cause wasted parts in the memory map and it is desirable to allow smaller section size at the expense of limiting the addressable memory.
I've hesitated between adding
Kconfigoption as Finn suggested [1] and other options likeSPARSE_VMEMMAPorARCH_HAS_HOLES_MEMORYMODEL. In the end, I thinkKconfigis the simplest one from the implementation point of view and would work fine for people that run mainline kernels on vintage hardware.For the systems with ST-RAM and FastRAM, the switch to SPARSEMEM does not change the limitation that if the kernel is loaded into the FastRam the ST-RAM remains unmapped. It only ensures that if the kernel is loaded in ST-RAM, the memory map is allocated from high physical addresses and then
atari/stram.cis able to reserve the frame buffer memory. If the kernel is loaded to FastRAM, the ST-RAM remains unmapped as with DISCONTIGMEM and theatari/stram.cmaps it as IOMEM.[1] https://marc.info/?l=linux-m68k&m=156309170500921&w=2
v3 changes:
* rebase on the current upstream
* aliasARCH_PFN_BASEto m68k_memory[0].addr
* add configuration option to allow two variants of section size.v2 changes:
* rebase on the current upstream
* make ColdFire MMU selectSINGLE_MEMORY_CHUNKinKconfig.cpuMike Rapoport (3):
m68k/mm: make node data and node setup depend onCONFIG_DISCONTIGMEMm68k/mm: enable use of genericmemory_model.hfor !DISCONTIGMEM m68k/mm: switch from DISCONTIGMEM to SPARSEMEMarch/m68k/Kconfig.cpu | 14 ++++++-- arch/m68k/include/asm/page.h | 2 ++ arch/m68k/include/asm/page_mm.h | 6 +++- arch/m68k/include/asm/q.h | 8 +++++ arch/m68k/include/asm/virtconvert.h | 2 +- arch/m68k/mm/init.c | 8 ++--- arch/m68k/mm/motorola.c | 64 ++++++++++++++++++++++++++++++------- 7 files changed, 84 insertions(+), 20 deletions(-)create mode 100644
arch/m68k/include/asm/sparsemem.hSignature · 20 lines
2.7.4 *** BLURB HERE *** Mike Rapoport (3): m68k/mm: make node data and node setup depend on CONFIG_DISCONTIGMEM m68k/mm: enable use of generic memory_model.h for !DISCONTIGMEM m68k/mm: switch from DISCONTIGMEM to SPARSEMEM arch/m68k/Kconfig.cpu | 23 ++++++++++++++--- arch/m68k/include/asm/page.h | 2 ++ arch/m68k/include/asm/page_mm.h | 7 +++++- arch/m68k/include/asm/virtconvert.h | 2 +- arch/m68k/mm/init.c | 8 +++--- arch/m68k/mm/motorola.c | 39 ++++++++++++++++++++++++++--- 6 files changed, 69 insertions(+), 12 deletions(-) -- 2.26.2
Quoted 26 lines · Michael Schmitz
Hi Mike,
Sorry, I had seen those but didn't get around to test in time.
Applying your patch series to Geert's v5.9-rc1, I get this:
Quoted 11 lines
CC
kernel/bounds.s
CCarch/m68k/kernel/asm-offsets.s
In file included from./include/linux/mmzone.h:19,
from./include/linux/topology.h:33,
from./include/linux/irq.h:19,
from./include/asm-generic/hardirq.h:13, from./arch/m68k/include/generated/asm/hardirq.h:1, from./include/linux/hardirq.h:10,
from./include/linux/interrupt.h:11, from./include/linux/kernel_stat.h:9, fromarch/m68k/kernel/asm-offsets.c:16:Quoted 8 lines
./include/linux/page-flags-layout.h:28:10: fatal error:asm/sparsemem.h:
No such file or directory
#include <asm/sparsemem.h>
^~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [arch/m68k/kernel/asm-offsets.s] Error 1 make[1]: *** [prepare0] Error 2
make: *** [__sub-make] Error 2
Quoted 3 lines
Your patch announcement blurb hat
sparsemem.hlisted among the changed files, but none of the three patches stats reference that file. Am I missing a prerequisite here?
Argh, I forgot to 'git add asm/sparsemem.h'. I'll resend a refreshed version in a couple of days.
Quoted 98 lines
Cheers,
Michael
Quoted 92 lines · Mike Rapoport
Gentle ping :)
Quoted 89 lines · Mike Rapoport
From: Mike Rapoport <[email protected]>
Hi,
It took me a while to get back to this, but better late than never :)
These patches replace DISCONTIGMEM with SPARSEMEM on m68k for systems with !SINGLE_MEMORY_CHUNK set.
With SPARSEMEM there is a single node for the entire physical memory and to cope with holes in the physical address space it is divided to sections of several megabytes.
Each section has it's own memory map which size depends on actual populated memory.
The section size of 16M was chosen pretty much arbitrarily as I couldn't find specs for systems with e.g. Zorro memory extensions.
Yet, we cannot use smaller sections and still be able to address the entire 4G of the physical memory because the section number is encoded in the page flags and there are only 8 bits available.For systems with several small memory chunks and with small (several megs) holes between them, 16M section size would cause wasted parts in the memory map and it is desirable to allow smaller section size at the expense of limiting the addressable memory.
I've hesitated between adding
Kconfigoption as Finn suggested [1] and other options likeSPARSE_VMEMMAPorARCH_HAS_HOLES_MEMORYMODEL. In the end, I thinkKconfigis the simplest one from the implementation point of view and would work fine for people that run mainline kernels on vintage hardware.For the systems with ST-RAM and FastRAM, the switch to SPARSEMEM does not change the limitation that if the kernel is loaded into the FastRam the ST-RAM remains unmapped. It only ensures that if the kernel is loaded in ST-RAM, the memory map is allocated from high physical addresses and then
atari/stram.cis able to reserve the frame buffer memory. If the kernel is loaded to FastRAM, the ST-RAM remains unmapped as with DISCONTIGMEM and theatari/stram.cmaps it as IOMEM.[1] https://marc.info/?l=linux-m68k&m=156309170500921&w=2
v3 changes:
* rebase on the current upstream
* aliasARCH_PFN_BASEto m68k_memory[0].addr
* add configuration option to allow two variants of section size.v2 changes:
* rebase on the current upstream
* make ColdFire MMU selectSINGLE_MEMORY_CHUNKinKconfig.cpuMike Rapoport (3):
m68k/mm: make node data and node setup depend onCONFIG_DISCONTIGMEMm68k/mm: enable use of genericmemory_model.hfor !DISCONTIGMEM m68k/mm: switch from DISCONTIGMEM to SPARSEMEMarch/m68k/Kconfig.cpu | 14 ++++++-- arch/m68k/include/asm/page.h | 2 ++ arch/m68k/include/asm/page_mm.h | 6 +++- arch/m68k/include/asm/q.h | 8 +++++ arch/m68k/include/asm/virtconvert.h | 2 +- arch/m68k/mm/init.c | 8 ++--- arch/m68k/mm/motorola.c | 64 ++++++++++++++++++++++++++++++------- 7 files changed, 84 insertions(+), 20 deletions(-)create mode 100644
arch/m68k/include/asm/sparsemem.hSignature · 20 lines
2.7.4 *** BLURB HERE *** Mike Rapoport (3): m68k/mm: make node data and node setup depend on CONFIG_DISCONTIGMEM m68k/mm: enable use of generic memory_model.h for !DISCONTIGMEM m68k/mm: switch from DISCONTIGMEM to SPARSEMEM arch/m68k/Kconfig.cpu | 23 ++++++++++++++--- arch/m68k/include/asm/page.h | 2 ++ arch/m68k/include/asm/page_mm.h | 7 +++++- arch/m68k/include/asm/virtconvert.h | 2 +- arch/m68k/mm/init.c | 8 +++--- arch/m68k/mm/motorola.c | 39 ++++++++++++++++++++++++++--- 6 files changed, 69 insertions(+), 12 deletions(-) -- 2.26.2
Signature · 2 lines
Sincerely yours, Mike.
Hi Mike,
Am 21.08.2020 um 19:56 schrieb Mike Rapoport:
Quoted 27 lines · Michael Schmitz
Quoted 26 lines
Hi Mike,
Sorry, I had seen those but didn't get around to test in time.
Applying your patch series to Geert's v5.9-rc1, I get this:
Quoted 19 lines
CC
kernel/bounds.s
CCarch/m68k/kernel/asm-offsets.s
In file included from./include/linux/mmzone.h:19,from ./include/linux/topology.h:33, from ./include/linux/irq.h:19, from ./include/asm-generic/hardirq.h:13, from ./arch/m68k/include/generated/asm/hardirq.h:1, from ./include/linux/hardirq.h:10, from ./include/linux/interrupt.h:11, from ./include/linux/kernel_stat.h:9, from arch/m68k/kernel/asm-offsets.c:16: ./include/linux/page-flags-layout.h:28:10: fatal error: asm/sparsemem.h: No such file or directory #include <asm/sparsemem.h> ^~~~~~~~~~~~~~~~~compilation terminated.
make[2]: *** [arch/m68k/kernel/asm-offsets.s] Error 1 make[1]: *** [prepare0] Error 2
make: *** [__sub-make] Error 2
Quoted 5 lines
Quoted 3 lines
Your patch announcement blurb hat
sparsemem.hlisted among the changed files, but none of the three patches stats reference that file. Am I missing a prerequisite here?Argh, I forgot to 'git add
asm/sparsemem.h'.
OK, that should be easy enough to overcome. I'll try setting the section size bits according to the 16 MB section size, and test with that for now.
Cheers,
Michael
Quoted 101 lines
I'll resend a refreshed version in a couple of days.
Quoted 98 lines
Cheers,
Michael
Quoted 92 lines · Mike Rapoport
Gentle ping :)
Quoted 89 lines · Mike Rapoport
From: Mike Rapoport <[email protected]>
Hi,
It took me a while to get back to this, but better late than never :)
These patches replace DISCONTIGMEM with SPARSEMEM on m68k for systems with !SINGLE_MEMORY_CHUNK set.
With SPARSEMEM there is a single node for the entire physical memory and to cope with holes in the physical address space it is divided to sections of several megabytes.
Each section has it's own memory map which size depends on actual populated memory.
The section size of 16M was chosen pretty much arbitrarily as I couldn't find specs for systems with e.g. Zorro memory extensions.
Yet, we cannot use smaller sections and still be able to address the entire 4G of the physical memory because the section number is encoded in the page flags and there are only 8 bits available.For systems with several small memory chunks and with small (several megs) holes between them, 16M section size would cause wasted parts in the memory map and it is desirable to allow smaller section size at the expense of limiting the addressable memory.
I've hesitated between adding
Kconfigoption as Finn suggested [1] and other options likeSPARSE_VMEMMAPorARCH_HAS_HOLES_MEMORYMODEL. In the end, I thinkKconfigis the simplest one from the implementation point of view and would work fine for people that run mainline kernels on vintage hardware.For the systems with ST-RAM and FastRAM, the switch to SPARSEMEM does not change the limitation that if the kernel is loaded into the FastRam the ST-RAM remains unmapped. It only ensures that if the kernel is loaded in ST-RAM, the memory map is allocated from high physical addresses and then
atari/stram.cis able to reserve the frame buffer memory. If the kernel is loaded to FastRAM, the ST-RAM remains unmapped as with DISCONTIGMEM and theatari/stram.cmaps it as IOMEM.[1] https://marc.info/?l=linux-m68k&m=156309170500921&w=2
v3 changes:
* rebase on the current upstream
* aliasARCH_PFN_BASEto m68k_memory[0].addr
* add configuration option to allow two variants of section size.v2 changes:
* rebase on the current upstream
* make ColdFire MMU selectSINGLE_MEMORY_CHUNKinKconfig.cpuMike Rapoport (3):
m68k/mm: make node data and node setup depend onCONFIG_DISCONTIGMEMm68k/mm: enable use of genericmemory_model.hfor !DISCONTIGMEM m68k/mm: switch from DISCONTIGMEM to SPARSEMEMarch/m68k/Kconfig.cpu | 14 ++++++-- arch/m68k/include/asm/page.h | 2 ++ arch/m68k/include/asm/page_mm.h | 6 +++- arch/m68k/include/asm/q.h | 8 +++++ arch/m68k/include/asm/virtconvert.h | 2 +- arch/m68k/mm/init.c | 8 ++--- arch/m68k/mm/motorola.c | 64 ++++++++++++++++++++++++++++++------- 7 files changed, 84 insertions(+), 20 deletions(-)create mode 100644
arch/m68k/include/asm/sparsemem.h--
2.7.4*** BLURB HERE ***
Mike Rapoport (3):
m68k/mm: make node data and node setup depend onCONFIG_DISCONTIGMEMm68k/mm: enable use of genericmemory_model.hfor !DISCONTIGMEM m68k/mm: switch from DISCONTIGMEM to SPARSEMEMarch/m68k/Kconfig.cpu | 23 ++++++++++++++--- arch/m68k/include/asm/page.h | 2 ++ arch/m68k/include/asm/page_mm.h | 7 +++++- arch/m68k/include/asm/virtconvert.h | 2 +- arch/m68k/mm/init.c | 8 +++--- arch/m68k/mm/motorola.c | 39 ++++++++++++++++++++++++++--- 6 files changed, 69 insertions(+), 12 deletions(-)--
2.26.2
Hi Mike,
only tested on ARAnyM, but appears to work (after adding sparsemem.h and changing memblocks_present() to non-static).
20 kB more total memory with sparsemem. Less memory used when booting to FastRAM, more used when booting to ST-RAM (checked right after boot on an idle system). The latter probably isn't significant.
Cheers,
Michael
Am 21.08.2020 um 19:56 schrieb Mike Rapoport:
Quoted 133 lines · Michael Schmitz
Quoted 26 lines
Hi Mike,
Sorry, I had seen those but didn't get around to test in time.
Applying your patch series to Geert's v5.9-rc1, I get this:
Quoted 15 lines
CC
kernel/bounds.s
CCarch/m68k/kernel/asm-offsets.s
In file included from./include/linux/mmzone.h:19,from ./include/linux/topology.h:33, from ./include/linux/irq.h:19, from ./include/asm-generic/hardirq.h:13, from ./arch/m68k/include/generated/asm/hardirq.h:1, from ./include/linux/hardirq.h:10, from ./include/linux/interrupt.h:11, from ./include/linux/kernel_stat.h:9, from arch/m68k/kernel/asm-offsets.c:16: ./include/linux/page-flags-layout.h:28:10: fatal error: asm/sparsemem.h: No such file or directory #include <asm/sparsemem.h> ^~~~~~~~~~~~~~~~~Quoted 4 lines
compilation terminated.
make[2]: *** [arch/m68k/kernel/asm-offsets.s] Error 1 make[1]: *** [prepare0] Error 2
make: *** [__sub-make] Error 2Quoted 3 lines
Your patch announcement blurb hat
sparsemem.hlisted among the changed files, but none of the three patches stats reference that file. Am I missing a prerequisite here?Argh, I forgot to 'git add
asm/sparsemem.h'. I'll resend a refreshed version in a couple of days.Quoted 98 lines
Cheers,
Michael
Quoted 92 lines · Mike Rapoport
Gentle ping :)
Quoted 89 lines · Mike Rapoport
From: Mike Rapoport <[email protected]>
Hi,
It took me a while to get back to this, but better late than never :)
These patches replace DISCONTIGMEM with SPARSEMEM on m68k for systems with !SINGLE_MEMORY_CHUNK set.
With SPARSEMEM there is a single node for the entire physical memory and to cope with holes in the physical address space it is divided to sections of several megabytes.
Each section has it's own memory map which size depends on actual populated memory.
The section size of 16M was chosen pretty much arbitrarily as I couldn't find specs for systems with e.g. Zorro memory extensions.
Yet, we cannot use smaller sections and still be able to address the entire 4G of the physical memory because the section number is encoded in the page flags and there are only 8 bits available.For systems with several small memory chunks and with small (several megs) holes between them, 16M section size would cause wasted parts in the memory map and it is desirable to allow smaller section size at the expense of limiting the addressable memory.
I've hesitated between adding
Kconfigoption as Finn suggested [1] and other options likeSPARSE_VMEMMAPorARCH_HAS_HOLES_MEMORYMODEL. In the end, I thinkKconfigis the simplest one from the implementation point of view and would work fine for people that run mainline kernels on vintage hardware.For the systems with ST-RAM and FastRAM, the switch to SPARSEMEM does not change the limitation that if the kernel is loaded into the FastRam the ST-RAM remains unmapped. It only ensures that if the kernel is loaded in ST-RAM, the memory map is allocated from high physical addresses and then
atari/stram.cis able to reserve the frame buffer memory. If the kernel is loaded to FastRAM, the ST-RAM remains unmapped as with DISCONTIGMEM and theatari/stram.cmaps it as IOMEM.[1] https://marc.info/?l=linux-m68k&m=156309170500921&w=2
v3 changes:
* rebase on the current upstream
* aliasARCH_PFN_BASEto m68k_memory[0].addr
* add configuration option to allow two variants of section size.v2 changes:
* rebase on the current upstream
* make ColdFire MMU selectSINGLE_MEMORY_CHUNKinKconfig.cpuMike Rapoport (3):
m68k/mm: make node data and node setup depend onCONFIG_DISCONTIGMEMm68k/mm: enable use of genericmemory_model.hfor !DISCONTIGMEM m68k/mm: switch from DISCONTIGMEM to SPARSEMEMarch/m68k/Kconfig.cpu | 14 ++++++-- arch/m68k/include/asm/page.h | 2 ++ arch/m68k/include/asm/page_mm.h | 6 +++- arch/m68k/include/asm/q.h | 8 +++++ arch/m68k/include/asm/virtconvert.h | 2 +- arch/m68k/mm/init.c | 8 ++--- arch/m68k/mm/motorola.c | 64 ++++++++++++++++++++++++++++++------- 7 files changed, 84 insertions(+), 20 deletions(-)create mode 100644
arch/m68k/include/asm/sparsemem.h--
2.7.4*** BLURB HERE ***
Mike Rapoport (3):
m68k/mm: make node data and node setup depend onCONFIG_DISCONTIGMEMm68k/mm: enable use of genericmemory_model.hfor !DISCONTIGMEM m68k/mm: switch from DISCONTIGMEM to SPARSEMEMarch/m68k/Kconfig.cpu | 23 ++++++++++++++--- arch/m68k/include/asm/page.h | 2 ++ arch/m68k/include/asm/page_mm.h | 7 +++++- arch/m68k/include/asm/virtconvert.h | 2 +- arch/m68k/mm/init.c | 8 +++--- arch/m68k/mm/motorola.c | 39 ++++++++++++++++++++++++++--- 6 files changed, 69 insertions(+), 12 deletions(-)--
2.26.2
Hi Michael,
Quoted 4 lines · Michael Schmitz
Hi Mike,
only tested on ARAnyM, but appears to work (after adding
sparsemem.hand changingmemblocks_present()to non-static).
Cool, thanks!memblocks_present() is now called from sparse_init() and can be simply dropped.
Quoted 3 lines
20 kB more total memory with sparsemem. Less memory used when booting to FastRAM, more used when booting to ST-RAM (checked right after boot on an idle system). The latter probably isn't significant.
When booting to FastRAM we still discard ST-RAM and only use it as device memory for the framebuffer. So the total memory map size will be smaller.
How many FastRAM do you have in your configuration?
Quoted 139 lines
Cheers,
Michael
Am 21.08.2020 um 19:56 schrieb Mike Rapoport:
Quoted 133 lines · Michael Schmitz
Quoted 26 lines
Hi Mike,
Sorry, I had seen those but didn't get around to test in time.
Applying your patch series to Geert's v5.9-rc1, I get this:
Quoted 15 lines
CC
kernel/bounds.s
CCarch/m68k/kernel/asm-offsets.s
In file included from./include/linux/mmzone.h:19,from ./include/linux/topology.h:33, from ./include/linux/irq.h:19, from ./include/asm-generic/hardirq.h:13, from ./arch/m68k/include/generated/asm/hardirq.h:1, from ./include/linux/hardirq.h:10, from ./include/linux/interrupt.h:11, from ./include/linux/kernel_stat.h:9, from arch/m68k/kernel/asm-offsets.c:16: ./include/linux/page-flags-layout.h:28:10: fatal error: asm/sparsemem.h: No such file or directory #include <asm/sparsemem.h> ^~~~~~~~~~~~~~~~~Quoted 4 lines
compilation terminated.
make[2]: *** [arch/m68k/kernel/asm-offsets.s] Error 1 make[1]: *** [prepare0] Error 2
make: *** [__sub-make] Error 2Quoted 3 lines
Your patch announcement blurb hat
sparsemem.hlisted among the changed files, but none of the three patches stats reference that file. Am I missing a prerequisite here?Argh, I forgot to 'git add
asm/sparsemem.h'. I'll resend a refreshed version in a couple of days.Quoted 98 lines
Cheers,
Michael
Quoted 92 lines · Mike Rapoport
Gentle ping :)
Quoted 89 lines · Mike Rapoport
From: Mike Rapoport <[email protected]>
Hi,
It took me a while to get back to this, but better late than never :)
These patches replace DISCONTIGMEM with SPARSEMEM on m68k for systems with !SINGLE_MEMORY_CHUNK set.
With SPARSEMEM there is a single node for the entire physical memory and to cope with holes in the physical address space it is divided to sections of several megabytes.
Each section has it's own memory map which size depends on actual populated memory.
The section size of 16M was chosen pretty much arbitrarily as I couldn't find specs for systems with e.g. Zorro memory extensions.
Yet, we cannot use smaller sections and still be able to address the entire 4G of the physical memory because the section number is encoded in the page flags and there are only 8 bits available.For systems with several small memory chunks and with small (several megs) holes between them, 16M section size would cause wasted parts in the memory map and it is desirable to allow smaller section size at the expense of limiting the addressable memory.
I've hesitated between adding
Kconfigoption as Finn suggested [1] and other options likeSPARSE_VMEMMAPorARCH_HAS_HOLES_MEMORYMODEL. In the end, I thinkKconfigis the simplest one from the implementation point of view and would work fine for people that run mainline kernels on vintage hardware.For the systems with ST-RAM and FastRAM, the switch to SPARSEMEM does not change the limitation that if the kernel is loaded into the FastRam the ST-RAM remains unmapped. It only ensures that if the kernel is loaded in ST-RAM, the memory map is allocated from high physical addresses and then
atari/stram.cis able to reserve the frame buffer memory. If the kernel is loaded to FastRAM, the ST-RAM remains unmapped as with DISCONTIGMEM and theatari/stram.cmaps it as IOMEM.[1] https://marc.info/?l=linux-m68k&m=156309170500921&w=2
v3 changes:
* rebase on the current upstream
* aliasARCH_PFN_BASEto m68k_memory[0].addr
* add configuration option to allow two variants of section size.v2 changes:
* rebase on the current upstream
* make ColdFire MMU selectSINGLE_MEMORY_CHUNKinKconfig.cpuMike Rapoport (3):
m68k/mm: make node data and node setup depend onCONFIG_DISCONTIGMEMm68k/mm: enable use of genericmemory_model.hfor !DISCONTIGMEM m68k/mm: switch from DISCONTIGMEM to SPARSEMEMarch/m68k/Kconfig.cpu | 14 ++++++-- arch/m68k/include/asm/page.h | 2 ++ arch/m68k/include/asm/page_mm.h | 6 +++- arch/m68k/include/asm/q.h | 8 +++++ arch/m68k/include/asm/virtconvert.h | 2 +- arch/m68k/mm/init.c | 8 ++--- arch/m68k/mm/motorola.c | 64 ++++++++++++++++++++++++++++++------- 7 files changed, 84 insertions(+), 20 deletions(-)create mode 100644
arch/m68k/include/asm/sparsemem.h--
2.7.4*** BLURB HERE ***
Mike Rapoport (3):
m68k/mm: make node data and node setup depend onCONFIG_DISCONTIGMEMm68k/mm: enable use of genericmemory_model.hfor !DISCONTIGMEM m68k/mm: switch from DISCONTIGMEM to SPARSEMEMarch/m68k/Kconfig.cpu | 23 ++++++++++++++--- arch/m68k/include/asm/page.h | 2 ++ arch/m68k/include/asm/page_mm.h | 7 +++++- arch/m68k/include/asm/virtconvert.h | 2 +- arch/m68k/mm/init.c | 8 +++--- arch/m68k/mm/motorola.c | 39 ++++++++++++++++++++++++++--- 6 files changed, 69 insertions(+), 12 deletions(-)--
2.26.2
Signature · 2 lines
Sincerely yours, Mike.
Hi Mike,
Am 22.08.2020 um 21:51 schrieb Mike Rapoport:
Quoted 11 lines
Hi Michael,
Quoted 4 lines · Michael Schmitz
Hi Mike,
only tested on ARAnyM, but appears to work (after adding
sparsemem.hand changingmemblocks_present()to non-static).Cool, thanks!
memblocks_present()is now called fromsparse_init()and can be simply dropped.
Right you are - I missed that in the hurry.
Quoted 8 lines
Quoted 4 lines
20 kB more total memory with sparsemem. Less memory used when booting to FastRAM, more used when booting to ST-RAM (checked right after boot on an idle system). The latter probably isn't significant.
When booting to FastRAM we still discard ST-RAM and only use it as device memory for the framebuffer. So the total memory map size will be smaller.
Makes sense, but I was still surprised that replacing discontigmem by sparsemem saves 20 kB regardless of whether or not ST-RAM is used.
Quoted 1 line
How many FastRAM do you have in your configuration?
Only 256 MB. Can't use much more on my old Powerbook.
Cheers,
Michael
Quoted 22 lines · Michael Schmitz
Hi Mike,
Am 22.08.2020 um 21:51 schrieb Mike Rapoport:
Quoted 11 lines
Hi Michael,
Quoted 4 lines · Michael Schmitz
Hi Mike,
only tested on ARAnyM, but appears to work (after adding
sparsemem.hand changingmemblocks_present()to non-static).Cool, thanks!
memblocks_present()is now called fromsparse_init()and can be simply dropped.Right you are - I missed that in the hurry.
Quoted 5 lines
Quoted 4 lines
20 kB more total memory with sparsemem. Less memory used when booting to FastRAM, more used when booting to ST-RAM (checked right after boot on an idle system). The latter probably isn't significant.
Quoted 6 lines
Quoted 3 lines
When booting to FastRAM we still discard ST-RAM and only use it as device memory for the framebuffer. So the total memory map size will be smaller.
Makes sense, but I was still surprised that replacing discontigmem by sparsemem saves 20 kB regardless of whether or not ST-RAM is used.
The problem with sparse, however, is the memory wasted for empty memmap. For example, if the section size is 16M and there is, say, 17M of FastRAM, the memory map will be created for 32M. This means that there will be 3840 unused 'struct page' objects. :(
Quoted 8 lines
Quoted 1 line
How many FastRAM do you have in your configuration?
Only 256 MB. Can't use much more on my old Powerbook.
Cheers,
Michael
Signature · 2 lines
Sincerely yours, Mike.
Hi Mike,
Quoted 6 lines · Mike Rapoport
Quoted 6 lines
Quoted 6 lines
Quoted 3 lines
20 kB more total memory with sparsemem. Less memory used when booting to FastRAM, more used when booting to ST-RAM (checked right after boot on an idle system). The latter probably isn't significant.
When booting to FastRAM we still discard ST-RAM and only use it as device memory for the framebuffer. So the total memory map size will be smaller.
Quoted 6 lines
Quoted 2 lines
Makes sense, but I was still surprised that replacing discontigmem by sparsemem saves 20 kB regardless of whether or not ST-RAM is used.
The problem with sparse, however, is the memory wasted for empty memmap. For example, if the section size is 16M and there is, say, 17M of FastRAM, the memory map will be created for 32M. This means that there will be 3840 unused 'struct page' objects. :(
No such thing as a free lunch - that would be a case for the 1G VM limit (which I admit, I did not test!)?
In my case, ST-RAM is 14 MB, so only half of the last 4 MB wasted. Note that the top of the 16 MB physical area is mapped by early kernel startup as noncacheable (hardware registers). I hope this mapping is left alone by sparsemem.
Now what would be required to allow use of the ST-RAM chunk (or any other memory area mapped out of order) by the kernel memory allocators?
Cheers,
Michael
Quoted 8 lines
Quoted 8 lines
Quoted 2 lines
How many FastRAM do you have in your configuration?
Only 256 MB. Can't use much more on my old Powerbook.
Cheers,
Michael
Quoted 11 lines · Michael Schmitz
Hi Mike,
Quoted 8 lines · Mike Rapoport
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
20 kB more total memory with sparsemem. Less memory used when booting to FastRAM, more used when booting to ST-RAM (checked right after boot on an idle system). The latter probably isn't significant.
When booting to FastRAM we still discard ST-RAM and only use it as device memory for the framebuffer. So the total memory map size will be smaller.
Makes sense, but I was still surprised that replacing discontigmem by sparsemem saves 20 kB regardless of whether or not ST-RAM is used.
Quoted 7 lines
Quoted 4 lines
The problem with sparse, however, is the memory wasted for empty memmap. For example, if the section size is 16M and there is, say, 17M of FastRAM, the memory map will be created for 32M. This means that there will be 3840 unused 'struct page' objects. :(
No such thing as a free lunch - that would be a case for the 1G VM limit (which I admit, I did not test!)?
For 1G physical memory limit the section size is 4M, so for a system with 1M of RAM there will be 768 unused 'struct page' objects. There is an option to free unused memmap, like ARM does [1], or even make sparsemem to avoid allocating it from the beginning.
This should work, at least for the -mm case, because m68k has pfn_valid() that does not depend on the memory model.
Quoted 4 lines
In my case, ST-RAM is 14 MB, so only half of the last 4 MB wasted. Note that the top of the 16 MB physical area is mapped by early kernel startup as noncacheable (hardware registers). I hope this mapping is left alone by sparsemem.
Sparsmem will allocate an empty struct page for it, but it should not be used and even initialized. And I didn't change the page table creation code, at least not intentionally :)
Quoted 2 lines
Now what would be required to allow use of the ST-RAM chunk (or any other memory area mapped out of order) by the kernel memory allocators?
Oh, that's a different story. This will require changes to the way we create the virtual mapping of the physical memory and to __pa()/__va() functions.
[1] https://elixir.bootlin.com/linux/latest/source/arch/arm/mm/init.c#L305
Signature · 2 lines
Sincerely yours, Mike.