Home
last modified time | relevance | path

Searched refs:nmissed (Results 1 – 9 of 9) sorted by relevance

/linux-6.1.9/kernel/trace/
Dfprobe.c36 fp->nmissed++; in fprobe_handler()
46 fp->nmissed++; in fprobe_handler()
65 fp->nmissed++; in fprobe_kprobe_handler()
118 fp->nmissed = 0; in fprobe_init()
Dtrace_kprobe.c1179 unsigned long nmissed; in probes_profile_seq_show() local
1185 nmissed = trace_kprobe_is_return(tk) ? in probes_profile_seq_show()
1186 tk->rp.kp.nmissed + tk->rp.nmissed : tk->rp.kp.nmissed; in probes_profile_seq_show()
1190 nmissed); in probes_profile_seq_show()
/linux-6.1.9/include/linux/
Dfprobe.h29 unsigned long nmissed; member
Dkprobes.h67 unsigned long nmissed; member
152 int nmissed; member
/linux-6.1.9/samples/kprobes/
Dkretprobe_example.c102 my_kretprobe.nmissed, my_kretprobe.kp.symbol_name); in kretprobe_exit()
/linux-6.1.9/samples/fprobe/
Dfprobe_example.c143 symbol, nhit, sample_probe.nmissed); in fprobe_exit()
/linux-6.1.9/Documentation/trace/
Dfprobe.rst149 The `fprobe` data structure has `fprobe::nmissed` counter field as same as
159 The `fprobe::nmissed` field counts up in both cases. Therefore, the former
Dkprobes.rst57 a post_handler, and how to use the maxactive and nmissed fields of
137 some probes. In the kretprobe struct, the nmissed field is set to
164 object available, then in addition to incrementing the nmissed count,
567 handlers won't be run in that instance, and the kprobe.nmissed member
/linux-6.1.9/kernel/
Dkprobes.c1232 p->nmissed++; in kprobes_inc_nmissed_count()
1235 kp->nmissed++; in kprobes_inc_nmissed_count()
1624 p->nmissed = 0; in register_kprobe()
2086 rp->nmissed++; in NOKPROBE_SYMBOL()
2117 rp->nmissed++; in pre_handler_kretprobe()
2234 rp->nmissed = 0; in register_kretprobe()
2261 rp->nmissed = 0; in register_kretprobe()