riscv: Get rid of MAXPHYSMEM configs
authorAlexandre Ghiti <alexandre.ghiti@canonical.com>
Mon, 17 Jan 2022 09:57:16 +0000 (10:57 +0100)
committerPalmer Dabbelt <palmer@rivosinc.com>
Wed, 19 Jan 2022 23:12:32 +0000 (15:12 -0800)
commitdb1503d355a79d1d4255a9996f20e72848b74a56
tree764e3005492caecb74b1bc8656d288c4de80dd6d
parentfa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf
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: 2bfc6cd81bd1 ("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>
arch/riscv/Kconfig
arch/riscv/configs/nommu_k210_defconfig
arch/riscv/configs/nommu_k210_sdcard_defconfig
arch/riscv/configs/nommu_virt_defconfig