Merge tag 'linux-kselftest-kunit-fixes-5.10-rc5' of...

   re-run kunit_tool.

5. Try to run ``make ARCH=um defconfig`` before running ``kunit.py run``. This

   may help clean up any residual config items which could be causing problems.

6. Finally, try running KUnit outside UML. KUnit and KUnit tests can run be

6. Finally, try running KUnit outside UML. KUnit and KUnit tests can be

   built into any kernel, or can be built as a module and loaded at runtime.

   Doing so should allow you to determine if UML is causing the issue you're

   seeing. When tests are built-in, they will execute when the kernel boots, and

		  This builds unit tests for foo.

		  For more information on KUnit and unit tests in general, please refer

                    to the KUnit documentation in Documentation/dev-tools/kunit

		  to the KUnit documentation in Documentation/dev-tools/kunit/.

                    If unsure, say N

		  If unsure, say N.

Test File and Module Names

the second parameter, in this case, is what the value is expected to be; the

last value is what the value actually is. If ``add`` passes all of these

expectations, the test case, ``add_test_basic`` will pass; if any one of these

expectations fail, the test case will fail.

expectations fails, the test case will fail.

It is important to understand that a test case *fails* when any expectation is

violated; however, the test will continue running, potentially trying other

	kunit_test_suite(example_test_suite);

In the above example the test suite, ``example_test_suite``, would run the test

cases ``example_test_foo``, ``example_test_bar``, and ``example_test_baz``,

cases ``example_test_foo``, ``example_test_bar``, and ``example_test_baz``;

each would have ``example_test_init`` called immediately before it and would

have ``example_test_exit`` called immediately after it.

``kunit_test_suite(example_test_suite)`` registers the test suite with the

such that the definition of that function can be changed without affecting the

rest of the code base. In the kernel this primarily comes from two constructs,

classes, structs that contain function pointers that are provided by the

implementer, and architecture specific functions which have definitions selected

implementer, and architecture-specific functions which have definitions selected

at compile time.

Classes

By default KUnit uses UML as a way to provide dependencies for code under test.

Under most circumstances KUnit's usage of UML should be treated as an

implementation detail of how KUnit works under the hood. Nevertheless, there

are instances where being able to run architecture specific code or test

are instances where being able to run architecture-specific code or test

against real hardware is desirable. For these reasons KUnit supports running on

other architectures.

hardware state in between test cases; if this is not possible, you may only be

able to run one test case per invocation.

.. TODO(brendanhiggins@google.com): Add an actual example of an architecture

.. TODO(brendanhiggins@google.com): Add an actual example of an architecture-

   dependent KUnit test.

KUnit debugfs representation

	KUNIT_ASSERTION(test,						       \

			strcmp(__left, __right) op 0,			       \

			kunit_binary_str_assert,			       \

			KUNIT_INIT_BINARY_ASSERT_STRUCT(test,		       \

			KUNIT_INIT_BINARY_STR_ASSERT_STRUCT(test,	       \

							assert_type,	       \

							#op,		       \

							#left,		       \

test_data/* binary