| /linux/tools/testing/selftests/vDSO/ |
| A D | parse_vdso.c | 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()
112 ELF(Word) *hash = 0; in vdso_init_from_sysinfo_ehdr()
130 hash = (ELF(Word) *) in vdso_init_from_sysinfo_ehdr()
[all …]
|
| /linux/fs/ |
| A 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
46 bool "Kernel support for FDPIC ELF binaries"
51 ELF FDPIC binaries are based on ELF, but allow the individual load
65 bool "Write ELF core dumps with partial segments"
69 ELF core dump files describe each memory mapping of the crashed
[all …]
|
| /linux/arch/sparc/vdso/ |
| A 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()
|
| /linux/arch/x86/entry/vdso/ |
| A D | vdso2c.h | 27 FILE *outfile, ELF(Shdr) *sec, const char *name) in BITSFUNC()
50 ELF(Ehdr) *hdr = (ELF(Ehdr) *)raw_addr; in BITSFUNC()
52 ELF(Shdr) *symtab_hdr = NULL, *strtab_hdr, *secstrings_hdr, in BITSFUNC()
54 ELF(Dyn) *dyn = 0, *dyn_end = 0; in BITSFUNC()
58 ELF(Phdr) *pt = (ELF(Phdr) *)(raw_addr + GET_LE(&hdr->e_phoff)); in BITSFUNC()
107 ELF(Shdr) *sh = raw_addr + GET_LE(&hdr->e_shoff) + in BITSFUNC()
129 ELF(Sym) *sym = raw_addr + GET_LE(&symtab_hdr->sh_offset) + in BITSFUNC()
|
| /linux/arch/mips/vdso/ |
| A 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()
|
| /linux/Documentation/ABI/testing/ |
| A 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
|
| /linux/Documentation/powerpc/ |
| A 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 some
52 For the sc instruction, the differences from the ELF ABI are as follows:
70 For the scv 0 instruction, the differences from the ELF ABI are as follows:
97 behavior depends on the presence of PPC_FEATURE2_HTM_NOSC in the AT_HWCAP2 ELF
|
| A D | elfnote.rst | 2 ELF Note PowerPC Namespace
5 The PowerPC namespace in an ELF Note of the kernel binary is used to store
|
| A 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
|
| /linux/Documentation/features/vm/ELF-ASLR/ |
| A D | arch-support.txt | 2 # Feature name: ELF-ASLR
4 # description: arch randomizes the stack, heap and binary images of ELF binaries
|
| /linux/Documentation/bpf/libbpf/ |
| A D | libbpf_naming_convention.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
168 * bytes of an ELF's BTF section
|
| /linux/fs/proc/ |
| A 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
|
| /linux/arch/alpha/ |
| A 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
|
| /linux/Documentation/x86/ |
| A D | elf_auxvec.rst | 4 x86-specific ELF Auxiliary Vectors
12 ELF Auxiliary vectors enable the kernel to efficiently provide
|
| /linux/Documentation/translations/zh_TW/arm64/ |
| A D | elf_hwcaps.rst | 11 ARM64 ELF hwcaps
14 這篇文檔描述了 arm64 ELF hwcaps 的用法和語義。
|
| /linux/Documentation/translations/zh_CN/arm64/ |
| A D | elf_hwcaps.rst | 8 ARM64 ELF hwcaps
11 这篇文档描述了 arm64 ELF hwcaps 的用法和语义。
|
| /linux/Documentation/translations/zh_CN/mips/ |
| A D | booting.rst | 17 bootloaders将跳转到ELF的开始地址处。两种方案都支持的；因为
|
| /linux/Documentation/admin-guide/ |
| A 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.
|
| /linux/tools/perf/Documentation/ |
| A D | perf-kallsyms.txt | 17 addresses and the addresses in the ELF kallsyms symbol table (for symbols in
|
| A D | perf-buildid-list.txt | 19 It can also be used to show the build id of the running kernel or in an ELF
|
| /linux/Documentation/bpf/ |
| A 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.
374 :ref:`BTF_Ext_Section` (ELF) or in the arguments to :ref:`BPF_Prog_Load`
421 variable in ELF sections 1
566 value types for the map. During ELF parsing, libbpf is able to extract
659 4. ELF File Format Interface
707 func_info for each specific ELF section.::
729 ``bpf_line_info->insn_off`` is different between kernel API and ELF API. For
731 bpf_insn``. For ELF API, the ``insn_off`` is the byte offset from the
|
| /linux/scripts/ |
| A D | check_extable.sh | 7 file ${obj} | grep -q ELF || (echo "${obj} is not an ELF file." 1>&2 ; exit 0)
|
| /linux/kernel/configs/ |
| A D | xen.config | 17 # You want TCP/IP and ELF binaries right?
|
| /linux/Documentation/mips/ |
| A D | booting.rst | 7 kernel image. Other bootloaders will jump to the ELF start address.
|
| /linux/tools/bpf/bpftool/Documentation/ |
| A D | bpftool-struct_ops.rst | 52 the ELF section ".struct_ops" will be registered to
|