-
- Downloads
riscv: Get rid of MAXPHYSMEM configs
CONFIG_MAXPHYSMEM_* are actually never used, even the nommu defconfigs selecting the MAXPHYSMEM_2GB had no effects on PAGE_OFFSET since it was preempted by !MMU case right before. In addition, the move of the kernel mapping at the end of the address space broke the use of MAXPHYSMEM_2G with MMU since it defines PAGE_OFFSET at the same address as the kernel mapping. Reported-by:Geert Uytterhoeven <geert@linux-m68k.org> Fixes: 2bfc6cd8 ("riscv: Move kernel mapping outside of linear mapping") Signed-off-by:
Alexandre Ghiti <alexandre.ghiti@canonical.com> Tested-by:
Geert Uytterhoeven <geert@linux-m68k.org> Tested-by:
Conor Dooley <Conor.Dooley@microchip.com> Cc: stable@vger.kernel.org Signed-off-by:
Palmer Dabbelt <palmer@rivosinc.com>
Showing
- arch/riscv/Kconfig 2 additions, 21 deletionsarch/riscv/Kconfig
- arch/riscv/configs/nommu_k210_defconfig 0 additions, 2 deletionsarch/riscv/configs/nommu_k210_defconfig
- arch/riscv/configs/nommu_k210_sdcard_defconfig 0 additions, 2 deletionsarch/riscv/configs/nommu_k210_sdcard_defconfig
- arch/riscv/configs/nommu_virt_defconfig 0 additions, 1 deletionarch/riscv/configs/nommu_virt_defconfig
Loading
Please register or sign in to comment