2020-01-06 22:28:22 +00:00
|
|
|
obj-$(CONFIG_KUNIT) += kunit.o
|
|
|
|
|
|
|
|
|
|
kunit-objs += test.o \
|
2022-03-28 17:41:43 +00:00
|
|
|
resource.o \
|
kunit: Expose 'static stub' API to redirect functions
Add a simple way of redirecting calls to functions by including a
special prologue in the "real" function which checks to see if the
replacement function should be called (and, if so, calls it).
To redirect calls to a function, make the first (non-declaration) line
of the function:
KUNIT_STATIC_STUB_REDIRECT(function_name, [function arguments]);
(This will compile away to nothing if KUnit is not enabled, otherwise it
will check if a redirection is active, call the replacement function,
and return. This check is protected by a static branch, so has very
little overhead when there are no KUnit tests running.)
Calls to the real function can be redirected to a replacement using:
kunit_activate_static_stub(test, real_fn, replacement_fn);
The redirection will only affect calls made from within the kthread of
the current test, and will be automatically disabled when the test
completes. It can also be manually disabled with
kunit_deactivate_static_stub().
The 'example' KUnit test suite has a more complete example.
Co-developed-by: Daniel Latypov <dlatypov@google.com>
Signed-off-by: Daniel Latypov <dlatypov@google.com>
Signed-off-by: David Gow <davidgow@google.com>
Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
2023-01-31 06:46:40 +00:00
|
|
|
static_stub.o \
|
2019-09-23 09:02:34 +00:00
|
|
|
string-stream.o \
|
2019-09-23 09:02:39 +00:00
|
|
|
assert.o \
|
2020-08-04 20:47:42 +00:00
|
|
|
try-catch.o \
|
2023-07-25 21:25:12 +00:00
|
|
|
executor.o \
|
2023-12-15 07:39:08 +00:00
|
|
|
attributes.o \
|
|
|
|
|
device.o
|
2019-09-23 09:02:37 +00:00
|
|
|
|
2020-03-26 14:25:07 +00:00
|
|
|
ifeq ($(CONFIG_KUNIT_DEBUGFS),y)
|
|
|
|
|
kunit-objs += debugfs.o
|
|
|
|
|
endif
|
|
|
|
|
|
kunit: Add "hooks" to call into KUnit when it's built as a module
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:
db105c37a4d6 ("kunit: Export kunit_running()")
This patch supersedes the above.
Shuah Khan <skhan@linuxfoundation.org>
Signed-off-by: David Gow <davidgow@google.com>
Reviewed-by: Rae Moar <rmoar@google.com>
Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
2023-01-28 07:10:07 +00:00
|
|
|
# KUnit 'hooks' are built-in even when KUnit is built as a module.
|
2023-02-25 01:45:30 +00:00
|
|
|
obj-y += hooks.o
|
kunit: Add "hooks" to call into KUnit when it's built as a module
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:
db105c37a4d6 ("kunit: Export kunit_running()")
This patch supersedes the above.
Shuah Khan <skhan@linuxfoundation.org>
Signed-off-by: David Gow <davidgow@google.com>
Reviewed-by: Rae Moar <rmoar@google.com>
Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
2023-01-28 07:10:07 +00:00
|
|
|
|
2020-01-06 22:28:20 +00:00
|
|
|
obj-$(CONFIG_KUNIT_TEST) += kunit-test.o
|
2019-09-23 09:02:37 +00:00
|
|
|
|
2020-01-06 22:28:20 +00:00
|
|
|
# string-stream-test compiles built-in only.
|
|
|
|
|
ifeq ($(CONFIG_KUNIT_TEST),y)
|
|
|
|
|
obj-$(CONFIG_KUNIT_TEST) += string-stream-test.o
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
obj-$(CONFIG_KUNIT_EXAMPLE_TEST) += kunit-example-test.o
|