• David Gow's avatar
    kunit: Add "hooks" to call into KUnit when it's built as a module · 7170b7ed
    David Gow authored
    KUnit has several macros and functions intended for use from non-test
    code. These hooks, currently the kunit_get_current_test() and
    kunit_fail_current_test() macros, didn't work when CONFIG_KUNIT=m.
    
    In order to support this case, the required functions and static data
    need to be available unconditionally, even when KUnit itself is not
    built-in. The new 'hooks.c' file is therefore always included, and has
    both the static key required for kunit_get_current_test(), and a table
    of function pointers in struct kunit_hooks_table. This is filled in with
    the real implementations by kunit_install_hooks(), which is kept in
    hooks-impl.h and called when the kunit module is loaded.
    
    This can  be extended for future features which require similar
    "hook" behaviour, such as static stubs, by simply adding new entries to
    the struct, and the appropriate code to set them.
    
    Fixed white-space errors during commit:
    Shuah Khan <skhan@linuxfoundation.org>
    
    Resolved merge conflicts with:
    db105c37 ("kunit: Export kunit_running()")
    This patch supersedes the above.
    Shuah Khan <skhan@linuxfoundation.org>
    Signed-off-by: default avatarDavid Gow <davidgow@google.com>
    Reviewed-by: default avatarRae Moar <rmoar@google.com>
    Reviewed-by: default avatarBrendan Higgins <brendanhiggins@google.com>
    Signed-off-by: default avatarShuah Khan <skhan@linuxfoundation.org>
    7170b7ed
usage.rst 23.3 KB