2019-05-27 14:55:01 +08:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0-or-later */
|
powerpc: Make the 64-bit kernel as a position-independent executable
This implements CONFIG_RELOCATABLE for 64-bit by making the kernel as
a position-independent executable (PIE) when it is set. This involves
processing the dynamic relocations in the image in the early stages of
booting, even if the kernel is being run at the address it is linked at,
since the linker does not necessarily fill in words in the image for
which there are dynamic relocations. (In fact the linker does fill in
such words for 64-bit executables, though not for 32-bit executables,
so in principle we could avoid calling relocate() entirely when we're
running a 64-bit kernel at the linked address.)
The dynamic relocations are processed by a new function relocate(addr),
where the addr parameter is the virtual address where the image will be
run. In fact we call it twice; once before calling prom_init, and again
when starting the main kernel. This means that reloc_offset() returns
0 in prom_init (since it has been relocated to the address it is running
at), which necessitated a few adjustments.
This also changes __va and __pa to use an equivalent definition that is
simpler. With the relocatable kernel, PAGE_OFFSET and MEMORY_START are
constants (for 64-bit) whereas PHYSICAL_START is a variable (and
KERNELBASE ideally should be too, but isn't yet).
With this, relocatable kernels still copy themselves down to physical
address 0 and run there.
Signed-off-by: Paul Mackerras <paulus@samba.org>
2008-08-30 09:43:47 +08:00
|
|
|
/*
|
|
|
|
* Code to process dynamic relocations in the kernel.
|
|
|
|
*
|
|
|
|
* Copyright 2008 Paul Mackerras, IBM Corp.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <asm/ppc_asm.h>
|
|
|
|
|
|
|
|
RELA = 7
|
|
|
|
RELACOUNT = 0x6ffffff9
|
|
|
|
R_PPC64_RELATIVE = 22
|
|
|
|
|
|
|
|
/*
|
|
|
|
* r3 = desired final address of kernel
|
|
|
|
*/
|
|
|
|
_GLOBAL(relocate)
|
|
|
|
mflr r0
|
|
|
|
bcl 20,31,$+4
|
|
|
|
0: mflr r12 /* r12 has runtime addr of label 0 */
|
|
|
|
mtlr r0
|
|
|
|
ld r11,(p_dyn - 0b)(r12)
|
|
|
|
add r11,r11,r12 /* r11 has runtime addr of .dynamic section */
|
|
|
|
ld r9,(p_rela - 0b)(r12)
|
|
|
|
add r9,r9,r12 /* r9 has runtime addr of .rela.dyn section */
|
|
|
|
ld r10,(p_st - 0b)(r12)
|
|
|
|
add r10,r10,r12 /* r10 has runtime addr of _stext */
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Scan the dynamic section for the RELA and RELACOUNT entries.
|
|
|
|
*/
|
|
|
|
li r7,0
|
|
|
|
li r8,0
|
|
|
|
1: ld r6,0(r11) /* get tag */
|
|
|
|
cmpdi r6,0
|
|
|
|
beq 4f /* end of list */
|
|
|
|
cmpdi r6,RELA
|
|
|
|
bne 2f
|
|
|
|
ld r7,8(r11) /* get RELA pointer in r7 */
|
|
|
|
b 3f
|
|
|
|
2: addis r6,r6,(-RELACOUNT)@ha
|
|
|
|
cmpdi r6,RELACOUNT@l
|
|
|
|
bne 3f
|
|
|
|
ld r8,8(r11) /* get RELACOUNT value in r8 */
|
|
|
|
3: addi r11,r11,16
|
|
|
|
b 1b
|
|
|
|
4: cmpdi r7,0 /* check we have both RELA and RELACOUNT */
|
|
|
|
cmpdi cr1,r8,0
|
|
|
|
beq 6f
|
|
|
|
beq cr1,6f
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Work out linktime address of _stext and hence the
|
|
|
|
* relocation offset to be applied.
|
|
|
|
* cur_offset [r7] = rela.run [r9] - rela.link [r7]
|
|
|
|
* _stext.link [r10] = _stext.run [r10] - cur_offset [r7]
|
|
|
|
* final_offset [r3] = _stext.final [r3] - _stext.link [r10]
|
|
|
|
*/
|
|
|
|
subf r7,r7,r9 /* cur_offset */
|
|
|
|
subf r10,r7,r10
|
|
|
|
subf r3,r10,r3 /* final_offset */
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Run through the list of relocations and process the
|
|
|
|
* R_PPC64_RELATIVE ones.
|
|
|
|
*/
|
|
|
|
mtctr r8
|
2014-01-30 23:58:42 +08:00
|
|
|
5: ld r0,8(9) /* ELF64_R_TYPE(reloc->r_info) */
|
|
|
|
cmpdi r0,R_PPC64_RELATIVE
|
powerpc: Make the 64-bit kernel as a position-independent executable
This implements CONFIG_RELOCATABLE for 64-bit by making the kernel as
a position-independent executable (PIE) when it is set. This involves
processing the dynamic relocations in the image in the early stages of
booting, even if the kernel is being run at the address it is linked at,
since the linker does not necessarily fill in words in the image for
which there are dynamic relocations. (In fact the linker does fill in
such words for 64-bit executables, though not for 32-bit executables,
so in principle we could avoid calling relocate() entirely when we're
running a 64-bit kernel at the linked address.)
The dynamic relocations are processed by a new function relocate(addr),
where the addr parameter is the virtual address where the image will be
run. In fact we call it twice; once before calling prom_init, and again
when starting the main kernel. This means that reloc_offset() returns
0 in prom_init (since it has been relocated to the address it is running
at), which necessitated a few adjustments.
This also changes __va and __pa to use an equivalent definition that is
simpler. With the relocatable kernel, PAGE_OFFSET and MEMORY_START are
constants (for 64-bit) whereas PHYSICAL_START is a variable (and
KERNELBASE ideally should be too, but isn't yet).
With this, relocatable kernels still copy themselves down to physical
address 0 and run there.
Signed-off-by: Paul Mackerras <paulus@samba.org>
2008-08-30 09:43:47 +08:00
|
|
|
bne 6f
|
|
|
|
ld r6,0(r9) /* reloc->r_offset */
|
|
|
|
ld r0,16(r9) /* reloc->r_addend */
|
|
|
|
add r0,r0,r3
|
|
|
|
stdx r0,r7,r6
|
|
|
|
addi r9,r9,24
|
|
|
|
bdnz 5b
|
|
|
|
|
|
|
|
6: blr
|
|
|
|
|
2014-03-04 05:31:24 +08:00
|
|
|
.balign 8
|
2017-03-09 13:42:12 +08:00
|
|
|
p_dyn: .8byte __dynamic_start - 0b
|
|
|
|
p_rela: .8byte __rela_dyn_start - 0b
|
|
|
|
p_st: .8byte _stext - 0b
|
powerpc: Make the 64-bit kernel as a position-independent executable
This implements CONFIG_RELOCATABLE for 64-bit by making the kernel as
a position-independent executable (PIE) when it is set. This involves
processing the dynamic relocations in the image in the early stages of
booting, even if the kernel is being run at the address it is linked at,
since the linker does not necessarily fill in words in the image for
which there are dynamic relocations. (In fact the linker does fill in
such words for 64-bit executables, though not for 32-bit executables,
so in principle we could avoid calling relocate() entirely when we're
running a 64-bit kernel at the linked address.)
The dynamic relocations are processed by a new function relocate(addr),
where the addr parameter is the virtual address where the image will be
run. In fact we call it twice; once before calling prom_init, and again
when starting the main kernel. This means that reloc_offset() returns
0 in prom_init (since it has been relocated to the address it is running
at), which necessitated a few adjustments.
This also changes __va and __pa to use an equivalent definition that is
simpler. With the relocatable kernel, PAGE_OFFSET and MEMORY_START are
constants (for 64-bit) whereas PHYSICAL_START is a variable (and
KERNELBASE ideally should be too, but isn't yet).
With this, relocatable kernels still copy themselves down to physical
address 0 and run there.
Signed-off-by: Paul Mackerras <paulus@samba.org>
2008-08-30 09:43:47 +08:00
|
|
|
|