Home
last modified time | relevance | path

Searched refs:probes (Results 1 – 25 of 77) sorted by relevance

1234

/linux-5.19.10/tools/testing/ktest/examples/bootconfigs/
Dtracing.bconf14 probes = "vfs_read $arg2 $arg3";
17 probes = "vfs_write $arg2 +0($arg2):ustring $arg3";
20 probes = "initrd_load";
Dfunctiongraph.bconf6 probes = "pci_proc_init"
10 probes = "pci_proc_init%return"
/linux-5.19.10/drivers/base/
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-5.19.10/Documentation/core-api/
Dtracepoint.rst13 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-5.19.10/Documentation/trace/
Dkprobes.rst36 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
138 some probes. In the kretprobe struct, the nmissed field is set to
313 Kprobes and return probes are implemented on the following
319 - ia64 (Does not support probes on instruction slot1.)
[all …]
Dboottime-trace.rst114 ftrace.[instance.INSTANCE.]event.kprobes.EVENT.probes = PROBE[, PROBE2[...]]
116 multiple probes on one event, but those must have same type of
219 probes = "vfs_read $arg1 $arg2"
273 probes = "pci_proc_init"
277 probes = "pci_proc_init%return"
/linux-5.19.10/Documentation/devicetree/bindings/devfreq/event/
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-5.19.10/sound/soc/sof/
DMakefile20 snd-sof-probes-objs := sof-client-probes.o
37 obj-$(CONFIG_SND_SOC_SOF_DEBUG_PROBES) += snd-sof-probes.o
/linux-5.19.10/arch/s390/lib/
DMakefile8 lib-$(CONFIG_KPROBES) += probes.o
9 lib-$(CONFIG_UPROBES) += probes.o
/linux-5.19.10/drivers/bcma/
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-5.19.10/drivers/mtd/maps/
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()
Dpxa2xx-flash.c42 static const char * const probes[] = { "RedBoot", "cmdlinepart", NULL }; variable
92 mtd_device_parse_register(info->mtd, probes, NULL, flash->parts, in pxa2xx_flash_probe()
Ddc21285.c147 static const char * const probes[] = { "RedBoot", "cmdlinepart", NULL }; variable
198 mtd_device_parse_register(dc21285_mtd, probes, NULL, NULL, 0); in init_dc21285()
Dpcmciamtd.c468 static char *probes[] = { "jedec_probe", "cfi_probe" }; in pcmciamtd_config() local
571 for(i = 0; i < ARRAY_SIZE(probes); i++) { in pcmciamtd_config()
572 pr_debug("Trying %s\n", probes[i]); in pcmciamtd_config()
573 mtd = do_map_probe(probes[i], &dev->pcmcia_map); in pcmciamtd_config()
577 pr_debug("FAILED: %s\n", probes[i]); in pcmciamtd_config()
/linux-5.19.10/drivers/mtd/nand/raw/bcm47xxnflash/
Dmain.c20 static const char *probes[] = { "bcm47xxpart", NULL }; variable
51 err = mtd_device_parse_register(mtd, probes, NULL, NULL, 0); in bcm47xxnflash_probe()
/linux-5.19.10/tools/perf/Documentation/
Dperf-probe.txt76 When this is used with --cache, perf shows all cached probes instead of
77 the live probes.
125 (With --add) Cache the probes. Any events which successfully added
127 (With --list) Show cached probes.
128 (With --del) Remove cached probes.
130 --max-probes=NUM::
173 … omitted, it will be set the name of the probed function, and for return probes, a "\_\_return" su…
176 …lative-line number from function entry line, and '%return' means that it probes function return. A…
179 …which is defined by user SDT (Statically Defined Tracing) or the pre-cached probes with event name.
257 Add one or more probes which has the name start with "schedule".
[all …]
/linux-5.19.10/include/linux/mtd/
Dplat-ram.h20 const char * const *probes; member
/linux-5.19.10/kernel/
Dtracepoint.c98 struct tracepoint_func probes[]; member
109 struct tp_probes *p = kmalloc(struct_size(p, probes, count), in allocate_probes()
111 return p == NULL ? NULL : p->probes; in allocate_probes()
146 struct tp_probes, probes[0]); in release_probes()
/linux-5.19.10/arch/arm/
DKbuild9 obj-y += probes/
/linux-5.19.10/Documentation/features/debug/kretprobes/
Darch-support.txt4 # description: arch supports kernel function-return probes
/linux-5.19.10/Documentation/features/debug/uprobes/
Darch-support.txt4 # description: arch supports live patched user probes
/linux-5.19.10/tools/bpf/bpftool/Documentation/
Dbpftool-feature.rst39 By default, bpftool **does not run probes** for
42 and run all probes, the **full** keyword should be used.
/linux-5.19.10/kernel/trace/
Dtrace_probe.h238 struct list_head probes; member
305 return list_first_entry(&tpe->probes, struct trace_probe, list); in trace_probe_primary_from_call()
310 return &tp->event->probes; in trace_probe_probe_list()
/linux-5.19.10/arch/csky/kernel/
DMakefile7 obj-y += probes/
/linux-5.19.10/arch/arm/mach-pxa/
Dpoodle.c363 static const char * const probes[] = { variable
372 .part_parsers = probes,

1234