Searched refs:maxactive (Results 1 – 6 of 6) sorted by relevance
| /linux-6.3-rc2/kernel/trace/ |
| A D | trace_kprobe.c | 261 int maxactive, in alloc_trace_kprobe() argument
289 tk->rp.maxactive = maxactive; in alloc_trace_kprobe()
740 int maxactive = 0; in __trace_kprobe_create() local
780 ret = kstrtouint(buf, 0, &maxactive); in __trace_kprobe_create()
781 if (ret || !maxactive) { in __trace_kprobe_create()
788 if (maxactive > KRETPROBE_MAXACTIVE_MAX) { in __trace_kprobe_create()
858 tk = alloc_trace_kprobe(group, event, addr, symbol, offset, maxactive, in __trace_kprobe_create()
1104 if (trace_kprobe_is_return(tk) && tk->rp.maxactive) in trace_kprobe_show()
1105 seq_printf(m, "%d", tk->rp.maxactive); in trace_kprobe_show()
|
| /linux-6.3-rc2/samples/kprobes/ |
| A D | kretprobe_example.c | 77 .maxactive = 20,
|
| /linux-6.3-rc2/Documentation/trace/ |
| A 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
136 It's not a disaster if you set maxactive too low; you'll just miss
424 You must set rp->maxactive appropriately before you call
|
| /linux-6.3-rc2/include/linux/ |
| A D | kprobes.h | 151 int maxactive; member
|
| /linux-6.3-rc2/kernel/ |
| A D | kprobes.c | 2213 if (rp->maxactive <= 0) in register_kretprobe()
2214 rp->maxactive = max_t(unsigned int, 10, 2*num_possible_cpus()); in register_kretprobe()
2221 for (i = 0; i < rp->maxactive; i++) { in register_kretprobe()
2245 for (i = 0; i < rp->maxactive; i++) { in register_kretprobe()
|
| /linux-6.3-rc2/arch/s390/lib/ |
| A D | test_unwind.c | 201 my_kretprobe.maxactive = 1; in test_unwind_kretprobe()
|
Completed in 18 milliseconds