Searched refs:kprobe (Results 1 – 15 of 15) sorted by relevance
4 82 kprobe 0 1 Oct19/23:52 map_perf_test5 83 kprobe 0 1 Oct19/23:52 map_perf_test6 84 kprobe 0 1 Oct19/23:52 map_perf_test7 85 kprobe 0 1 Oct19/23:52 map_perf_test8 86 kprobe 0 4 Oct19/23:52 map_perf_test9 87 kprobe 0 1 Oct19/23:52 map_perf_test10 88 kprobe 0 1 Oct19/23:52 map_perf_test11 89 kprobe 0 1 Oct19/23:52 map_perf_test16 86 kprobe 0 4 Oct19/23:52 map_perf_test
49 older ftrace-based kprobe tool as a workarond. This is from my perf-tools52 # ./perf-tools/bin/kprobe -s 'p:kmem_cache_alloc name=+0(+96(%di)):string' 'name == "kmalloc-4096' …53 Tracing kprobe kmem_cache_alloc. Ctrl-C to end.54 …kprobe-3892 [002] d... 7888274.478331: kmem_cache_alloc: (kmem_cache_alloc+0x0/0x1b0) name="kmall…55 kprobe-3892 [002] d... 7888274.478333: <stack trace>62 …kprobe-3892 [002] d... 7888274.478340: kmem_cache_alloc: (kmem_cache_alloc+0x0/0x1b0) name="kmall…63 kprobe-3892 [002] d... 7888274.478341: <stack trace>70 …kprobe-3892 [002] d... 7888274.478345: kmem_cache_alloc: (kmem_cache_alloc+0x0/0x1b0) name="kmall…71 kprobe-3892 [002] d... 7888274.478346: <stack trace>78 …kprobe-3892 [002] d... 7888274.478350: kmem_cache_alloc: (kmem_cache_alloc+0x0/0x1b0) name="kmall…[all …]
26 4058 fileslower kprobe 4 46 4058 fileslower kprobe 4
42 How this works: the function entry and return are traced using the kernel kprobe
101 Here you can see that arming the kprobe to which our eBPF program is attached
30 local trace_start = bpf.kprobe('myprobe:blk_start_request', function (ptregs)33 local trace_end = bpf.kprobe('myprobe2:blk_account_io_completion', function (ptregs)
26 local probe = bpf.kprobe('myprobe:sys_write', function (ptregs)
1393 * SEC("kprobe/sys_open")
3 #include "kprobe.b"
33 …D ${TEST_WRAPPER} py_trace1 sudo ${CMAKE_CURRENT_SOURCE_DIR}/test_trace1.py test_trace1.b kprobe.b)
21 # ./ftracetest test.d/kprobe/
9 define i64 @"kprobe:blk_update_request"(i8* %0) local_unnamed_addr section "s_kprobe:blk_update_req…
97 1. ```b.attach_kprobe(event=b.get_syscall_fnname("clone"), fn_name="hello")```: Creates a kprobe fo…229 …q)```: This function will later be attached to kprobes. The arguments to kprobe functions are ```s…385 …ix means the rest will be treated as a kernel function name that will be instrumented using kprobe.386 - ```struct pt_regs *ctx, struct request *req```: Arguments to kprobe. The ```ctx``` is registers a…671 context that is passed by the kprobe infrastructure. The prototype of the args
107 ```kprobe__``` is a special prefix that creates a kprobe (dynamic tracing of a kernel function call…119 This instruments the tcp_v4_connect() kernel function using a kprobe, with the following arguments:414 When used in a program attached to a function entry kprobe, causes the
1599 kprobe = function(tp, prog, retprobe, pid, cpu, group_fd) function