Merge tag 'linux-kselftest-5.6-rc1-kunit' of...

For the most part, the KUnit core framework (what you use to write the tests)

can compile to any architecture; it compiles like just another part of the

kernel and runs when the kernel boots. However, there is some infrastructure,

kernel and runs when the kernel boots, or when built as a module, when the

module is loaded.  However, there is some infrastructure,

like the KUnit Wrapper (``tools/testing/kunit/kunit.py``) that does not support

other architectures.

of a host operating system; to be clear, it does not require any virtualization

support; it is just a regular program.

Alternatively, kunit and kunit tests can be built as modules and tests will

run when the test module is loaded.

KUnit is fast. Excluding build time, from invocation to completion KUnit can run

several dozen tests in only 10 to 20 seconds; this might not sound like a big

deal to some people, but having such fast and easy to run tests fundamentally

Congratulations, you just ran a KUnit test on the x86 architecture!

In a similar manner, kunit and kunit tests can also be built as modules,

so if you wanted to run tests in this way you might add the following config

options to your ``.config``:

.. code-block:: none

	CONFIG_KUNIT=m

	CONFIG_KUNIT_EXAMPLE_TEST=m

Once the kernel is built and installed, a simple

.. code-block:: bash

	modprobe example-test

...will run the tests.

Writing new tests for other architectures

-----------------------------------------

config PM_QOS_KUNIT_TEST

	bool "KUnit Test for PM QoS features"

	depends on KUNIT

	depends on KUNIT=y

config HMEM_REPORTING

	bool

	.name = "qos-kunit-test",

	.test_cases = pm_qos_test_cases,

};

kunit_test_suite(pm_qos_test_module);

kunit_test_suites(&pm_qos_test_module);