| /linux/arch/sh/kernel/ |
| 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/ |
| A D | module-elf-format.rst | 30 table, symbol table, and relocation section indices, ELF information is
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.
93 text section of a function) to which the relocation(s) apply. It is
94 also possible for a livepatch module to have no livepatch relocation
101 access the relocation section and apply the relocations.
107 3.1 Livepatch relocation section format
138 **Livepatch relocation section names:**
[all …]
|
| A D | livepatch.rst | 238 relocation section in the generated livepatch module, see
|
| /linux/arch/arc/kernel/ |
| 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/ |
| 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/devicetree/bindings/remoteproc/ |
| A D | qcom,pil-info.yaml | 7 title: Qualcomm peripheral image loader relocation info
13 The Qualcomm peripheral image loader relocation memory region, in IMEM, is
14 used for communicating remoteproc relocation information to post mortem
|
| /linux/Documentation/bpf/ |
| 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
63 For example, the first relocation corresponds to the first instruction
106 Six relocation types are supported. The following is an overview and
120 data bitsize is 32 (4 bytes). The relocation can be resolved with
127 bitsize is 64 (8 bytes). The relocation can be resolved with
207 relocation below in ``.data`` section with command
251 of CO-RE specific relocation records. These relocation records are not
362 associated with this relocation;
368 String interpretation depends on specific relocation kind:
[all …]
|
| /linux/Documentation/devicetree/bindings/arm/hisilicon/controller/ |
| A D | hip04-bootwrapper.yaml | 25 [2]: relocation physical address
26 [3]: relocation size
|
| /linux/arch/powerpc/platforms/8xx/ |
| A D | Kconfig | 143 bool "I2C/SPI relocation patch"
148 bool "I2C/SPI/SMC1 relocation patch"
153 bool "SMC relocation patch"
|
| /linux/Documentation/devicetree/bindings/sram/ |
| A D | qcom,imem.yaml | 54 description: Peripheral image loader relocation region
|
| /linux/tools/testing/selftests/bpf/ |
| 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/fs/btrfs/ |
| A D | Makefile | 31 compression.o delayed-ref.o relocation.o delayed-inode.o scrub.o \
|
| /linux/Documentation/core-api/ |
| 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
|
| A D | local_ops.rst | 22 relocation with the ``local_t`` like semantics in a single instruction and
|
| /linux/Documentation/arch/arm/ |
| A D | memory.rst | 35 CPU supports vector relocation (control
|
| /linux/Documentation/gpu/ |
| A D | vgaarbiter.rst | 6 modern devices allow relocation of such ranges, some "Legacy" VGA devices
|
| A D | drm-mm.rst | 339 others (a fairly expensive operation), and providing relocation support
|
| A D | i915.rst | 342 This process is dubbed relocation.
|
| /linux/arch/riscv/ |
| A D | Kconfig | 944 which retains all relocation metadata required to relocate the
947 Since RISCV uses the RELA relocation format, this requires a
948 relocation pass at runtime even if the kernel is loaded at the
|
| /linux/Documentation/bpf/libbpf/ |
| A D | libbpf_overview.rst | 162 recorded BTF type and relocation information and matching them to BTF
|
| /linux/arch/ |
| A D | Kconfig | 1488 architectures, and don't require runtime relocation on relocatable
1508 bool "Use RELR relocation packing"
1512 Store the kernel's dynamic relocations in the RELR relocation packing
|
| /linux/arch/loongarch/ |
| A D | Kconfig | 623 which retains all relocation metadata required, so as to relocate
|
| /linux/tools/perf/ |
| A D | Makefile.perf | 1282 $(OUTPUT)tests/llvm-src-{base,kbuild,prologue,relocation}.c \
|
| /linux/arch/arm64/ |
| A D | Kconfig | 2259 which retains all relocation metadata required to relocate the
2262 Since AArch64 uses the RELA relocation format, this requires a
2263 relocation pass at runtime even if the kernel is loaded at the
|
| /linux/arch/s390/ |
| A D | Kconfig | 611 This builds a kernel image that retains relocation information
|