Home
last modified time | relevance | path

Searched full:probes (Results 1 – 25 of 276) sorted by relevance

12345678910>>...12

/linux/Documentation/trace/
H A Dkprobes.rst2 Kernel Probes (Kprobes)
11 1. Concepts: Kprobes, and Return Probes
25 Concepts: Kprobes and Return Probes
36 There are currently two types of probes: kprobes, and kretprobes
37 (also called return probes). A kprobe can be inserted on virtually
43 one or more probes, and the exit function unregisters them. A
48 There are also ``register_/unregister_*probes()`` functions for batch
49 registration/unregistration of a group of ``*probes``. These functions
51 a lot of probes at once.
54 probes work and how jump optimization works. They explain certain
[all …]
/linux/sound/soc/sof/
H A DMakefile31 snd-sof-probes-y := sof-client-probes.o
33 snd-sof-probes-y += sof-client-probes-ipc3.o
36 snd-sof-probes-y += sof-client-probes-ipc4.o
55 obj-$(CONFIG_SND_SOC_SOF_DEBUG_PROBES) += snd-sof-probes.o
H A Dsof-client-probes-ipc4.c14 #include "sof-client-probes.h"
172 * are no probes connected and with all injectors detached.
198 * @desc: Returned list of active probes
199 * @num_desc: Returned count of active probes
303 * ipc4_probes_points_add - connect specified probes
357 * ipc4_probes_points_remove - disconnect specified probes
/linux/tools/perf/tests/shell/base_probe/
H A Dtest_adding_kernel.sh2 # perf_probe :: Add probes, list and remove them (exclusive)
12 # This test tests adding of probes, their correct listing
60 # any added probes should appear in perf-list output
76 # '-l' should list all the added probes as well
133 # removed probes should NOT appear in perf-list output
166 ### force-adding probes
177 print_results $PERF_EXIT_CODE $CHECK_EXIT_CODE "force-adding probes :: first probe adding"
189 print_results $PERF_EXIT_CODE $CHECK_EXIT_CODE "force-adding probes :: second probe adding (without…
202 print_results $PERF_EXIT_CODE $CHECK_EXIT_CODE "force-adding probes :: second probe adding (with fo…
227 ### removing multiple probes
[all …]
H A Dtest_adding_blacklisted.sh2 # perf_probe :: Reject blacklisted probes (exclusive)
12 # Blacklisted functions should not be added successfully as probes,
32 # remove all previously added probes
99 # blacklisted probes should NOT appear in perf-list output
/linux/Documentation/core-api/
H A Dtracepoint.rst12 throughout the kernel. 'Probes' register/unregister with tracepoints via
13 a callback mechanism. The 'probes' are strictly typed functions that are
16 From this simple callback mechanism, 'probes' can be used to profile,
18 provide a framework for using 'probes'. These tools include Systemtap,
30 unregistering probes with these callback sites is covered in the
/linux/tools/perf/Documentation/
H A Dperf-probe.txt82 When this is used with --cache, perf shows all cached probes instead of
83 the live probes.
131 (With --add) Cache the probes. Any events which successfully added
133 (With --list) Show cached probes.
134 (With --del) Remove cached probes.
136 --max-probes=NUM::
179 'EVENT' specifies the name of new event, if omitted, it will be set the name of the probed function, and for return probes, a "\_\_return" suffix is automatically added to the function name. You can also specify a group name by 'GROUP', if omitted, set 'probe' is used for kprobe and 'probe_<bin>' is used for uprobe.
182 'FUNC' specifies a probed function name, and it may have one of the following options; '+OFFS' is the offset from function entry address in bytes, ':RLN' is the relative-line number from function entry line, and '%return' means that it probes function return. And ';PTN' means lazy matching pattern (see LAZY MATCHING). Note that ';PTN' must be the end of the probe point definition. In addition, '@SRC' specifies a source file which has that function.
185 'SDTEVENT' and 'PROVIDER' is the pre-defined event name which is defined by user SDT (Statically Defined Tracing) or the pre-cached probes with event name.
263 Add one or more probes whic
[all...]
/linux/tools/testing/ktest/examples/bootconfigs/
H A Dtracing.bconf14 probes = "vfs_read $arg2 $arg3";
17 probes = "vfs_write $arg2 +0($arg2):ustring $arg3";
20 probes = "initrd_load";
H A Dfunctiongraph.bconf6 probes = "pci_proc_init"
10 probes = "pci_proc_init%return"
/linux/drivers/base/
H A Dmap.c28 } *probes[255]; member
58 struct probe **s = &domain->probes[index % 255]; in kobj_map()
81 for (s = &domain->probes[index % 255]; *s; s = &(*s)->next) { in kobj_unmap()
103 for (p = domain->probes[MAJOR(dev) % 255]; p; p = p->next) { in kobj_lookup()
151 p->probes[i] = base; in kobj_map_init()
/linux/Documentation/devicetree/bindings/devfreq/event/
H A Dsamsung,exynos-nocp.yaml16 that the Network on Chip (NoC) probes detects are transported over the
17 network infrastructure to observer units. You can configure probes to capture
19 traffic debug or statistic collectors. Exynos542x bus has multiple NoC probes
/linux/arch/powerpc/include/asm/
H A Duprobes.h5 * User-space Probes (UProbes) for powerpc
13 #include <asm/probes.h>
/linux/arch/arm/probes/
H A Ddecode.h3 * arch/arm/probes/decode.h
16 #include <asm/probes.h>
148 * The probes instruction handler is set to the value found by
154 * The probes instruction handler is set to the value found by
157 * modified instruction (see below) is placed in the probes instruction
/linux/Documentation/dev-tools/
H A Dgpio-sloppy-logic-analyzer.rst19 connected to these GPIO lines with wires (i.e. digital probes), acting as a
43 Tell the kernel which GPIOs are used as probes. For a Device Tree based system,
54 maximum of 8 probes are supported. 32 are likely possible but are not
/linux/tools/testing/selftests/bpf/prog_tests/
H A Dusdt.c24 unsigned short test_usdt0_semaphore SEC(".probes");
25 unsigned short test_usdt3_semaphore SEC(".probes");
26 unsigned short test_usdt12_semaphore SEC(".probes");
67 unsigned short test_usdt_sib_semaphore SEC(".probes"); in subtest_basic_usdt()
340 unsigned short test_usdt_100_semaphore SEC(".probes"); in urand_spawn()
341 unsigned short test_usdt_300_semaphore SEC(".probes"); in urand_spawn()
342 unsigned short test_usdt_400_semaphore SEC(".probes"); in urand_spawn()
/linux/drivers/bcma/
H A Ddriver_chipcommon_nflash.c25 static const char *probes[] = { "bcm47xxpart", NULL }; variable
51 cc->nflash.brcmnand_info.part_probe_types = probes; in bcma_nflash_init()
/linux/arch/s390/include/asm/
H A Dkprobes.h5 * Kernel Probes (KProbes)
10 * Probes initial implementation ( includes suggestions from
/linux/drivers/mtd/nand/raw/bcm47xxnflash/
H A Dmain.c20 static const char *probes[] = { "bcm47xxpart", NULL }; variable
51 err = mtd_device_parse_register(mtd, probes, NULL, NULL, 0); in bcm47xxnflash_probe()
/linux/drivers/mtd/maps/
H A Dsolutionengine.c34 static const char * const probes[] = { "RedBoot", "cmdlinepart", NULL }; variable
73 mtd_device_parse_register(flash_mtd, probes, NULL, NULL, 0); in init_soleng_maps()
H A Dpxa2xx-flash.c42 static const char * const probes[] = { "RedBoot", "cmdlinepart", NULL }; variable
94 mtd_device_parse_register(info->mtd, probes, NULL, flash->parts, in pxa2xx_flash_probe()
/linux/drivers/net/wireless/ti/wl12xx/
H A Dscan.h30 /* Rate bit field for sending the probes */
86 u8 n_probe_reqs; /* Number of probes requests per channel */
/linux/tools/testing/selftests/net/
H A Dtest_neigh.sh198 local probes
216 probes=$(ip -n "$ns1" -j -s neigh get "$ip_addr" dev veth0 | jq '.[]["probes"]')
217 if [[ $probes -eq 0 ]]; then
218 check_err 1 "No probes were sent"
/linux/samples/kprobes/
H A Dkretprobe_example.c5 * Here's a sample kernel module showing the use of return probes to
107 MODULE_DESCRIPTION("sample kernel module showing the use of return probes");
/linux/drivers/net/
H A DSpace.c23 * - sort probes in a sane way, make sure all (safe) probes
199 /* ISA probes that touch addresses < 0x400 (including those that also
/linux/include/scsi/fc/
H A Dfc_fip.h26 #define FIP_VN_PROBE_WAIT 100 /* interval between VN2VN probes (ms) */
28 #define FIP_VN_RLIM_INT 10000 /* interval between probes when rate limited */
29 #define FIP_VN_RLIM_COUNT 10 /* number of probes before rate limiting */

12345678910>>...12