Home
last modified time | relevance | path

Searched refs:relocation (Results 1 – 25 of 29) sorted by relevance

12

/Linux-v5.15/arch/sh/kernel/
Dmodule.c33 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-v5.15/Documentation/livepatch/
Dmodule-elf-format.rst21 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 …]
Dlivepatch.rst238 relocation section in the generated livepatch module, see
/Linux-v5.15/arch/arc/kernel/
Dmodule.c54 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-v5.15/arch/arm/mach-hisi/
Dplatmcpm.c269 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-v5.15/Documentation/bpf/
Dllvm_reloc.rst7 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,
104 Six relocation types are supported. The following is an overview and
115 For example, ``R_BPF_64_64`` relocation type is used for ``ld_imm64`` instruction.
118 data bitsize is 32 (4 bytes). The relocation can be resolved with
123 In another case, ``R_BPF_64_ABS64`` relocation type is used for normal 64-bit data.
[all …]
/Linux-v5.15/arch/mips/vdso/
DKconfig3 # relocation in binutils > 2.25 but it will fail with older versions
4 # because that relocation is not supported for that symbol. As a result
/Linux-v5.15/tools/perf/tests/
DBuild39 perf-y += llvm.o llvm-src-base.o llvm-src-kbuild.o llvm-src-prologue.o llvm-src-relocation.o
90 $(OUTPUT)tests/llvm-src-relocation.c: tests/bpf-script-test-relocation.c tests/Build
D.gitignore5 llvm-src-relocation.c
/Linux-v5.15/arch/powerpc/platforms/8xx/
DKconfig142 bool "I2C/SPI relocation patch"
147 bool "I2C/SPI/SMC1 relocation patch"
152 bool "SMC relocation patch"
/Linux-v5.15/tools/testing/selftests/bpf/
DREADME.rst213 Clang relocation changes
217 that existing relocation types are broken into more types and
218 each new type corresponds to only one way to resolve relocation.
225 Here, ``type 2`` refers to new relocation type ``R_BPF_64_ABS64``.
/Linux-v5.15/fs/btrfs/
DMakefile29 compression.o delayed-ref.o relocation.o delayed-inode.o scrub.o \
/Linux-v5.15/Documentation/core-api/
Dthis_cpu_ops.rst71 the processor. So the relocation to the per cpu base is encoded in the
256 address relocation and a Read-Modify-Write operation in the same
268 relocation. IMHO the second form looks cleaner and has an easier time
Dlocal_ops.rst22 relocation with the ``local_t`` like semantics in a single instruction and
/Linux-v5.15/Documentation/arm/
Dmemory.rst35 CPU supports vector relocation (control
/Linux-v5.15/arch/x86/boot/
Dheader.S211 # The EFI application loader requires a relocation section
/Linux-v5.15/Documentation/gpu/
Dvgaarbiter.rst6 modern devices allow relocation of such ranges, some "Legacy" VGA devices
Ddrm-mm.rst342 others (a fairly expensive operation), and providing relocation support
Di915.rst336 This process is dubbed relocation.
/Linux-v5.15/arch/
DKconfig1205 architectures, and don't require runtime relocation on relocatable
1225 bool "Use RELR relocation packing"
1229 Store the kernel's dynamic relocations in the RELR relocation packing
/Linux-v5.15/tools/perf/
DMakefile.perf1090 $(OUTPUT)tests/llvm-src-{base,kbuild,prologue,relocation}.c \
/Linux-v5.15/arch/arm64/
DKconfig1773 which retains all relocation metadata required to relocate the
1776 Since AArch64 uses the RELA relocation format, this requires a
1777 relocation pass at runtime even if the kernel is loaded at the
/Linux-v5.15/arch/s390/
DKconfig608 This builds a kernel image that retains relocation information
/Linux-v5.15/arch/arm/boot/compressed/
Dhead.S307 add sp, sp, r1 @ apply relocation
/Linux-v5.15/arch/mips/
DKconfig2784 This builds a kernel image that retains relocation information
2796 A table of relocation data will be appended to the kernel binary

12