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
67 	/* A single fd descriptor allows coverage collection on a single
81 	/* Enable coverage collection on the current thread. */
84 	/* Reset coverage from the tail of the ioctl() call. */
92 	/* Disable coverage collection for the current thread. After this call
93 	 * coverage can be enabled for a different thread.
122 If a program needs to collect coverage from several threads (independently),
127 mmaps coverage buffer and then forks child processes in a loop. Child processes
128 only need to enable coverage (disable happens automatically on thread end).
133 Comparison operands collection is similar to coverage collection:
205 Note that the kcov modes (coverage collection or comparison operands) are
208 Remote coverage collection
211 With KCOV_ENABLE coverage is collected only for syscalls that are issued
213 coverage for arbitrary parts of the kernel code, provided that those parts
216 This allows to collect coverage from two types of kernel background
223 To enable collecting coverage from a global background thread or from a
246 When a particular userspace proccess collects coverage via a common
247 handle, kcov will collect coverage for each code section that is annotated
249 task_struct. However non common handles allow to collect coverage
302 	/* Enable coverage collection via common handle and from USB bus #1. */