| /kernel/linux/linux-5.10/tools/testing/selftests/vDSO/ |
| D | parse_vdso.c | 37 #define ELF(x) ELF_BITS_XFORM(ELF_BITS, x) macro
48 ELF(Sym) *symtab;
50 ELF(Word) *bucket, *chain;
51 ELF(Word) nbucket, nchain;
54 ELF(Versym) *versym;
55 ELF(Verdef) *verdef;
81 ELF(Ehdr) *hdr = (ELF(Ehdr)*)base; in vdso_init_from_sysinfo_ehdr()
87 ELF(Phdr) *pt = (ELF(Phdr)*)(vdso_info.load_addr + hdr->e_phoff); in vdso_init_from_sysinfo_ehdr()
88 ELF(Dyn) *dyn = 0; in vdso_init_from_sysinfo_ehdr()
102 dyn = (ELF(Dyn)*)(base + pt[i].p_offset); in vdso_init_from_sysinfo_ehdr()
[all …]
|
| /kernel/linux/linux-5.10/arch/sparc/vdso/ |
| D | vdso2c.h | 20 ELF(Shdr) *symtab_hdr = NULL, *strtab_hdr; in BITSFUNC()
21 ELF(Ehdr) *hdr = (ELF(Ehdr) *)raw_addr; in BITSFUNC()
22 ELF(Dyn) *dyn = 0, *dyn_end = 0; in BITSFUNC()
25 ELF(Phdr) *pt = (ELF(Phdr) *)(raw_addr + GET_BE(&hdr->e_phoff)); in BITSFUNC()
66 ELF(Shdr) *sh = raw_addr + GET_BE(&hdr->e_shoff) + in BITSFUNC()
84 ELF(Sym) *sym = raw_addr + GET_BE(&symtab_hdr->sh_offset) + in BITSFUNC()
|
| /kernel/linux/linux-5.10/fs/ |
| D | Kconfig.binfmt | 6 bool "Kernel support for ELF binaries"
11 ELF (Executable and Linkable Format) is a format for libraries and
13 systems. Saying Y here will enable your kernel to run ELF binaries
14 and enlarge it by about 13 KB. ELF support under Linux has now all
19 executables are distributed solely in ELF format. You definitely
22 Information about ELF is contained in the ELF HOWTO available from
26 here, you still can't run any ELF binaries (they just crash), then
27 you'll have to install the newest ELF runtime libraries, including
46 bool "Kernel support for FDPIC ELF binaries"
51 ELF FDPIC binaries are based on ELF, but allow the individual load
[all …]
|
| /kernel/linux/linux-5.10/arch/x86/entry/vdso/ |
| D | vdso2c.h | 15 ELF(Ehdr) *hdr = (ELF(Ehdr) *)raw_addr; in BITSFUNC()
17 ELF(Shdr) *symtab_hdr = NULL, *strtab_hdr, *secstrings_hdr, in BITSFUNC()
19 ELF(Dyn) *dyn = 0, *dyn_end = 0; in BITSFUNC()
23 ELF(Phdr) *pt = (ELF(Phdr) *)(raw_addr + GET_LE(&hdr->e_phoff)); in BITSFUNC()
72 ELF(Shdr) *sh = raw_addr + GET_LE(&hdr->e_shoff) + in BITSFUNC()
92 ELF(Sym) *sym = raw_addr + GET_LE(&symtab_hdr->sh_offset) + in BITSFUNC()
|
| /kernel/linux/linux-5.10/arch/mips/vdso/ |
| D | genvdso.h | 9 const ELF(Ehdr) *ehdr = vdso; in FUNC()
11 ELF(Shdr) *shdr; in FUNC()
60 const ELF(Ehdr) *ehdr = vdso; in FUNC()
62 ELF(Shdr) *shdr; in FUNC()
63 const ELF(Sym) *sym; in FUNC()
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-kernel-vmcoreinfo | 8 Shows physical address and size of vmcoreinfo ELF note.
10 second value contains the size of note in hex. This ELF
12 space as part of ELF note in /proc/vmcore file. This note
|
| /kernel/linux/linux-5.10/Documentation/features/vm/ELF-ASLR/ |
| D | arch-support.txt | 2 # Feature name: ELF-ASLR
4 # description: arch randomizes the stack, heap and binary images of ELF binaries
|
| /kernel/linux/linux-5.10/Documentation/powerpc/ |
| D | syscall64-abi.rst | 13 If PPC_FEATURE2_SCV appears in the AT_HWCAP2 ELF auxiliary vector, the
17 syscall calling sequence\ [1]_ matches the Power Architecture 64-bit ELF ABI
49 Register preservation rules match the ELF ABI calling sequence with the
53 | For the sc instruction, differences with the ELF ABI |
62 | For the scv 0 instruction, differences with the ELF ABI |
84 behavior depends on the presence of PPC_FEATURE2_HTM_NOSC in the AT_HWCAP2 ELF
|
| D | elfnote.rst | 2 ELF Note PowerPC Namespace
5 The PowerPC namespace in an ELF Note of the kernel binary is used to store
|
| D | firmware-assisted-dump.rst | 17 in the ELF format in the same way as kdump. This helps us reuse the
84 of memory, which holds the previous crashed kernel dump in ELF
161 | | |///|////| DUMP | HDR | ELF |////| |
190 | | |///|////| DUMP | HDR | ELF |////| |
208 in ELF format. Hence the existing kdump infrastructure (kdump scripts)
357 in the scratch area before the ELF core header. The idea of introducing
359 kernel which will help second kernel to populate ELF core header with
|
| /kernel/linux/linux-5.10/tools/lib/bpf/ |
| D | README.rst | 37 These objects are associated with corresponding parts of ELF object that
40 For example ``struct bpf_object`` represents ELF object itself created
41 from an ELF file or from a buffer, ``struct bpf_program`` represents a
42 program in ELF object and ``struct bpf_map`` is a map.
49 purpose of the function to open ELF file and create ``bpf_object`` from
|
| /kernel/linux/linux-5.10/arch/alpha/ |
| D | Kconfig.debug | 19 ELF headers to determine where to transfer control. Unfortunately,
21 address rather than examining the ELF headers, and the result is a
|
| /kernel/linux/linux-5.10/fs/proc/ |
| D | Kconfig | 37 Provides a virtual ELF core file of the live kernel. This can
38 be read with gdb and other ELF tools. No modifications can be
46 Exports the dump image of crashed kernel in ELF format.
61 as ELF notes to /proc/vmcore. You can still disable device
|
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| D | perf-kallsyms.txt | 17 addresses and the addresses in the ELF kallsyms symbol table (for symbols in
|
| D | perf-buildid-list.txt | 19 It can also be used to show the build id of the running kernel or in an ELF
|
| D | perf-inject.txt | 63 functions. This option also generates the ELF images for each jitted function
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | highuid.rst | 71 - The ELF core dump format only supports 16-bit UIDs on arm, i386, m68k,
73 require adding a new ELF section.
|
| /kernel/linux/linux-5.10/scripts/ |
| D | check_extable.sh | 7 file ${obj} | grep -q ELF || (echo "${obj} is not and ELF file." 1>&2 ; exit 0)
|
| /kernel/linux/linux-5.10/kernel/configs/ |
| D | xen.config | 17 # You want TCP/IP and ELF binaries right?
|
| /kernel/linux/linux-5.10/Documentation/mips/ |
| D | booting.rst | 7 kernel image. Other bootloaders will jump to the ELF start address.
|
| /kernel/linux/linux-5.10/Documentation/bpf/ |
| D | btf.rst | 20 * BTF ELF file format
23 verifies the BTF info before using it. The ELF file format is a user space
24 contract between ELF file and libbpf loader.
372 :ref:`BTF_Ext_Section` (ELF) or in the arguments to :ref:`BPF_Prog_Load`
419 variable in ELF sections 1
526 value types for the map. During ELF parsing, libbpf is able to extract
619 4. ELF File Format Interface
667 func_info for each specific ELF section.::
689 ``bpf_line_info->insn_off`` is different between kernel API and ELF API. For
691 bpf_insn``. For ELF API, the ``insn_off`` is the byte offset from the
|
| /kernel/linux/linux-5.10/tools/bpf/bpftool/Documentation/ |
| D | bpftool-struct_ops.rst | 52 the ELF section ".struct_ops" will be registered to
|
| /kernel/linux/linux-5.10/Documentation/ABI/stable/ |
| D | vdso | 8 maps an ELF DSO into that program's address space. This DSO is called
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/kdump/ |
| D | kdump.rst | 43 encoded in the ELF format, and stored in a reserved area of memory
44 before a crash. The physical address of the start of the ELF header is
46 parameter. Optionally the size of the ELF header can also be passed
51 /proc/vmcore. This exports the dump as an ELF-format file that you can
415 * By default, the ELF headers are stored in ELF64 format to support
446 * For s390x there are two kdump modes: If a ELF header is specified with
|
| /kernel/linux/linux-5.10/Documentation/arm64/ |
| D | elf_hwcaps.rst | 2 ARM64 ELF hwcaps
5 This document describes the usage and semantics of the arm64 ELF hwcaps.
|