On Mon, Nov 21, 2022 at 7:16 PM David Gow davidgow@google.com wrote:
Reviewed-by: Daniel Latypov dlatypov@google.com
Looks good to me, but some small optional nits about the Documentation.
I'm a bit sad that the kunit_fail_current_test() macro is now a bit more complicated (has two definitions).
I'm not too happy with it either, but I think it's worth having the printf() format string checking, as well as making it possible to optimise the call out (without needing LTO), and I can't think of a better way of doing that at the moment.
The only other option I can think of would be to have lots of #ifdefs for the _contents_ of the functions, and that seemed more ugly to me.
Sorry, I should have been more clear. I'm fine with it as-is.
It's just a bit sad that it could have remained a single definition, but that would sacrifice performance. The version in this patch can avoid the call to __kunit_fail_current_test() via static key, so that's more important.
Optional: perhaps it's long enough now that we should have a comment after the #endif, i.e. #endif /* IS_BUILTIN(CONFIG_KUNIT) */
Makes sense to me. Will add in v3.
<snip>
diff --git a/Documentation/dev-tools/kunit/usage.rst b/Documentation/dev-tools/kunit/usage.rst index 2737863ef365..e70014b82350 100644 --- a/Documentation/dev-tools/kunit/usage.rst +++ b/Documentation/dev-tools/kunit/usage.rst @@ -625,17 +625,21 @@ as shown in next section: *Accessing The Current Test*. Accessing The Current Test
-In some cases, we need to call test-only code from outside the test file. -For example, see example in section *Injecting Test-Only Code* or if -we are providing a fake implementation of an ops struct. Using -``kunit_test`` field in ``task_struct``, we can access it via -``current->kunit_test``. +In some cases, we need to call test-only code from outside the test file, +for example, when providing a fake implementation of a function, or to fail
nit: there are two spaces after "for example, "
Personal preference: I'd rather keep "For example," as the start of a new sentence.
+any current test from within an error handler.
Hmm... I found it a bit ugly to keep "For example" at the start of the sentence, as we then have to stick a (possibly duplicated) verb in to make it actually a sentence.
How about: In some cases, we need to call test-only code from outside the test file. For example, this is useful when providing a fake implementation of a function, or if we wish to fail the current test from within an error handler.
I see what you mean. The initial wording is good as-is, I think. I thought I had some ideas of how to reword it, but they don't sound so good when I actually write them out.
+We can do this via the ``kunit_test`` field in ``task_struct``, which we can +access using the ``kunit_get_current_test`` function in ``kunit/test-bug.h``.
Personal preference: kunit_get_current_test() IMO that would make it easier to pick up when the reader is quickly scanning over.
Agreed, will fix in v3.
-The example below includes how to implement "mocking": +``kunit_get_current_test`` requires KUnit be built-in to the kernel, i.e. +``CONFIG_KUNIT=y``. It is safe to call even if KUnit is not enabled, is built as a module, +or no test is currently running, in which case it will quickly return ``NULL``.
I find this sentence a bit confusing.
I think it's trying to convey that
- it can be called no matter how the kernel is built or what cmdline
args are given
- but it doesn't work properly for CONFIG_KUNIT=m
- for CONFIG_KUNIT=n, it's a static inline func that just returns NULL
- when booting with `kunit.enabled=0`, it's fast (thanks to static keys)
Yeah: that's the goal.
But the current wording basically says "the func requires CONFIG_KUNIT=y" then says it's safe to call it even if CONFIG_KUNIT=n. It feels a bit whiplashy.
Should this be reworded to say the function can be used regardless of whether KUnit is enabled but add a `note` block about how it doesn't properly for CONFIG_KUNIT=m?
How about: ``kunit_get_current_test()`` is safe to call even if KUnit is not enabled. If KUnit is not enabled (or was built as a module), or no test is running, it will return NULL.
Or: ``kunit_get_current_test()`` is always available, but will only return a test if KUnit is built-in to the kernel (i.e, CONFIG_KUNIT=y). In all other cases, it will return NULL.
We could add a: This will compile to either a no-op or a static key, so will have
*static key check?
negligible performance impact when no test is running.
Thoughts?
Regardless, the plan is to eventually get rid of the restriction with modules, so hopefully that part of the awkwardness won't last too long.
I think both of these work, w/ a slight preference to the first. I think it more clearly explains how the function behaves, even if the gotcha "this function won't do what you expect with moduels" is not immediately apparent. But hopefully we can fix that soon so this becomes a moot point. I also think it works better for the section down below about kunit_fail_current_test().
Up to you if you want to include the bit about the static key. I can see arguments either way.
Daniel
+The example below uses this to implement a "mock" implementation of a function, ``foo``:
.. code-block:: c
#include <linux/sched.h> /* for current */
#include <kunit/test-bug.h> /* for kunit_get_current_test */ struct test_data { int foo_result;@@ -644,7 +648,7 @@ The example below includes how to implement "mocking":
static int fake_foo(int arg) {
struct kunit *test = current->kunit_test;
struct kunit *test = kunit_get_current_test(); struct test_data *test_data = test->priv; KUNIT_EXPECT_EQ(test, test_data->want_foo_called_with, arg);@@ -675,7 +679,7 @@ Each test can have multiple resources which have string names providing the same flexibility as a ``priv`` member, but also, for example, allowing helper functions to create resources without conflicting with each other. It is also possible to define a clean up function for each resource, making it easy to -avoid resource leaks. For more information, see Documentation/dev-tools/kunit/api/test.rst. +avoid resource leaks. For more information, see Documentation/dev-tools/kunit/api/resource.rst.
Oops, thanks for cleaning this up. I guess I forgot to update this when splitting out resource.rst or my change raced with the rewrite of this file.
Failing The Current Test
@@ -703,3 +707,6 @@ structures as shown below: static void my_debug_function(void) { } #endif
+Note that ``kunit_fail_current_test`` requires KUnit be built-in to the kernel, i.e. +``CONFIG_KUNIT=y``. It is safe to call even if KUnit is not enabled, is built as a module, +or no test is currently running, but will do nothing.
This is the same wording as above. I think it's clearer since what it's trying to convey is simpler, so it's probably fine.
But if we do end up thinking of a good way to reword the previous bit, we might want to reword it here too.
Yeah: I wrote this one first, then copied it above, so that's why this one is a bit simpler. If we come up with something better for the first one, we can keep it.
_Maybe_ if we moved things to a .. note block, then we could share that between both of these sections, though that has its own issues.