Searched refs:maxactive (Results 1 – 5 of 5) sorted by relevance
| /Linux-v4.19/samples/kprobes/ |
| D | kretprobe_example.c | 75 .maxactive = 20,
|
| /Linux-v4.19/kernel/trace/ |
| D | trace_kprobe.c | 309 int maxactive, in alloc_trace_kprobe() argument
337 tk->rp.maxactive = maxactive; in alloc_trace_kprobe()
711 int maxactive = 0; in create_trace_kprobe() local
736 ret = kstrtouint(&argv[0][1], 0, &maxactive); in create_trace_kprobe()
744 if (maxactive > KRETPROBE_MAXACTIVE_MAX) { in create_trace_kprobe()
746 maxactive, KRETPROBE_MAXACTIVE_MAX); in create_trace_kprobe()
825 tk = alloc_trace_kprobe(group, event, addr, symbol, offset, maxactive, in create_trace_kprobe()
|
| /Linux-v4.19/include/linux/ |
| D | kprobes.h | 164 int maxactive; member
|
| /Linux-v4.19/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
437 You must set rp->maxactive appropriately before you call
|
| /Linux-v4.19/kernel/ |
| D | kprobes.c | 1889 if (rp->maxactive <= 0) { in register_kretprobe()
1891 rp->maxactive = max_t(unsigned int, 10, 2*num_possible_cpus()); in register_kretprobe()
1893 rp->maxactive = num_possible_cpus(); in register_kretprobe()
1898 for (i = 0; i < rp->maxactive; i++) { in register_kretprobe()
|
