On Sat, Jun 25, 2022 at 1:10 AM David Gow [off-list ref] wrote:

The kunit_test_suite() macro previously conflicted with module_init,
making it unsuitable for use in the nitro_enclaves test. Now that it's
fixed, we can use it instead of a custom call into internal KUnit
functions to run the test.

As a side-effect, this means that the test results are properly included
with other suites when built-in. To celebrate, enable the test by
default when KUNIT_ALL_TESTS is set (and NITRO_ENCLAVES enabled).

The nitro_enclave tests can now be run via kunit_tool with:
        ./tools/testing/kunit/kunit.py run --arch=x86_64 \
        --kconfig_add CONFIG_PCI=y --kconfig_add CONFIG_SMP=y \
        --kconfig_add CONFIG_HOTPLUG_CPU=y \
        --kconfig_add CONFIG_VIRT_DRIVERS=y \
        --kconfig_add CONFIG_NITRO_ENCLAVES=y \
        'ne_misc_dev_test'

(This is a pretty long command, so it may be worth adding a .kunitconfig
file at some point, instead.)

Reviewed-by: Andra Paraschiv <redacted>
Signed-off-by: David Gow <redacted>

Acked-by: Brendan Higgins <redacted>