/linux/arch/sh/kernel/ |
H A D | module.c | 33 Elf32_Addr relocation; in apply_relocate_add() local 47 relocation = sym->st_value + rel[i].r_addend; in apply_relocate_add() 54 value += relocation; in apply_relocate_add() 58 relocation = (relocation - (Elf32_Addr) location); in apply_relocate_add() 60 value += relocation; in apply_relocate_add() 65 ((relocation & 0xffff) << 10); in apply_relocate_add() 69 (((relocation >> 16) & 0xffff) << 10); in apply_relocate_add() 72 relocation -= (Elf32_Addr) location; in apply_relocate_add() 74 ((relocation & 0xffff) << 10); in apply_relocate_add() 77 relocation -= (Elf32_Addr) location; in apply_relocate_add() [all …]
|
/linux/Documentation/livepatch/ |
H A D | module-elf-format.rst | 21 loader to perform the all the arch-specific relocation work. Specifically, 30 table, symbol table, and relocation section indices, ELF information is 32 relocation sections and symbols, which are described in this document. The 33 ELF constants used to mark livepatch symbols and relocation sections were 51 relocation sections in place of dynrela sections, and the symbols that the 53 arch-specific livepatch relocation code is replaced by a call to 80 3. Livepatch relocation sections 83 A livepatch module manages its own ELF relocation sections to apply 87 relocation section(s) to the driver once it loads. 90 multiple livepatch relocation sections associated with it (e.g. patches to [all …]
|
H A D | livepatch.rst | 238 relocation section in the generated livepatch module, see
|
/linux/arch/arc/kernel/ |
H A D | module.c | 54 Elf32_Addr relocation, location, tgt_addr; in apply_relocate_add() local 83 relocation = sym_entry->st_value + rel_entry[i].r_addend; in apply_relocate_add() 93 sym_entry->st_value, location, relocation, s); in apply_relocate_add() 103 arc_write_me((unsigned short *)location, relocation); in apply_relocate_add() 105 *((Elf32_Addr *) location) = relocation; in apply_relocate_add() 107 *((Elf32_Addr *) location) = relocation - location; in apply_relocate_add()
|
/linux/arch/arm/mach-hisi/ |
H A D | platmcpm.c | 269 void __iomem *relocation; in hip04_smp_init() local 292 relocation = ioremap(hip04_boot_method[2], hip04_boot_method[3]); in hip04_smp_init() 293 if (!relocation) { in hip04_smp_init() 327 writel_relaxed(hip04_boot_method[0], relocation); in hip04_smp_init() 328 writel_relaxed(0xa5a5a5a5, relocation + 4); /* magic number */ in hip04_smp_init() 329 writel_relaxed(__pa_symbol(secondary_startup), relocation + 8); in hip04_smp_init() 330 writel_relaxed(0, relocation + 12); in hip04_smp_init() 331 iounmap(relocation); in hip04_smp_init() 340 iounmap(relocation); in hip04_smp_init()
|
/linux/Documentation/bpf/ |
H A D | llvm_reloc.rst | 7 This document describes LLVM BPF backend relocation types. 12 LLVM BPF backend records each relocation with the following 16-byte 62 Each relocation is represented by ``Offset`` (8 bytes) and ``Info`` (8 bytes). 63 For example, the first relocation corresponds to the first instruction 64 (Offset 0x0) and the corresponding ``Info`` indicates the relocation type 81 Similarly, the second relocation is at ``.text`` offset ``0x18``, instruction 3, 83 The second relocation resolves to global variable ``g2`` which has a symbol 106 Six relocation types are supported. The following is an overview and 117 For example, ``R_BPF_64_64`` relocation type is used for ``ld_imm64`` instruction. 120 data bitsize is 32 (4 bytes). The relocation can be resolved with [all …]
|
H A D | btf.rst | 929 BTF relocation happens on kernel module load when a kernel module has a 960 is to struct foo, and relocation results in new split BTF:: 966 So we see how .BTF.base plays the role of facilitating later relocation,
|
/linux/arch/powerpc/platforms/8xx/ |
H A D | Kconfig | 143 bool "I2C/SPI relocation patch" 148 bool "I2C/SPI/SMC1 relocation patch" 153 bool "SMC relocation patch"
|
/linux/tools/testing/selftests/bpf/ |
H A D | README.rst | 309 Clang relocation changes 313 that existing relocation types are broken into more types and 314 each new type corresponds to only one way to resolve relocation. 321 Here, ``type 2`` refers to new relocation type ``R_BPF_64_ABS64``.
|
/linux/Documentation/core-api/ |
H A D | this_cpu_ops.rst | 70 the processor. So the relocation to the per cpu base is encoded in the 254 address relocation and a Read-Modify-Write operation in the same 266 relocation. IMHO the second form looks cleaner and has an easier time
|
H A D | local_ops.rst | 22 relocation with the ``local_t`` like semantics in a single instruction and
|
/linux/Documentation/arch/arm/ |
H A D | memory.rst | 35 CPU supports vector relocation (control
|
/linux/Documentation/gpu/ |
H A D | vgaarbiter.rst | 6 modern devices allow relocation of such ranges, some "Legacy" VGA devices
|
H A D | drm-mm.rst | 339 others (a fairly expensive operation), and providing relocation support
|
/linux/arch/riscv/ |
H A D | Kconfig | 1080 which retains all relocation metadata required to relocate the 1083 Since RISCV uses the RELA relocation format, this requires a 1084 relocation pass at runtime even if the kernel is loaded at the
|
/linux/Documentation/bpf/libbpf/ |
H A D | libbpf_overview.rst | 162 recorded BTF type and relocation information and matching them to BTF
|
/linux/arch/ |
H A D | Kconfig | 1536 architectures, and don't require runtime relocation on relocatable 1556 bool "Use RELR relocation packing" 1560 Store the kernel's dynamic relocations in the RELR relocation packing
|
/linux/tools/perf/ |
H A D | Makefile.perf | 1281 $(OUTPUT)tests/llvm-src-{base,kbuild,prologue,relocation}.c \
|
/linux/arch/arm/boot/compressed/ |
H A D | head.S | 304 add sp, sp, r1 @ apply relocation
|
/linux/arch/arm64/ |
H A D | Kconfig | 2312 which retains all relocation metadata required to relocate the 2315 Since AArch64 uses the RELA relocation format, this requires a 2316 relocation pass at runtime even if the kernel is loaded at the
|
/linux/arch/mips/ |
H A D | Kconfig | 2623 This builds a kernel image that retains relocation information 2635 A table of relocation data will be appended to the kernel binary
|
/linux/Documentation/kbuild/ |
H A D | makefiles.rst | 1491 For example, powerpc uses this to check relocation sanity of
|
/linux/arch/x86/ |
H A D | Kconfig | 2145 This builds a kernel image that retains relocation information
|