Searched refs:ELF (Results 1 – 11 of 11) sorted by relevance
59 #define ELF(x) ELF_BITS_XFORM(ELF_BITS, x) macro70 ELF(Sym) *symtab;72 ELF(Word) *bucket, *chain;73 ELF(Word) nbucket, nchain;76 ELF(Versym) *versym;77 ELF(Verdef) *verdef;103 ELF(Ehdr) *hdr = (ELF(Ehdr)*)base; in vdso_init_from_sysinfo_ehdr()109 ELF(Phdr) *pt = (ELF(Phdr)*)(vdso_info.load_addr + hdr->e_phoff); in vdso_init_from_sysinfo_ehdr()110 ELF(Dyn) *dyn = 0; in vdso_init_from_sysinfo_ehdr()124 dyn = (ELF(Dyn)*)(base + pt[i].p_offset); in vdso_init_from_sysinfo_ehdr()[all …]
37 These objects are associated with corresponding parts of ELF object that40 For example ``struct bpf_object`` represents ELF object itself created41 from an ELF file or from a buffer, ``struct bpf_program`` represents a42 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
17 addresses and the addresses in the ELF kallsyms symbol table (for symbols in
19 It can also be used to show the build id of the running kernel or in an ELF
59 functions. This option also generates the ELF images for each jitted function
77 is defined by header.size (see perf_event.h). Each event defines a ELF build id78 for a executable file name for a pid. An ELF build id is a unique identifier452 Define a ELF build ID for a referenced executable.
42 * uint32_t elf_mach : ELF architecture encoding (ELF e_machine value as specified in /usr/include/…
99 The BPF program can attach to various perf events based on the ELF section
121 1. Each callable function must be annotated as such with the ELF131 be annotated as an ELF function. The ENDPROC macro shouldn't be used191 its ELF function annotation by changing ENDPROC to END, and instead
114 By default bpftool will create new maps as declared in the ELF118 to be replaced in the ELF file counting from 0, while *NAME*
56 When specifying *FILE*, an ELF file is expected, containing