Home
last modified time | relevance | path

Searched full:probe (Results 1 – 25 of 6142) sorted by relevance

12345678910>>...246

/linux-5.10/tools/perf/Documentation/
Dperf-probe.txt1 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 …]
/linux-5.10/Documentation/trace/
Dkprobes.rst16 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 …]
Dkprobetrace.rst10 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 …]
Dtracepoints.rst10 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 …]
Duprobetracer.rst14 current_tracer. Instead of that, add probe points via
38 OFFSET : Offset where the probe is inserted.
39 OFFSET%return : Offset where the return probe is inserted.
41 FETCHARGS : Arguments. Each probe can have up to 128 args.
56 (\*1) only for return probe.
81 You can check the total number of probe hits per event via
83 the second is the event name, the third is the number of probe hits.
87 * Add a probe as a new uprobe event, write a new definition to uprobe_events
92 * Add a probe as a new uretprobe event::
109 at the probed text address. Probe zfree function in /bin/zsh::
[all …]
/linux-5.10/fs/afs/
Dfs_probe.c18 * 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 …]
Dvl_probe.c20 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 …]
/linux-5.10/drivers/base/
Dmap.c20 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 …]
Ddd.c36 * 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()
101 * Drop the mutex while probing each device; the probe path may in deferred_probe_work_func()
110 * probe makes that very unsafe. in deferred_probe_work_func()
151 * list and schedules the deferred probe workqueue to process them. It
[all …]
/linux-5.10/drivers/net/ethernet/sfc/
Def100.c73 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 …]
/linux-5.10/tools/perf/tests/shell/lib/
Dprobe_vfs_getname.sh3 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"
/linux-5.10/tools/testing/selftests/ftrace/test.d/direct/
Dkprobe-direct.tc44 # 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
/linux-5.10/kernel/
Dtracepoint.c125 printk(KERN_DEBUG "Probe %d : %p\n", i, funcs[i].func); in debug_print_probes()
152 /* + 2 : one for new probe, one for NULL func */ in func_add()
161 /* Copy higher priority probes ahead of the new probe */ in func_add()
198 * If probe is NULL, then nr_probes = nr_del = 0, and then the in func_remove()
248 * Add the probe function to a tracepoint.
272 * that the new probe callbacks array is consistent before setting in tracepoint_add_func()
285 * Remove a probe function from a tracepoint.
320 * tracepoint_probe_register_prio - Connect a probe to a tracepoint with priority
322 * @probe: probe handler
328 * unregistering the probe before the module is gone. This can be
[all …]
/linux-5.10/tools/perf/tests/shell/
Drecord+script_probe_vfs_getname.sh2 # 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:]]+\) …
/linux-5.10/tools/testing/selftests/bpf/
Dtest_bpftool.py50 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"])
/linux-5.10/Documentation/devicetree/bindings/devfreq/event/
Dexynos-nocp.txt2 * 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.
/linux-5.10/drivers/devfreq/event/
Dexynos-nocp.c3 * exynos-nocp.c - Exynos NoC (Network On Chip) Probe support
30 * The devfreq-event ops structure for nocp probe.
37 /* Disable NoC probe */ in exynos_nocp_set_event()
41 dev_err(nocp->dev, "failed to disable the NoC probe device\n"); in exynos_nocp_set_event()
124 /* Enable NoC probe */ in exynos_nocp_set_event()
134 /* Reset NoC probe */ in exynos_nocp_set_event()
137 dev_err(nocp->dev, "Failed to reset NoC probe device\n"); in exynos_nocp_set_event()
176 dev_err(nocp->dev, "Failed to read the counter of NoC probe device\n"); in exynos_nocp_get_event()
273 pr_info("exynos-nocp: new NoC Probe device registered: %s\n", in exynos_nocp_probe()
289 .probe = exynos_nocp_probe,
[all …]
/linux-5.10/tools/perf/
Dbuiltin-probe.c3 * builtin-probe.c
5 * Builtin probe command: Set up probe events by C expression
27 #include "util/probe-finder.h"
28 #include "util/probe-event.h"
29 #include "util/probe-file.h"
58 pr_debug("probe-definition(%d): %s\n", params.nevents, str); in parse_probe_event()
74 /* Parse a perf-probe command into event */ in parse_probe_event()
499 "perf probe [<options>] 'PROBEDEF' ['PROBEDEF' ...]", in __cmd_probe()
500 "perf probe [<options>] --add 'PROBEDEF' [--add 'PROBEDEF' ...]", in __cmd_probe()
501 "perf probe [<options>] --del '[GROUP:]EVENT' ...", in __cmd_probe()
[all …]
/linux-5.10/drivers/media/usb/gspca/gl860/
Dgl860.c315 /* This function is called at probe time */
383 /* This function is called at probe time after sd_config */
467 /* Probe sensor orientation */ in sd_callback()
523 .probe = sd_probe,
628 u8 probe, nb26, nb96, nOV, ntry; in gl860_guess_sensor() local
634 ctrl_in(gspca_dev, 0xc0, 2, 0x0000, 0x0004, 1, &probe); in gl860_guess_sensor()
635 ctrl_in(gspca_dev, 0xc0, 2, 0x0000, 0x0004, 1, &probe); in gl860_guess_sensor()
661 ctrl_in(gspca_dev, 0xc0, 2, 0x7a00, 0x8030, 1, &probe); in gl860_guess_sensor()
662 gspca_dbg(gspca_dev, D_PROBE, "probe=0x%02x\n", probe); in gl860_guess_sensor()
663 if (probe == 0xff) in gl860_guess_sensor()
[all …]
/linux-5.10/arch/powerpc/platforms/85xx/
Dmpc85xx_rdb.c186 .probe = p2020_rdb_probe, in define_machine()
200 .probe = p1020_rdb_probe, in define_machine()
214 .probe = p1021_rdb_pc_probe, in define_machine()
228 .probe = p2020_rdb_pc_probe, in define_machine()
242 .probe = p1025_rdb_probe, in define_machine()
256 .probe = p1020_mbg_pc_probe, in define_machine()
270 .probe = p1020_utm_pc_probe, in define_machine()
284 .probe = p1020_rdb_pc_probe, in define_machine()
298 .probe = p1020_rdb_pd_probe, in define_machine()
312 .probe = p1024_rdb_probe, in define_machine()
/linux-5.10/drivers/base/test/
Dtest_async_driver_probe.c33 dev_err(dev, "async probe took too long\n"); in test_probe()
36 dev_dbg(&pdev->dev, "sleeping for %d msecs in probe\n", in test_probe()
65 .probe = test_probe,
73 .probe = test_probe,
140 pr_err("test failed: probe took too long\n"); in test_async_probe_init()
170 "test failed: probe took too long\n"); in test_async_probe_init()
205 "test failed: probe was too quick\n"); in test_async_probe_init()
232 "test failed: probe was too quick\n"); in test_async_probe_init()
240 * asynchronous probe calls remaining by forcing timeout and remove in test_async_probe_init()
242 * pending asynchronous probe calls. in test_async_probe_init()
[all …]
/linux-5.10/tools/perf/util/
Dprobe-event.h11 /* Probe related configurations */
36 bool retprobe; /* Return probe flag */
39 /* probe-tracer tracing argument referencing offset */
64 /* Perf probe probing point */
69 bool retprobe; /* Return probe flag */
75 /* Perf probe probing argument field chain */
83 /* Perf probe probing argument */
92 /* Perf probe probing event (point + arg) */
96 struct perf_probe_point point; /* Probe point */
/linux-5.10/Documentation/driver-api/driver-model/
Ddriver.rst35 .probe = eepro100_probe,
67 .probe = eepro100_probe,
149 int (*probe) (struct device *dev);
151 The probe() entry is called in task context, with the bus's rwsem locked
153 container_of() to convert "dev" to a bus-specific type, both in probe()
163 When the driver has successfully bound itself to that device, then probe()
167 A driver's probe() may return a negative errno value to indicate that
171 Optionally, probe() may return -EPROBE_DEFER if the driver depends on
174 deferred probe list and will try to call it again later. If a driver
180 -EPROBE_DEFER must not be returned if probe() has already created
[all …]
/linux-5.10/tools/bpf/bpftool/Documentation/
Dbpftool-feature.rst17 *COMMANDS* := { **probe** | **help** }
22 | **bpftool** **feature probe** [*COMPONENT*] [**full**] [**unprivileged**] [**macros** [**prefix**…
29 **bpftool feature probe** [**kernel**] [**full**] [**macros** [**prefix** *PREFIX*]]
30 Probe the running kernel and dump a number of eBPF-related
49 Keyword **kernel** can be omitted. If no probe target is
62 **bpftool feature probe dev** *NAME* [**full**] [**macros** [**prefix** *PREFIX*]]
63 Probe network device for supported eBPF features and dump
/linux-5.10/Documentation/driver-api/
Ddevice_link.rst19 another one can probe or function correctly.
57 device ``->probe`` callback or a boot-time PCI quirk.
61 ``->probe`` callback while the supplier hasn't started to probe yet: Had the
66 ``->probe`` callback while the supplier is still probing, but the consumer must
72 is added in the ``->probe`` callback of the supplier or consumer driver, it is
87 link is added from the consumer's ``->probe`` callback: ``DL_FLAG_RPM_ACTIVE``
91 probe or later unbinds.
93 Similarly, when the device link is added from supplier's ``->probe`` callback,
95 purged when the supplier fails to probe or later unbinds.
99 to probe for a driver for the consumer driver on the link automatically after
[all …]

12345678910>>...246