Skip to content

Commit 5f77108

Browse files
Alexandre Ghitipalmer-dabbelt
authored andcommitted
riscv: Do not restrict memory size because of linear mapping on nommu
It makes no sense to restrict physical memory size because of linear mapping size constraints when there is no linear mapping, so only do that when mmu is enabled. Reported-by: Geert Uytterhoeven <geert@linux-m68k.org> Closes: https://lore.kernel.org/linux-riscv/CAMuHMdW0bnJt5GMRtOZGkTiM7GK4UaLJCDMF_Ouq++fnDKi3_A@mail.gmail.com/ Fixes: 3b65644 ("riscv: Fix linear mapping checks for non-contiguous memory regions") Signed-off-by: Alexandre Ghiti <alexghiti@rivosinc.com> Tested-by: Geert Uytterhoeven <geert+renesas@glider.be> Link: https://lore.kernel.org/r/20240827065230.145021-1-alexghiti@rivosinc.com Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
1 parent 5ba7a75 commit 5f77108

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

arch/riscv/mm/init.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -252,7 +252,7 @@ static void __init setup_bootmem(void)
252252
* The size of the linear page mapping may restrict the amount of
253253
* usable RAM.
254254
*/
255-
if (IS_ENABLED(CONFIG_64BIT)) {
255+
if (IS_ENABLED(CONFIG_64BIT) && IS_ENABLED(CONFIG_MMU)) {
256256
max_mapped_addr = __pa(PAGE_OFFSET) + KERN_VIRT_SIZE;
257257
memblock_cap_memory_range(phys_ram_base,
258258
max_mapped_addr - phys_ram_base);

0 commit comments

Comments
 (0)