Lines Matching +full:pre +full:- +full:programs

1 .. SPDX-License-Identifier: GPL-2.0
26 ------------------------------------------
28 KUnit (Documentation/dev-tools/kunit/index.rst) is an entirely in-kernel system
32 KUnit tests therefore are best written against small, self-contained parts
44 Documentation/dev-tools/kunit/style.rst
47 kselftest (Documentation/dev-tools/kselftest.rst), on the other hand, is
49 programs.
62 details. This aligns well with 'system' or 'end-to-end' testing.
72 and for finding corner-cases which are not covered by the appropriate test.
74 Documentation/dev-tools/gcov.rst is GCC's coverage testing tool, which can be
75 used with the kernel to get global or per-module coverage. Unlike KCOV, it
76 does not record per-task coverage. Coverage data can be read from debugfs,
79 Documentation/dev-tools/kcov.rst is a feature which can be built in to the
80 kernel to allow capturing coverage on a per-task level. It's therefore useful
97   Documentation/dev-tools/kmemleak.rst
98 * KASAN detects invalid memory accesses such as out-of-bounds and
99   use-after-free errors. See Documentation/dev-tools/kasan.rst
101   overflows. See Documentation/dev-tools/ubsan.rst
102 * KCSAN detects data races. See Documentation/dev-tools/kcsan.rst
103 * KFENCE is a low-overhead detector of memory issues, which is much faster than
104   KASAN and can be used in production. See Documentation/dev-tools/kfence.rst
106   Documentation/locking/lockdep-design.rst
127 Sparse can help test the kernel by performing type-checking, lock checking,
129 examining the code. See the Documentation/dev-tools/sparse.rst documentation
145 Documentation/dev-tools/coccinelle.rst documentation page for details.
151 -----------------------------
166 --------------------------------------
169 pre-processor so it's easier to check for bugs in macros using Coccinelle.