summaryrefslogtreecommitdiffstats
path: root/net/lapb/lapb_timer.c
diff options
context:
space:
mode:
authorSamuel Holland <samuel.holland@sifive.com>2024-10-26 10:13:58 -0700
committerPalmer Dabbelt <palmer@rivosinc.com>2025-03-26 15:56:46 -0700
commite1cf2d009b00fd890dbbcb8b79613ff538732559 (patch)
tree8e1a2a9d38d27ab5fe96ea4cc42d106bfb1b8e5f /net/lapb/lapb_timer.c
parentea2bde36a46d5724c1b44d80cc9fafbd73c2ecf9 (diff)
downloadlinux-e1cf2d009b00fd890dbbcb8b79613ff538732559.tar.gz
linux-e1cf2d009b00fd890dbbcb8b79613ff538732559.tar.bz2
linux-e1cf2d009b00fd890dbbcb8b79613ff538732559.zip
riscv: Remove CONFIG_PAGE_OFFSET
The current definition of CONFIG_PAGE_OFFSET is problematic for a couple of reasons: 1) The value is misleading for normal 64-bit kernels, where it is overridden at runtime if Sv48 or Sv39 is chosen. This is especially the case for XIP kernels, which always use Sv39. 2) The option is not user-visible, but for NOMMU kernels it must be a valid RAM address, and for !RELOCATABLE it must additionally be the exact address where the kernel is loaded. Fix both of these by removing the option. 1) For MMU kernels, drop the indirection through Kconfig. Additionally, for XIP, drop the indirection through kernel_map. 2) For NOMMU kernels, use the user-visible physical RAM base if provided. Otherwise, force the kernel to be relocatable. Signed-off-by: Samuel Holland <samuel.holland@sifive.com> Reviewed-by: Jesse Taube <mr.bossman075@gmail.com> Link: https://lore.kernel.org/r/20241026171441.3047904-7-samuel.holland@sifive.com Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
Diffstat (limited to 'net/lapb/lapb_timer.c')
0 files changed, 0 insertions, 0 deletions