zephyr/tests/kernel/mutex/sys_mutex/prj.conf

CONFIG_MAIN_THREAD_PRIORITY=10
CONFIG_ZTEST=y
CONFIG_TEST_USERSPACE=y
tests: kernel: mutex: minor rework Rename task -> thread and use main as the entry thread saving 512 bytes of RAM. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-08-24 17:05:35 +08:00			`CONFIG_MAIN_THREAD_PRIORITY=10`
tests: mutex: convert legacy test to ztest Make legacy test case use of ztest apis to support ztest framework. Reduce ztest stack size to 512 otherwise region 'SRAM' will overflow for nucleo board. Signed-off-by: Punit Vara <punit.vara@intel.com> 2017-10-30 18:38:40 +08:00			`CONFIG_ZTEST=y`
tests: CONFIG_TEST_USERSPACE now off by default Unlike CONFIG_HW_STACK_PROTECTION, which greatly helps expose stack overflows in test code, activating userspace without putting threads in user mode is of very limited value. Now CONFIG_TEST_USERSPACE is off by default. Any test which puts threads in user mode will need to set CONFIG_TEST_USERSPACE. This should greatly increase sanitycheck build times as there is non-trivial build time overhead to enabling this feature. This also allows some tests which failed the build on RAM-constrained platforms to compile properly. tests/drivers/build_all is a special case; it doesn't put threads in user mode, but we want to ensure all the syscall handlers compile properly. Fixes: #15103 (and probably others) Signed-off-by: Andrew Boie <andrew.p.boie@intel.com> 2019-04-06 06:39:50 +08:00			`CONFIG_TEST_USERSPACE=y`