Searched refs:maxactive (Results 1 – 5 of 5) sorted by relevance
| /Linux-v5.15/kernel/trace/ |
| D | trace_kprobe.c | 258 int maxactive, in alloc_trace_kprobe() argument
286 tk->rp.maxactive = maxactive; in alloc_trace_kprobe()
742 int maxactive = 0; in __trace_kprobe_create() local
781 ret = kstrtouint(buf, 0, &maxactive); in __trace_kprobe_create()
782 if (ret || !maxactive) { in __trace_kprobe_create()
789 if (maxactive > KRETPROBE_MAXACTIVE_MAX) { in __trace_kprobe_create()
857 tk = alloc_trace_kprobe(group, event, addr, symbol, offset, maxactive, in __trace_kprobe_create()
1103 if (trace_kprobe_is_return(tk) && tk->rp.maxactive) in trace_kprobe_show()
1104 seq_printf(m, "%d", tk->rp.maxactive); in trace_kprobe_show()
|
| /Linux-v5.15/samples/kprobes/ |
| D | kretprobe_example.c | 78 .maxactive = 20,
|
| /Linux-v5.15/Documentation/trace/ |
| D | kprobes.rst | 57 a post_handler, and how to use the maxactive and nmissed fields of
125 register_kretprobe(), the user sets the maxactive field of the
131 spinlock held, maxactive = 1 should be enough. If the function is
133 or preemption), NR_CPUS should be enough. If maxactive <= 0, it is
137 It's not a disaster if you set maxactive too low; you'll just miss
425 You must set rp->maxactive appropriately before you call
|
| /Linux-v5.15/include/linux/ |
| D | kprobes.h | 150 int maxactive; member
|
| /Linux-v5.15/kernel/ |
| D | kprobes.c | 2013 if (rp->maxactive <= 0) { in register_kretprobe()
2015 rp->maxactive = max_t(unsigned int, 10, 2*num_possible_cpus()); in register_kretprobe()
2017 rp->maxactive = num_possible_cpus(); in register_kretprobe()
2026 for (i = 0; i < rp->maxactive; i++) { in register_kretprobe()
|
