Home
last modified time | relevance | path

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

12

/linux/arch/sh/kernel/
A 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/Documentation/livepatch/
A Dmodule-elf-format.rst30 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 Dlivepatch.rst238 relocation section in the generated livepatch module, see
/linux/arch/arm/mach-hisi/
A 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/arch/arc/kernel/
A 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/Documentation/bpf/
A 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
118 data bitsize is 32 (4 bytes). The relocation can be resolved with
125 bitsize is 64 (8 bytes). The relocation can be resolved with
205 relocation below in ``.data`` section with command
[all …]
/linux/Documentation/devicetree/bindings/remoteproc/
A Dqcom,pil-info.yaml7 title: Qualcomm peripheral image loader relocation info binding
13 The Qualcomm peripheral image loader relocation memory region, in IMEM, is
14 used for communicating remoteproc relocation information to post mortem
/linux/Documentation/devicetree/bindings/arm/hisilicon/controller/
A Dhip04-bootwrapper.yaml24 [2]: relocation physical address
25 [3]: relocation size
/linux/arch/mips/vdso/
A 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/tools/perf/tests/
A 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
A D.gitignore5 llvm-src-relocation.c
/linux/arch/powerpc/platforms/8xx/
A DKconfig142 bool "I2C/SPI relocation patch"
147 bool "I2C/SPI/SMC1 relocation patch"
152 bool "SMC relocation patch"
/linux/tools/testing/selftests/bpf/
A DREADME.rst227 Clang relocation changes
231 that existing relocation types are broken into more types and
232 each new type corresponds to only one way to resolve relocation.
239 Here, ``type 2`` refers to new relocation type ``R_BPF_64_ABS64``.
/linux/fs/btrfs/
A DMakefile29 compression.o delayed-ref.o relocation.o delayed-inode.o scrub.o \
/linux/Documentation/core-api/
A 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
A Dlocal_ops.rst22 relocation with the ``local_t`` like semantics in a single instruction and
/linux/Documentation/arm/
A Dmemory.rst35 CPU supports vector relocation (control
/linux/arch/x86/boot/
A Dheader.S211 # The EFI application loader requires a relocation section
/linux/arch/arm64/kernel/
A Dvmlinux.lds192 <= 0x00001000, "kexec relocation code is too big or misaligned")
/linux/Documentation/gpu/
A Dvgaarbiter.rst6 modern devices allow relocation of such ranges, some "Legacy" VGA devices
A Ddrm-mm.rst339 others (a fairly expensive operation), and providing relocation support
A Di915.rst333 This process is dubbed relocation.
/linux/arch/
A DKconfig1223 architectures, and don't require runtime relocation on relocatable
1243 bool "Use RELR relocation packing"
1247 Store the kernel's dynamic relocations in the RELR relocation packing
/linux/tools/perf/
A DMakefile.perf1098 $(OUTPUT)tests/llvm-src-{base,kbuild,prologue,relocation}.c \
/linux/arch/arm64/
A DKconfig1899 which retains all relocation metadata required to relocate the
1902 Since AArch64 uses the RELA relocation format, this requires a
1903 relocation pass at runtime even if the kernel is loaded at the

Completed in 41 milliseconds

12