Home
last modified time | relevance | path

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

12345678910>>...238

/linux-6.14.4/tools/perf/tests/shell/base_probe/
Dtest_adding_kernel.sh40 ### basic probe adding
44 $CMD_PERF probe $opt $TEST_PROBE 2> $LOGS_DIR/adding_kernel_add$opt.err
47 …../common/check_all_patterns_found.pl "Added new events?:" "probe:$TEST_PROBE" "on $TEST_PROBE" < …
50 print_results $PERF_EXIT_CODE $CHECK_EXIT_CODE "adding probe $TEST_PROBE :: $opt"
55 ### listing added probe :: perf list
58 $CMD_PERF list probe:\* > $LOGS_DIR/adding_kernel_list.log
61 ../common/check_all_lines_matched.pl "$RE_LINE_EMPTY" "List of pre-defined events" "probe:${TEST_PR…
64 print_results $PERF_EXIT_CODE $CHECK_EXIT_CODE "listing added probe :: perf list"
68 ### listing added probe :: perf probe -l
71 $CMD_PERF probe -l > $LOGS_DIR/adding_kernel_list-l.log
[all …]
Dtest_basic.sh2 # perf_probe :: Basic perf probe functionality (exclusive)
12 # This test tests basic functionality of perf probe command.
30 $CMD_PERF probe --help > $LOGS_DIR/basic_helpmsg.log 2> $LOGS_DIR/basic_helpmsg.err
33 …ommon/check_all_patterns_found.pl "PERF-PROBE" "NAME" "SYNOPSIS" "DESCRIPTION" "OPTIONS" "PROBE\s+…
53 # without any args perf-probe should print usage
54 $CMD_PERF probe 2> $LOGS_DIR/basic_usage.log > /dev/null
56 ../common/check_all_patterns_found.pl "[Uu]sage" "perf probe" "verbose" "quiet" "add" "del" "force"…
66 $CMD_PERF probe --quiet --add vfs_read > $LOGS_DIR/basic_quiet01.log 2> $LOGS_DIR/basic_quiet01.err
68 $CMD_PERF probe --quiet --del vfs_read > $LOGS_DIR/basic_quiet03.log 2> $LOGS_DIR/basic_quiet02.err
Dtest_adding_blacklisted.sh29 VMLINUX_FILE=$(perf probe -v random_probe |& grep "Using.*for symbols" | sed -r 's/^Using (.*) for …
36 REGEX_SCOPE_FAIL="Failed to find scope of probe point"
38 REGEX_NOT_FOUND_MESSAGE="Probe point \'$RE_EVENT\' not found."
51 # functions from blacklist should be skipped by perf probe
52 ! $CMD_PERF probe $BLACKFUNC > $LOGS_DIR/adding_blacklisted.log 2> $LOGS_DIR/adding_blacklisted.err
60 echo "Result polluted by broken DWARF, trying another probe"
65 awk -v probe="$BLACKFUNC" '/DW_AT_language/ { comp_lang = $0 }
66 $0 ~ probe { if (comp_lang) { print comp_lang }; exit }' |
91 ### listing not-added probe
94 $CMD_PERF list probe:\* > $LOGS_DIR/adding_blacklisted_list.log
[all …]
/linux-6.14.4/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-6.14.4/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
138 zero when the return probe is registered, and is incremented every
140 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 …]
/linux-6.14.4/fs/afs/
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.
64 server->probe.error = 0; in afs_vlserver_probe_result()
67 if (!(server->probe.flags & AFS_VLSERVER_PROBE_RESPONDED)) { in afs_vlserver_probe_result()
68 server->probe.abort_code = call->abort_code; in afs_vlserver_probe_result()
69 server->probe.error = ret; in afs_vlserver_probe_result()
77 server->probe.flags |= AFS_VLSERVER_PROBE_LOCAL_FAILURE; in afs_vlserver_probe_result()
78 if (server->probe.error == 0) in afs_vlserver_probe_result()
79 server->probe.error = ret; in afs_vlserver_probe_result()
94 if (!(server->probe.flags & AFS_VLSERVER_PROBE_RESPONDED) && in afs_vlserver_probe_result()
[all …]
/linux-6.14.4/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
60 /* Save the async probe drivers' name from kernel cmdline */
88 * bus_probe_device() to re-attempt the probe. The loop continues in deferred_probe_work_func()
109 * Drop the mutex while probing each device; the probe path may in deferred_probe_work_func()
118 * probe makes that very unsafe. in deferred_probe_work_func()
161 * list and schedules the deferred probe workqueue to process them. It
[all …]
/linux-6.14.4/drivers/gpu/drm/xe/
DKconfig63 string "Force probe xe for selected Intel hardware IDs"
69 Force probe the xe for Intel graphics devices that are
74 It can also be used to block the probe of recognized and fully
77 Use "" to disable force probe. If in doubt, use this.
79 Use "<pci-id>[,<pci-id>,...]" to force probe the xe for listed
82 Use "*" to force probe the driver for all known devices.
84 Use "!" right before the ID to block the probe of the device. For
85 example, "4500,!4571" forces the probe of 4500 and blocks the probe of
88 Use "!*" to block the probe of the driver for all known devices.
/linux-6.14.4/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-6.14.4/tools/perf/tests/shell/lib/
Dprobe_vfs_getname.sh4 perf probe -l 2>&1 | grep -q probe:vfs_getname
9 perf probe -q -d probe:vfs_getname*
17 …line=$(perf probe -L getname_flags 2>&1 | grep -E "$result_filename_re" | sed -r "s/$result_filena…
20 …line=$(perf probe -L getname_flags 2>&1 | grep -E "$result_aname_re" | sed -r "s/$result_aname_re/…
22 perf probe -q "vfs_getname=getname_flags:${line} pathname=result->name:string" || \
23 perf probe $add_probe_verbose "vfs_getname=getname_flags:${line} pathname=filename:ustring"
/linux-6.14.4/tools/testing/selftests/bpf/
Dsdt.h1 /* <sys/sdt.h> - Systemtap static probe definition macros.
244 Without that assembler support, some combinations of probe placements
404 number of probe arguments is not known until compile time. Since
406 pre-#define SDT_USE_VARIADIC to enable this type of probe.
430 contain the actual assembly code around the probe site.
438 emits the assembly code for "before\nafter", with a probe in between.
439 The probe arguments are the %eax register, and the value of the memory
444 In a GNU C extended asm statement, the probe arguments can be specified
446 macro STAP_PROBE_ASM_OPERANDS gives the C values of these probe arguments,
460 but the probe site is right between "someinsn" and "otherinsn".
[all …]
Duprobe_multi.c74 #define PROBE STAP_PROBE(test, usdt); macro
76 #define PROBE10 PROBE PROBE PROBE PROBE PROBE \
77 PROBE PROBE PROBE PROBE PROBE
Dtest_bpftool.py50 raise IfaceNotFoundError("Could not find any network interface to probe")
84 res = bpftool_json(["feature", "probe", "dev", iface])
95 bpftool_json(["feature", "probe", "kernel"]),
96 bpftool_json(["feature", "probe"]),
120 bpftool_json(["feature", "probe", "kernel", "full"]),
121 bpftool_json(["feature", "probe", "full"]),
142 full_res = bpftool_json(["feature", "probe", "full"])
143 not_full_res = bpftool_json(["feature", "probe"])
172 res = bpftool(["feature", "probe", "macros"])
/linux-6.14.4/tools/perf/tests/shell/
Drecord+script_probe_vfs_getname.sh2 # Use vfs_getname probe to get syscall args filenames (exclusive)
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 # shellcheck source=lib/probe.sh
13 . "$(dirname "$0")/lib/probe.sh"
23 skip_no_probe_record_support "probe:vfs_getname*"
28 perf record -o ${perfdata} -e probe:vfs_getname\* touch $file
34 …grep -E " +touch +[0-9]+ +\[[0-9]+\] +[0-9]+\.[0-9]+: +probe:vfs_getname[_0-9]*: +\([[:xdigit:]]+\…
Dtest_uprobe_from_different_cu.sh2 # test perf probe of function from different CU
7 # Skip if there's no probe command.
8 if ! perf | grep probe
10 echo "Skip: probe command isn't present"
27 perf probe -x ${temp_dir}/testfile -d foo || true
87 perf probe -x ${temp_dir}/testfile --funcs foo | grep "foo"
88 perf probe -x ${temp_dir}/testfile foo
/linux-6.14.4/kernel/
Dtracepoint.c130 printk(KERN_DEBUG "Probe %d : %p\n", i, funcs[i].func); in debug_print_probes()
138 int iter_probes; /* Iterate over old probe array. */ in func_add()
158 /* + 2 : one for new probe, one for NULL func */ in func_add()
209 * If probe is NULL, then nr_probes = nr_del = 0, and then the in func_remove()
275 * Add the probe function to a tracepoint.
300 * that the new probe callbacks array is consistent before setting in tracepoint_add_func()
345 * Remove a probe function from a tracepoint.
416 * tracepoint_probe_register_prio_may_exist - Connect a probe to a tracepoint with priority
418 * @probe: probe handler
425 int tracepoint_probe_register_prio_may_exist(struct tracepoint *tp, void *probe, in tracepoint_probe_register_prio_may_exist() argument
[all …]
/linux-6.14.4/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-6.14.4/drivers/gpu/drm/i915/
DKconfig61 string "Force probe i915 for selected Intel hardware IDs"
67 Force probe the i915 driver for Intel graphics devices that are
73 It can also be used to block the probe of recognized and fully
76 Use "" to disable force probe. If in doubt, use this.
78 Use "<pci-id>[,<pci-id>,...]" to force probe the i915 for listed
81 Use "*" to force probe the driver for all known devices. Not
84 Use "!" right before the ID to block the probe of the device. For
85 example, "4500,!4571" forces the probe of 4500 and blocks the probe of
88 Use "!*" to block the probe of the driver for all known devices.
/linux-6.14.4/tools/perf/
Dbuiltin-probe.c3 * builtin-probe.c
5 * Builtin probe command: Set up probe events by C expression
28 #include "util/probe-finder.h"
29 #include "util/probe-event.h"
30 #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()
396 pr_info("\nperf is not linked with libtraceevent, to use the new probe you can use tracefs:\n\n"); in perf_add_probe_events()
401 pr_info("\tBefore removing the probe, echo 0 > events/%s/%s/enable\n", group, event); in perf_add_probe_events()
520 "perf probe [<options>] 'PROBEDEF' ['PROBEDEF' ...]", in __cmd_probe()
[all …]
/linux-6.14.4/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()
272 pr_info("exynos-nocp: new NoC Probe device registered: %s\n", in exynos_nocp_probe()
286 .probe = exynos_nocp_probe,
[all …]
/linux-6.14.4/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-6.14.4/arch/s390/net/
Dbpf_jit_comp.c697 * A single BPF probe instruction
706 static void bpf_jit_probe_init(struct bpf_jit_probe *probe) in bpf_jit_probe_init() argument
708 probe->prg = -1; in bpf_jit_probe_init()
709 probe->nop_prg = -1; in bpf_jit_probe_init()
710 probe->reg = -1; in bpf_jit_probe_init()
711 probe->arena_reg = REG_0; in bpf_jit_probe_init()
721 struct bpf_jit_probe *probe) in bpf_jit_probe_emit_nop() argument
723 if (probe->prg == -1 || probe->nop_prg != -1) in bpf_jit_probe_emit_nop()
724 /* The probe is not armed or nop is already emitted. */ in bpf_jit_probe_emit_nop()
727 probe->nop_prg = jit->prg; in bpf_jit_probe_emit_nop()
[all …]

12345678910>>...238