Home
last modified time | relevance | path

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

/linux-4.1.27/kernel/events/
Duprobes.c65 struct uprobe { struct
90 struct uprobe *uprobe; argument
369 static int match_uprobe(struct uprobe *l, struct uprobe *r) in match_uprobe()
386 static struct uprobe *__find_uprobe(struct inode *inode, loff_t offset) in __find_uprobe()
388 struct uprobe u = { .inode = inode, .offset = offset }; in __find_uprobe()
390 struct uprobe *uprobe; in __find_uprobe() local
394 uprobe = rb_entry(n, struct uprobe, rb_node); in __find_uprobe()
395 match = match_uprobe(&u, uprobe); in __find_uprobe()
397 atomic_inc(&uprobe->ref); in __find_uprobe()
398 return uprobe; in __find_uprobe()
[all …]
/linux-4.1.27/Documentation/trace/
Duprobetracer.txt17 However unlike kprobe-event tracer, the uprobe event interface expects the
22 p[:[GRP/]EVENT] PATH:OFFSET [FETCHARGS] : Set a uprobe
23 r[:[GRP/]EVENT] PATH:OFFSET [FETCHARGS] : Set a return uprobe (uretprobe)
24 -:[GRP/]EVENT : Clear uprobe or uretprobe event
70 * Add a probe as a new uprobe event, write a new definition to uprobe_events
71 as below: (sets a uprobe at an offset of 0x4245c0 in the executable /bin/bash)
101 0x00400000. Hence the command to uprobe would be:
157 Output shows us uprobe was triggered for a pid 24842 with ip being 0x446420
/linux-4.1.27/include/linux/
Duprobes.h88 struct uprobe *active_uprobe;
/linux-4.1.27/tools/perf/util/
Dprobe-event.c557 bool uprobe) in post_process_probe_trace_events() argument
563 if (uprobe) in post_process_probe_trace_events()