Home
last modified time | relevance | path

Searched refs:uprobe (Results 1 – 10 of 10) sorted by relevance

/Linux-v5.4/kernel/events/
Duprobes.c55 struct uprobe { struct
82 struct uprobe *uprobe; argument
293 delayed_uprobe_check(struct uprobe *uprobe, struct mm_struct *mm) in delayed_uprobe_check() argument
298 if (du->uprobe == uprobe && du->mm == mm) in delayed_uprobe_check()
303 static int delayed_uprobe_add(struct uprobe *uprobe, struct mm_struct *mm) in delayed_uprobe_add() argument
307 if (delayed_uprobe_check(uprobe, mm)) in delayed_uprobe_add()
314 du->uprobe = uprobe; in delayed_uprobe_add()
328 static void delayed_uprobe_remove(struct uprobe *uprobe, struct mm_struct *mm) in delayed_uprobe_remove() argument
333 if (!uprobe && !mm) in delayed_uprobe_remove()
339 if (uprobe && du->uprobe != uprobe) in delayed_uprobe_remove()
[all …]
/Linux-v5.4/Documentation/trace/
Duprobetracer.rst18 However unlike kprobe-event tracer, the uprobe event interface expects the
29 p[:[GRP/]EVENT] PATH:OFFSET [FETCHARGS] : Set a uprobe
30 r[:[GRP/]EVENT] PATH:OFFSET [FETCHARGS] : Set a return uprobe (uretprobe)
31 -:[GRP/]EVENT : Clear uprobe or uretprobe event
56 (\*3) Unlike kprobe event, "u" prefix will just be ignored, becuse uprobe
85 * Add a probe as a new uprobe event, write a new definition to uprobe_events
86 as below (sets a uprobe at an offset of 0x4245c0 in the executable /bin/bash)::
116 0x00400000. Hence the command to uprobe would be::
182 Output shows us uprobe was triggered for a pid 24842 with ip being 0x446420
/Linux-v5.4/include/linux/
Duprobes.h76 struct uprobe *active_uprobe;
84 struct uprobe *uprobe; member
/Linux-v5.4/tools/bpf/bpftool/Documentation/
Dbpftool-perf.rst70 pid 21800 fd 5: prog_id 9 uprobe filename /home/yhs/a.out offset 1159
80 {"pid":21800,"fd":5,"prog_id":9,"fd_type":"uprobe","filename":"/home/yhs/a.out","offset":1159}]
/Linux-v5.4/tools/perf/util/
Dprobe-file.c34 static void print_open_warning(int err, bool uprobe) in print_open_warning() argument
41 if (uprobe) in print_open_warning()
48 uprobe ? 'u' : 'k', config); in print_open_warning()
53 uprobe ? 'u' : 'k', in print_open_warning()
Dprobe-event.c799 bool uprobe, struct debuginfo *dinfo) in post_process_probe_trace_events() argument
803 if (uprobe) in post_process_probe_trace_events()
2738 static int __open_probe_file_and_namelist(bool uprobe, in __open_probe_file_and_namelist() argument
2743 fd = probe_file__open(PF_FL_RW | (uprobe ? PF_FL_UPROBE : 0)); in __open_probe_file_and_namelist()
/Linux-v5.4/tools/perf/Documentation/
Dperf-buildid-cache.txt74 used when creating a uprobe for a process that resides in a
Dperf-probe.txt135 used when creating a uprobe for a process that resides in a
173 …p name by 'GROUP', if omitted, set 'probe' is used for kprobe and 'probe_<bin>' is used for uprobe.
281 Add a uprobe to a target process running in a different mount namespace
/Linux-v5.4/tools/lib/bpf/
Dlibbpf.c5013 static int perf_event_open_probe(bool uprobe, bool retprobe, const char *name, in perf_event_open_probe() argument
5020 type = uprobe ? determine_uprobe_perf_type() in perf_event_open_probe()
5024 uprobe ? "uprobe" : "kprobe", in perf_event_open_probe()
5029 int bit = uprobe ? determine_uprobe_retprobe_bit() in perf_event_open_probe()
5034 uprobe ? "uprobe" : "kprobe", in perf_event_open_probe()
5054 uprobe ? "uprobe" : "kprobe", in perf_event_open_probe()
/Linux-v5.4/kernel/trace/
DKconfig523 This allows the user to attach BPF programs to kprobe, uprobe, and