diff options
| author | Palmer Dabbelt <[email protected]> | 2025-03-26 22:55:45 +0000 |
|---|---|---|
| committer | Palmer Dabbelt <[email protected]> | 2025-03-26 22:56:49 +0000 |
| commit | f633de4aa4537c190a9842c3e84e77780621c615 (patch) | |
| tree | 1ce477b4058436b9ce7a8834a44d3038d94ba8da /net/unix/sysctl_net_unix.c | |
| parent | Merge tag 'riscv-mw1-6.15-rc1' of ssh://gitolite.kernel.org/pub/scm/linux/ker... (diff) | |
| parent | riscv: Remove CONFIG_PAGE_OFFSET (diff) | |
| download | kernel-f633de4aa4537c190a9842c3e84e77780621c615.tar.gz kernel-f633de4aa4537c190a9842c3e84e77780621c615.zip | |
Merge patch series "riscv: Relocatable NOMMU kernels"
Samuel Holland <[email protected]> says:
Currently, RISC-V NOMMU kernels are linked at CONFIG_PAGE_OFFSET, and
since they are not relocatable, must be loaded at this address as well.
CONFIG_PAGE_OFFSET is not a user-visible Kconfig option, so its value is
not obvious, and users must patch the kernel source if they want to load
it at a different address.
Make NOMMU kernels more portable by making them relocatable by default.
This allows a single kernel binary to work when loaded at any address.
* b4-shazam-merge:
riscv: Remove CONFIG_PAGE_OFFSET
riscv: Support CONFIG_RELOCATABLE on riscv32
asm-generic: Always define Elf_Rel and Elf_Rela
riscv: Support CONFIG_RELOCATABLE on NOMMU
riscv: Allow NOMMU kernels to access all of RAM
riscv: Remove duplicate CONFIG_PAGE_OFFSET definition
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Palmer Dabbelt <[email protected]>
Diffstat (limited to 'net/unix/sysctl_net_unix.c')
0 files changed, 0 insertions, 0 deletions