eebf4dd452
kselftest runs as a userspace process. Sometimes we need to test things from kernel space. One way of doing this is by creating a test module. Currently doing so requires developers to write a bunch of boiler plate in the module if kselftest is to be used to run the tests. This means we currently have a load of duplicate code to achieve these ends. If we have a uniform method for implementing test modules then we can reduce code duplication, ensure uniformity in the test framework, ease code maintenance, and reduce the work required to create tests. This all helps to encourage developers to write and run tests. Add a C header file that can be included in test modules. This provides a single point for common test functions/macros. Implement a few macros that make up the start of the test framework. Add documentation for new kselftest header to kselftest documentation. Acked-by: Kees Cook <keescook@chromium.org> Signed-off-by: Tobin C. Harding <tobin@kernel.org> Signed-off-by: Shuah Khan <shuah@kernel.org> |
||
|---|---|---|
| .. | ||
| coccinelle.rst | ||
| conf.py | ||
| gcov.rst | ||
| gdb-kernel-debugging.rst | ||
| index.rst | ||
| kasan.rst | ||
| kcov.rst | ||
| kgdb.rst | ||
| kmemleak.rst | ||
| kselftest.rst | ||
| sparse.rst | ||
| ubsan.rst | ||