Jeremy Kerr 3d6e446238 kunit: unify module and builtin suite definitions ... Currently, KUnit runs built-in tests and tests loaded from modules differently. For built-in tests, the kunit_test_suite{,s}() macro adds a list of suites in the .kunit_test_suites linker section. However, for kernel modules, a module_init() function is used to run the test suites. This causes problems if tests are included in a module which already defines module_init/exit_module functions, as they'll conflict with the kunit-provided ones. This change removes the kunit-defined module inits, and instead parses the kunit tests from their own section in the module. After module init, we call __kunit_test_suites_init() on the contents of that section, which prepares and runs the suite. This essentially unifies the module- and non-module kunit init formats. Tested-by: Maíra Canal <maira.canal@usp.br> Reviewed-by: Brendan Higgins <brendanhiggins@google.com> Signed-off-by: Jeremy Kerr <jk@codeconstruct.com.au> Signed-off-by: Daniel Latypov <dlatypov@google.com> Signed-off-by: David Gow <davidgow@google.com> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>		2022-07-11 17:13:09 -06:00
..
debug_kmemleak.c
decompress.c
internal.h
kallsyms.c
kdb.c
livepatch.c
main.c	kunit: unify module and builtin suite definitions	2022-07-11 17:13:09 -06:00
Makefile
procfs.c
signing.c
strict_rwx.c
sysfs.c
tracking.c
tree_lookup.c
version.c