| /kernel/linux/linux-4.19/tools/perf/Documentation/ |
| D | perf-probe.txt | 1 perf-probe(1)
6 perf-probe - Define new dynamic tracepoints
11 'perf probe' [options] --add='PROBE' [...]
13 'perf probe' [options] PROBE
15 'perf probe' [options] --del='[GROUP:]EVENT' [...]
17 'perf probe' --list[=[GROUP:]EVENT]
19 'perf probe' [options] --line='LINE'
21 'perf probe' [options] --vars='PROBEPOINT'
23 'perf probe' [options] --funcs
25 'perf probe' [options] --definition='PROBE' [...]
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| D | perf-probe.txt | 1 perf-probe(1)
6 perf-probe - Define new dynamic tracepoints
11 'perf probe' [options] --add='PROBE' [...]
13 'perf probe' [options] PROBE
15 'perf probe' [options] --del='[GROUP:]EVENT' [...]
17 'perf probe' --list[=[GROUP:]EVENT]
19 'perf probe' [options] --line='LINE'
21 'perf probe' [options] --vars='PROBEPOINT'
23 'perf probe' [options] --funcs
25 'perf probe' [options] --definition='PROBE' [...]
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | kprobes.txt | 16 6. Probe Overhead
37 any instruction in the kernel. A return probe fires when a specified
44 the probe is to be inserted and what handler is to be called when
45 the probe is hit.
86 Since kprobes can probe into a running kernel code, it can change the
106 How Does a Return Probe Work?
111 probe is hit, Kprobes saves a copy of the return address, and replaces
117 passes to the trampoline and that probe is hit. Kprobes' trampoline
138 zero when the return probe is registered, and is incremented every
140 object available for establishing the return probe.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/trace/ |
| D | kprobes.rst | 16 6. Probe Overhead
38 any instruction in the kernel. A return probe fires when a specified
45 the probe is to be inserted and what handler is to be called when
46 the probe is hit.
87 Since kprobes can probe into a running kernel code, it can change the
107 How Does a Return Probe Work?
112 probe is hit, Kprobes saves a copy of the return address, and replaces
118 passes to the trampoline and that probe is hit. Kprobes' trampoline
139 zero when the return probe is registered, and is incremented every
141 object available for establishing the return probe.
[all …]
|
| D | kprobetrace.rst | 10 this is based on kprobes (kprobe and kretprobe). So it can probe wherever
11 kprobes can probe (this means, all functions except those with
19 current_tracer. Instead of that, add probe points via
31 p[:[GRP/]EVENT] [MOD:]SYM[+offs]|MEMADDR [FETCHARGS] : Set a probe
32 r[MAXACTIVE][:[GRP/]EVENT] [MOD:]SYM[+0] [FETCHARGS] : Set a return probe
33 p:[GRP/]EVENT] [MOD:]SYM[+0]%return [FETCHARGS] : Set a return probe
34 -:[GRP/]EVENT : Clear a probe
40 SYM[+offs] : Symbol+offset where the probe is inserted.
42 MEMADDR : Address where the probe is inserted.
47 FETCHARGS : Arguments. Each probe can have up to 128 args.
[all …]
|
| D | tracepoints.rst | 10 connect probe functions to them and provides some examples of probe
16 A tracepoint placed in code provides a hook to call a function (probe)
17 that you can provide at runtime. A tracepoint can be "on" (a probe is
18 connected to it) or "off" (no probe is attached). When a tracepoint is
93 Connecting a function (probe) to a tracepoint is done by providing a
94 probe (function to call) for the specific tracepoint through
95 register_trace_subsys_eventname(). Removing a probe is done through
96 unregister_trace_subsys_eventname(); it will remove the probe.
100 the probe. This, and the fact that preemption is disabled around the
101 probe call, make sure that probe removal and module unload are safe.
[all …]
|
| /kernel/linux/linux-5.10/fs/afs/ |
| D | fs_probe.c | 18 * Start the probe polling timer. We have to supply it with an inc on the
42 bool responded = server->probe.responded; in afs_finished_fs_probe()
58 * Handle the completion of a probe.
71 * Handle inability to send a probe due to ENOMEM when trying to allocate a
86 server->probe.local_failure = true; in afs_fs_probe_not_done()
87 if (server->probe.error == 0) in afs_fs_probe_not_done()
88 server->probe.error = -ENOMEM; in afs_fs_probe_not_done()
114 server->probe.error = 0; in afs_fileserver_probe_result()
117 if (!server->probe.responded) { in afs_fileserver_probe_result()
118 server->probe.abort_code = call->abort_code; in afs_fileserver_probe_result()
[all …]
|
| D | vl_probe.c | 20 if (!(server->probe.flags & AFS_VLSERVER_PROBE_RESPONDED)) { in afs_finished_vl_probe()
30 * Handle the completion of a probe RPC call.
63 server->probe.error = 0; in afs_vlserver_probe_result()
66 if (!(server->probe.flags & AFS_VLSERVER_PROBE_RESPONDED)) { in afs_vlserver_probe_result()
67 server->probe.abort_code = call->abort_code; in afs_vlserver_probe_result()
68 server->probe.error = ret; in afs_vlserver_probe_result()
76 server->probe.flags |= AFS_VLSERVER_PROBE_LOCAL_FAILURE; in afs_vlserver_probe_result()
77 if (server->probe.error == 0) in afs_vlserver_probe_result()
78 server->probe.error = ret; in afs_vlserver_probe_result()
93 if (!(server->probe.flags & AFS_VLSERVER_PROBE_RESPONDED) && in afs_vlserver_probe_result()
[all …]
|
| /kernel/linux/linux-5.10/drivers/base/ |
| D | map.c | 20 struct probe { struct
21 struct probe *next; argument
33 struct module *module, kobj_probe_t *probe, in kobj_map() argument
39 struct probe *p; in kobj_map()
44 p = kmalloc_array(n, sizeof(struct probe), GFP_KERNEL); in kobj_map()
50 p->get = probe; in kobj_map()
58 struct probe **s = &domain->probes[index % 255]; in kobj_map()
73 struct probe *found = NULL; in kobj_unmap()
80 struct probe **s; in kobj_unmap()
82 struct probe *p = *s; in kobj_unmap()
[all …]
|
| D | dd.c | 36 * Deferred Probe infrastructure.
38 * Sometimes driver probe order matters, but the kernel doesn't always have
43 * request probing to be deferred by returning -EPROBE_DEFER from its probe hook
45 * Deferred probe maintains two lists of devices, a pending list and an active
47 * pending list. A successful driver probe will trigger moving all devices
61 /* Save the async probe drivers' name from kernel cmdline */
82 * bus_probe_device() to re-attempt the probe. The loop continues in deferred_probe_work_func()
104 * Drop the mutex while probing each device; the probe path may in deferred_probe_work_func()
113 * probe makes that very unsafe. in deferred_probe_work_func()
154 * list and schedules the deferred probe workqueue to process them. It
[all …]
|
| /kernel/linux/linux-4.19/Documentation/trace/ |
| D | kprobetrace.rst | 10 this is based on kprobes (kprobe and kretprobe). So it can probe wherever
11 kprobes can probe (this means, all functions except those with
19 current_tracer. Instead of that, add probe points via
28 p[:[GRP/]EVENT] [MOD:]SYM[+offs]|MEMADDR [FETCHARGS] : Set a probe
29 r[MAXACTIVE][:[GRP/]EVENT] [MOD:]SYM[+0] [FETCHARGS] : Set a return probe
30 -:[GRP/]EVENT : Clear a probe
36 SYM[+offs] : Symbol+offset where the probe is inserted.
37 MEMADDR : Address where the probe is inserted.
42 FETCHARGS : Arguments. Each probe can have up to 128 args.
56 (*) only for return probe.
[all …]
|
| D | tracepoints.rst | 10 connect probe functions to them and provides some examples of probe
16 A tracepoint placed in code provides a hook to call a function (probe)
17 that you can provide at runtime. A tracepoint can be "on" (a probe is
18 connected to it) or "off" (no probe is attached). When a tracepoint is
93 Connecting a function (probe) to a tracepoint is done by providing a
94 probe (function to call) for the specific tracepoint through
95 register_trace_subsys_eventname(). Removing a probe is done through
96 unregister_trace_subsys_eventname(); it will remove the probe.
100 the probe. This, and the fact that preemption is disabled around the
101 probe call, make sure that probe removal and module unload are safe.
[all …]
|
| D | uprobetracer.rst | 14 current_tracer. Instead of that, add probe points via
33 OFFSET : Offset where the probe is inserted.
35 FETCHARGS : Arguments. Each probe can have up to 128 args.
49 (*) only for return probe.
72 You can check the total number of probe hits and probe miss-hits via
74 The first column is event name, the second is the number of probe hits,
75 the third is the number of probe miss-hits.
79 * Add a probe as a new uprobe event, write a new definition to uprobe_events
84 * Add a probe as a new uretprobe event::
101 at the probed text address. Probe zfree function in /bin/zsh::
[all …]
|
| /kernel/linux/linux-4.19/drivers/base/ |
| D | map.c | 20 struct probe { struct
21 struct probe *next; argument
33 struct module *module, kobj_probe_t *probe, in kobj_map() argument
39 struct probe *p; in kobj_map()
44 p = kmalloc_array(n, sizeof(struct probe), GFP_KERNEL); in kobj_map()
50 p->get = probe; in kobj_map()
58 struct probe **s = &domain->probes[index % 255]; in kobj_map()
73 struct probe *found = NULL; in kobj_unmap()
80 struct probe **s; in kobj_unmap()
82 struct probe *p = *s; in kobj_unmap()
[all …]
|
| D | dd.c | 35 * Deferred Probe infrastructure.
37 * Sometimes driver probe order matters, but the kernel doesn't always have
42 * request probing to be deferred by returning -EPROBE_DEFER from its probe hook
44 * Deferred probe maintains two lists of devices, a pending list and an active
46 * pending list. A successful driver probe will trigger moving all devices
77 * bus_probe_device() to re-attempt the probe. The loop continues in deferred_probe_work_func()
96 * Drop the mutex while probing each device; the probe path may in deferred_probe_work_func()
105 * probe makes that very unsafe. in deferred_probe_work_func()
144 * list and schedules the deferred probe workqueue to process them. It
147 * Note, there is a race condition in multi-threaded probe. In the case where
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/sfc/ |
| D | ef100.c | 73 netif_dbg(efx, probe, efx->net_dev, in ef100_pci_parse_ef100_entry()
78 netif_err(efx, probe, efx->net_dev, in ef100_pci_parse_ef100_entry()
85 netif_err(efx, probe, efx->net_dev, in ef100_pci_parse_ef100_entry()
127 netif_err(efx, probe, efx->net_dev, in ef100_pci_parse_continue_entry()
137 netif_err(efx, probe, efx->net_dev, in ef100_pci_parse_continue_entry()
148 netif_err(efx, probe, efx->net_dev, in ef100_pci_parse_continue_entry()
166 netif_err(efx, probe, efx->net_dev, in ef100_pci_parse_continue_entry()
196 netif_dbg(efx, probe, efx->net_dev, in ef100_pci_walk_xilinx_table()
201 netif_err(efx, probe, efx->net_dev, in ef100_pci_walk_xilinx_table()
210 netif_err(efx, probe, efx->net_dev, in ef100_pci_walk_xilinx_table()
[all …]
|
| /kernel/linux/linux-4.19/tools/perf/tests/shell/lib/ |
| D | probe_vfs_getname.sh | 3 perf probe -l 2>&1 | grep -q probe:vfs_getname
8 perf probe -q -d probe:vfs_getname*
15 …line=$(perf probe -L getname_flags 2>&1 | egrep 'result.*=.*filename;' | sed -r 's/[[:space:]]+([[…
16 perf probe -q "vfs_getname=getname_flags:${line} pathname=result->name:string" || \
17 perf probe $verbose "vfs_getname=getname_flags:${line} pathname=filename:ustring"
|
| /kernel/linux/linux-5.10/tools/perf/tests/shell/lib/ |
| D | probe_vfs_getname.sh | 3 perf probe -l 2>&1 | grep -q probe:vfs_getname
8 perf probe -q -d probe:vfs_getname*
15 …line=$(perf probe -L getname_flags 2>&1 | egrep 'result.*=.*filename;' | sed -r 's/[[:space:]]+([[…
16 perf probe -q "vfs_getname=getname_flags:${line} pathname=result->name:string" || \
17 perf probe $verbose "vfs_getname=getname_flags:${line} pathname=filename:ustring"
|
| /kernel/linux/linux-5.10/tools/testing/selftests/ftrace/test.d/direct/ |
| D | kprobe-direct.tc | 44 # probe -> direct -> no direct > no probe
50 # probe -> direct -> no probe > no direct
56 # direct -> probe -> no probe > no direct
62 # direct -> probe -> no direct > no noprobe
|
| /kernel/linux/linux-4.19/kernel/ |
| D | tracepoint.c | 138 printk(KERN_DEBUG "Probe %d : %p\n", i, funcs[i].func); in debug_print_probes()
165 /* + 2 : one for new probe, one for NULL func */ in func_add()
174 /* Copy higher priority probes ahead of the new probe */ in func_add()
211 * If probe is NULL, then nr_probes = nr_del = 0, and then the in func_remove()
238 * Add the probe function to a tracepoint.
262 * that the new probe callbacks array is consistent before setting in tracepoint_add_func()
274 * Remove a probe function from a tracepoint.
306 * tracepoint_probe_register_prio - Connect a probe to a tracepoint with priority
308 * @probe: probe handler
314 * unregistering the probe before the module is gone. This can be
[all …]
|
| /kernel/linux/linux-5.10/kernel/ |
| D | tracepoint.c | 176 printk(KERN_DEBUG "Probe %d : %p\n", i, funcs[i].func); in debug_print_probes()
206 /* + 2 : one for new probe, one for NULL func - stub functions */ in func_add()
233 /* Copy higher priority probes ahead of the new probe */ in func_add()
271 * If probe is NULL, then nr_probes = nr_del = 0, and then the in func_remove()
342 * Add the probe function to a tracepoint.
367 * that the new probe callbacks array is consistent before setting in tracepoint_add_func()
412 * Remove a probe function from a tracepoint.
484 * tracepoint_probe_register_prio_may_exist - Connect a probe to a tracepoint with priority
486 * @probe: probe handler
493 int tracepoint_probe_register_prio_may_exist(struct tracepoint *tp, void *probe, in tracepoint_probe_register_prio_may_exist() argument
[all …]
|
| /kernel/linux/linux-4.19/tools/perf/tests/shell/ |
| D | record+script_probe_vfs_getname.sh | 1 # Use vfs_getname probe to get syscall args filenames
3 # Uses the 'perf test shell' library to add probe:vfs_getname to the system
5 # checks that that was captured by the vfs_getname probe in the generated
10 . $(dirname $0)/lib/probe.sh
21 perf record -o ${perfdata} -e probe:vfs_getname touch $file
27 …egrep " +touch +[0-9]+ +\[[0-9]+\] +[0-9]+\.[0-9]+: +probe:vfs_getname: +\([[:xdigit:]]+\) +pathna…
|
| /kernel/linux/linux-5.10/tools/perf/tests/shell/ |
| D | record+script_probe_vfs_getname.sh | 2 # Use vfs_getname probe to get syscall args filenames
4 # Uses the 'perf test shell' library to add probe:vfs_getname to the system
6 # checks that that was captured by the vfs_getname probe in the generated
12 . $(dirname $0)/lib/probe.sh
23 perf record -o ${perfdata} -e probe:vfs_getname\* touch $file
29 …egrep " +touch +[0-9]+ +\[[0-9]+\] +[0-9]+\.[0-9]+: +probe:vfs_getname[_0-9]*: +\([[:xdigit:]]+\) …
|
| /kernel/linux/linux-5.10/tools/testing/selftests/bpf/ |
| D | test_bpftool.py | 50 raise IfaceNotFoundError("Could not find any network interface to probe")
82 res = bpftool_json(["feature", "probe", "dev", iface])
93 bpftool_json(["feature", "probe", "kernel"]),
94 bpftool_json(["feature", "probe"]),
121 bpftool_json(["feature", "probe", "kernel", "full"]),
122 bpftool_json(["feature", "probe", "full"]),
146 full_res = bpftool_json(["feature", "probe", "full"])
147 not_full_res = bpftool_json(["feature", "probe"])
176 res = bpftool(["feature", "probe", "macros"])
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/devfreq/event/ |
| D | exynos-nocp.txt | 2 * Samsung Exynos NoC (Network on Chip) Probe device
4 The Samsung Exynos542x SoC has NoC (Network on Chip) Probe for NoC bus.
15 - reg: physical base address of each NoC Probe and length of memory mapped region.
18 - clock-names : the name of clock used by the NoC Probe, "nocp"
21 Example : NoC Probe nodes in Device Tree are listed below.
|