diff options
| author | Alexander Gordeev <agordeev@linux.ibm.com> | 2023-09-26 15:58:51 +0200 |
|---|---|---|
| committer | Alexander Gordeev <agordeev@linux.ibm.com> | 2024-04-17 13:38:02 +0200 |
| commit | 54f2ecc3188f78723267826f634e0747169f8685 (patch) | |
| tree | 8359599359b4c4730842f3f1dd5ef33e87cb55fa /arch/s390/tools | |
| parent | c98d2ecae08f02bd2dccd24e7e485e9f0211db65 (diff) | |
| download | linux-stable-54f2ecc3188f78723267826f634e0747169f8685.tar.gz linux-stable-54f2ecc3188f78723267826f634e0747169f8685.tar.bz2 linux-stable-54f2ecc3188f78723267826f634e0747169f8685.zip | |
s390: Map kernel at fixed location when KASLR is disabled
Since kernel virtual and physical address spaces are
uncoupled the kernel is mapped at the top of the virtual
address space in case KASLR is disabled.
That does not pose any issue with regard to the kernel
booting and operation, but makes it difficult to use a
generated vmlinux with some debugging tools (e.g. gdb),
because the exact location of the kernel image in virtual
memory is unknown. Make that location known and introduce
CONFIG_KERNEL_IMAGE_BASE configuration option.
A custom CONFIG_KERNEL_IMAGE_BASE value that would break
the virtual memory layout leads to a build error.
The kernel image size is defined by KERNEL_IMAGE_SIZE
macro and set to 512 MB, by analogy with x86.
Suggested-by: Vasily Gorbik <gor@linux.ibm.com>
Signed-off-by: Alexander Gordeev <agordeev@linux.ibm.com>
Diffstat (limited to 'arch/s390/tools')
| -rw-r--r-- | arch/s390/tools/relocs.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/s390/tools/relocs.c b/arch/s390/tools/relocs.c index 30a732c808f3..b4f35506779b 100644 --- a/arch/s390/tools/relocs.c +++ b/arch/s390/tools/relocs.c @@ -280,7 +280,7 @@ static int do_reloc(struct section *sec, Elf_Rel *rel) case R_390_GOTOFF64: break; case R_390_64: - add_reloc(&relocs64, offset); + add_reloc(&relocs64, offset - (ehdr.e_entry - 0x100000)); break; default: die("Unsupported relocation type: %d\n", r_type); |