| /tools/perf/arch/powerpc/util/ |
| D | sym-handling.c | 94 if (pev->point.offset || !map || !sym) in arch__fix_tev_from_maps()
98 if (!pev->uprobes && pev->point.retprobe) { in arch__fix_tev_from_maps()
108 tev->point.offset += PPC64LE_LEP_OFFSET; in arch__fix_tev_from_maps()
111 tev->point.address += lep_offset; in arch__fix_tev_from_maps()
113 tev->point.offset += lep_offset; in arch__fix_tev_from_maps()
134 if (map->unmap_ip(map, sym->start) == tev->point.address) { in arch__post_process_probe_trace_events()
|
| /tools/bpf/bpftool/Documentation/ |
| D | bpftool-perf.rst | 32 followed by bpf program id, attachment information, and attachment point.
33 The attachment point for raw_tracepoint/tracepoint is the trace probe name.
34 The attachment point for k[ret]probe is either symbol name and offset,
36 The attachment point for u[ret]probe is the file name and the file offset.
|
| D | bpftool-net.rst | 64 **xdpdrv** - Native XDP. runs earliest point in driver's receive path;
|
| D | bpftool-map.rst | 222 entry-point program. Below is an example for this use case: we load a program
|
| /tools/perf/util/ |
| D | probe-event.c | 427 memcpy(tmp, &pev->point, sizeof(*tmp)); in get_alternative_probe_event()
428 memset(&pev->point, 0, sizeof(pev->point)); in get_alternative_probe_event()
429 ret = find_alternative_probe_point(dinfo, tmp, &pev->point, pev->target, in get_alternative_probe_event()
432 memcpy(&pev->point, tmp, sizeof(*tmp)); in get_alternative_probe_event()
731 ret = post_process_probe_trace_point(&tevs[i].point, in post_process_offline_probe_trace_events()
757 tevs[i].point.address -= stext; in add_exec_to_probe_trace_events()
758 tevs[i].point.module = strdup(exec); in add_exec_to_probe_trace_events()
759 if (!tevs[i].point.module) { in add_exec_to_probe_trace_events()
790 ret = post_process_probe_trace_point(&tevs[i].point, in post_process_module_probe_trace_events()
794 tevs[i].point.module = in post_process_module_probe_trace_events()
[all …]
|
| D | probe-event.h | 58 struct probe_trace_point point; /* Trace point */ member
96 struct perf_probe_point point; /* Probe point */ member
123 struct probe_trace_point point; /* Actual probepoint */ member
|
| D | probe-finder.c | 799 .function = pf->pev->point.function, in find_best_scope()
834 if (pf->pev->point.function) { in verify_representive_line()
838 && die_match_name(&die_mem, pf->pev->point.function) in verify_representive_line()
976 pf->pev->point.lazy_line); in find_probe_point_lazy()
987 struct perf_probe_point *pp = &pf->pev->point; in skip_prologue()
1020 struct perf_probe_point *pp = &pf->pev->point; in probe_point_inline_cb()
1060 struct perf_probe_point *pp = &pf->pev->point; in probe_point_search_cb()
1156 struct perf_probe_point *pp = &pf->pev->point; in debuginfo__find_probe_location()
1336 if (tf->pf.addr == tf->tevs[i].point.address) in trace_event_finder_overlap()
1347 struct perf_probe_point *pp = &pf->pev->point; in add_probe_trace_event()
[all …]
|
| D | probe-file.c | 681 if (!tevs[i].point.symbol) in probe_cache__add_entry()
|
| /tools/testing/selftests/tc-testing/ |
| D | TODO.txt | 17 will attempt to run a function at every hook point. Could be
20 require action at a specific point, no penalty will be paid for
|
| /tools/perf/pmu-events/ |
| D | README | 26 such as Pipelining, Cache, Memory, Floating-point etc. All events for a topic
28 the topic. Eg: "Floating-point.json".
127 it supports). Multiple CPUIDS can point to the same
|
| /tools/perf/Documentation/ |
| D | perf-probe.txt | 86 Show available local variables at given probe point. The argument
176 …attern (see LAZY MATCHING). Note that ';PTN' must be the end of the probe point definition. In ad…
177 It is also possible to specify a probe point by the source line number or lazy matching by using 'S…
178 'ARG' specifies the arguments of this probe point, (see PROBE ARGUMENT).
200 …variables (including function parameters) which can access at given probe point. '$params' is expa…
234 This provides some sort of flexibility and robustness to probe point definitions against minor code…
|
| D | perf-inject.txt | 16 point the processing code can inject other events into the event stream - in
|
| D | android.txt | 10 Set the NDK variable to point to the path where you installed the NDK:
|
| D | perf-script.txt | 182 At this point usage is displayed, and perf-script exits.
235 period (since the last sample), not just for the sample point.
|
| D | perf-list.txt | 188 For accessing trace point events perf needs to have read access to
|
| D | perf-top.txt | 309 phase is over, i.e. insert a perf probe at that point and use the above
|
| D | perf-trace.txt | 199 beyond the specified depth will be ignored. Note that at this point
|
| /tools/thermal/tmon/ |
| D | README | 16 links, trip point bindings, and device instances. To traverse such
|
| /tools/perf/arch/powerpc/entry/syscalls/ |
| D | syscall.tbl | 6 # <number> <abi> <name> <entry point> <compat entry point>
|
| /tools/perf/ |
| D | builtin-probe.c | 373 tev->point.module, false); in perf_add_probe_events()
|
| D | Makefile.config | 450 …msg := $(warning Old libdw.h, finding variables at given 'perf probe' point will not work, install…
1022 …$(warning No alternatives command found, you need to set JDIR= to point to the root of your Java d…
|
| /tools/memory-model/ |
| D | README | 181 Starting point for someone new to Linux-kernel concurrency.
|
| /tools/perf/arch/x86/entry/syscalls/ |
| D | syscall_64.tbl | 5 # <number> <abi> <name> <entry point>
|
| /tools/usb/usbip/ |
| D | INSTALL | 37 some point `config.cache' contains results you don't want to keep, you
|
| /tools/memory-model/Documentation/ |
| D | litmus-tests.txt | 483 at some particular point in a given process's execution? One approach
655 If the "filter" clause were to check each variable at each point in the
1053 pointer types. There is no support for floating-point types,
|