Searched refs:maxactive (Results 1 – 5 of 5) sorted by relevance
| /Linux-v5.4/samples/kprobes/ |
| D | kretprobe_example.c | 76 .maxactive = 20,
|
| /Linux-v5.4/kernel/trace/ |
| D | trace_kprobe.c | 261 int maxactive, in alloc_trace_kprobe() argument
289 tk->rp.maxactive = maxactive; in alloc_trace_kprobe()
720 int maxactive = 0; in trace_kprobe_create() local
760 ret = kstrtouint(buf, 0, &maxactive); in trace_kprobe_create()
761 if (ret || !maxactive) { in trace_kprobe_create()
768 if (maxactive > KRETPROBE_MAXACTIVE_MAX) { in trace_kprobe_create()
820 tk = alloc_trace_kprobe(group, event, addr, symbol, offset, maxactive, in trace_kprobe_create()
|
| /Linux-v5.4/include/linux/ |
| D | kprobes.h | 151 int maxactive; member
|
| /Linux-v5.4/Documentation/ |
| D | kprobes.txt | 56 a post_handler, and how to use the maxactive and nmissed fields of
124 register_kretprobe(), the user sets the maxactive field of the
130 spinlock held, maxactive = 1 should be enough. If the function is
132 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
438 You must set rp->maxactive appropriately before you call
|
| /Linux-v5.4/kernel/ |
| D | kprobes.c | 1933 if (rp->maxactive <= 0) { in register_kretprobe()
1935 rp->maxactive = max_t(unsigned int, 10, 2*num_possible_cpus()); in register_kretprobe()
1937 rp->maxactive = num_possible_cpus(); in register_kretprobe()
1942 for (i = 0; i < rp->maxactive; i++) { in register_kretprobe()
|
