Lines Matching refs:coverage
1 kcov: code coverage for fuzzing
4 kcov exposes kernel code coverage information in a form suitable for coverage-
7 basis, and thus it can capture precise coverage of a single system call.
9 Note that kcov does not aim to collect as much coverage as possible. It aims
10 to collect more or less stable coverage that is function of syscall inputs.
11 To achieve this goal it does not collect coverage in soft/hard interrupts
38 The following program demonstrates coverage collection from within a test
68 /* A single fd descriptor allows coverage collection on a single
82 /* Enable coverage collection on the current thread. */
85 /* Reset coverage from the tail of the ioctl() call. */
93 /* Disable coverage collection for the current thread. After this call
94 * coverage can be enabled for a different thread.
123 If a program needs to collect coverage from several threads (independently),
128 mmaps coverage buffer and then forks child processes in a loop. Child processes
129 only need to enable coverage (disable happens automatically on thread end).
134 Comparison operands collection is similar to coverage collection:
208 Note that the kcov modes (coverage collection or comparison operands) are
211 Remote coverage collection
214 With KCOV_ENABLE coverage is collected only for syscalls that are issued
216 coverage for arbitrary parts of the kernel code, provided that those parts
219 This allows to collect coverage from two types of kernel background
226 To enable collecting coverage from a global background thread or from a
249 When a particular userspace process collects coverage via a common
250 handle, kcov will collect coverage for each code section that is annotated
252 task_struct. However non common handles allow to collect coverage
307 /* Enable coverage collection via common handle and from USB bus #1. */