Home
last modified time | relevance | path

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

123

/Linux-v5.4/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-v5.4/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-v5.4/Documentation/
Dkprobes.txt35 There are currently two types of probes: kprobes, and kretprobes
36 (also called return probes). A kprobe can be inserted on virtually
42 one or more probes, and the exit function unregisters them. A
47 There are also ``register_/unregister_*probes()`` functions for batch
48 registration/unregistration of a group of ``*probes``. These functions
50 a lot of probes at once.
53 probes work and how jump optimization works. They explain certain
137 some probes. In the kretprobe struct, the nmissed field is set to
312 Kprobes and return probes are implemented on the following
318 - ia64 (Does not support probes on instruction slot1.)
[all …]
/Linux-v5.4/arch/s390/lib/
DMakefile8 lib-$(CONFIG_KPROBES) += probes.o
9 lib-$(CONFIG_UPROBES) += probes.o
/Linux-v5.4/Documentation/devicetree/bindings/devfreq/event/
Dexynos-nocp.txt6 that the Network on Chip (NoC) probes detects are transported over
7 the network infrastructure to observer units. You can configure probes to
10 NoC probes to provide bandwidth information about behavior of the SoC
/Linux-v5.4/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-v5.4/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-v5.4/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.c44 static const char * const probes[] = { "RedBoot", "cmdlinepart", NULL }; variable
94 mtd_device_parse_register(info->mtd, probes, NULL, flash->parts, in pxa2xx_flash_probe()
Dixp4xx.c152 static const char * const probes[] = { "RedBoot", "cmdlinepart", NULL }; variable
235 err = mtd_device_parse_register(info->mtd, probes, &ppdata, in ixp4xx_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.c469 static char *probes[] = { "jedec_probe", "cfi_probe" }; in pcmciamtd_config() local
572 for(i = 0; i < ARRAY_SIZE(probes); i++) { in pcmciamtd_config()
573 pr_debug("Trying %s\n", probes[i]); in pcmciamtd_config()
574 mtd = do_map_probe(probes[i], &dev->pcmcia_map); in pcmciamtd_config()
578 pr_debug("FAILED: %s\n", probes[i]); in pcmciamtd_config()
Dplat-ram.c177 err = mtd_device_parse_register(info->mtd, pdata->probes, NULL, in platram_probe()
/Linux-v5.4/kernel/
Dtracepoint.c53 struct tracepoint_func probes[0]; member
58 struct tp_probes *p = kmalloc(struct_size(p, probes, count), in allocate_probes()
60 return p == NULL ? NULL : p->probes; in allocate_probes()
95 struct tp_probes, probes[0]); in release_probes()
/Linux-v5.4/include/linux/mtd/
Dplat-ram.h20 const char * const *probes; member
/Linux-v5.4/Documentation/features/debug/kretprobes/
Darch-support.txt4 # description: arch supports kernel function-return probes
/Linux-v5.4/Documentation/features/debug/uprobes/
Darch-support.txt4 # description: arch supports live patched user probes
/Linux-v5.4/kernel/trace/
Dtrace_probe.h232 struct list_head probes; member
298 return list_first_entry(&tpe->probes, struct trace_probe, list); in trace_probe_primary_from_call()
303 return &tp->event->probes; in trace_probe_probe_list()
/Linux-v5.4/arch/arm/mach-pxa/
Dpoodle.c350 static const char * const probes[] = { variable
359 .part_parsers = probes,
/Linux-v5.4/drivers/char/xillybus/
DKconfig12 programmable logic (FPGA). The driver probes the hardware for
/Linux-v5.4/net/ipv4/
Darp.c336 int probes = atomic_read(&neigh->probes); in arp_solicit() local
373 probes -= NEIGH_VAR(neigh->parms, UCAST_PROBES); in arp_solicit()
374 if (probes < 0) { in arp_solicit()
380 probes -= NEIGH_VAR(neigh->parms, APP_PROBES); in arp_solicit()
381 if (probes < 0) { in arp_solicit()
/Linux-v5.4/drivers/mtd/devices/
Dbcm47xxsflash.c16 static const char * const probes[] = { "bcm47xxpart", NULL }; variable
347 err = mtd_device_parse_register(&b47s->mtd, probes, NULL, NULL, 0); in bcm47xxsflash_bcma_probe()
/Linux-v5.4/Documentation/networking/
Dproc_net_tcp.txt39 | |----------------------------------> unanswered 0-window probes
/Linux-v5.4/Documentation/devicetree/bindings/clock/
Dsilabs,si5341.txt16 configured when the driver probes, it assumes the driver must fully initialize
49 probes, the PLL will be set to 14GHz.
/Linux-v5.4/arch/arm64/kernel/
DMakefile67 obj-y += vdso/ probes/

123