Help¶

This option indicates that a test case puts threads in user mode, and that the build system will [override and] enable USERSPACE if the platform supports it. It should be set in a .conf file on a per-test basis and is not meant to be used outside test cases. Tests with this option should also have the “userspace” filtering tag in their testcase.yaml file.

The userspace APIs are no-ops if userspace is not enabled, so it is OK to enable this even if the test will run on platforms which do not support userspace. The test should still run on those platforms, just with all threads in supervisor mode.

If a test requires that userspace be enabled in order to pass, CONFIG_ARCH_HAS_USERSPACE should be filtered in its testcase.yaml.

Defaults¶

No defaults. Implicitly defaults to n.

Kconfig definition¶

At <Zephyr>/subsys/testsuite/Kconfig:59

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:34 → <Zephyr>/subsys/Kconfig:55

Menu path: (Top) → Sub Systems and OS Services → Testing

config TEST_USERSPACE
    bool "Indicate that this test exercises user mode"
    help
      This option indicates that a test case puts threads in user mode,
      and that the build system will [override and] enable USERSPACE
      if the platform supports it. It should be set in a .conf file on
      a per-test basis and is not meant to be used outside test cases.
      Tests with this option should also have the "userspace" filtering
      tag in their testcase.yaml file.

      The userspace APIs are no-ops if userspace is not enabled, so it is
      OK to enable this even if the test will run on platforms which do
      not support userspace. The test should still run on those platforms,
      just with all threads in supervisor mode.

      If a test requires that userspace be enabled in order to
      pass, CONFIG_ARCH_HAS_USERSPACE should be filtered in its
      testcase.yaml.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)