7b1ee5cf13
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>
13 lines
283 B
Plaintext
13 lines
283 B
Plaintext
CONFIG_TEST=y
|
|
# all printf, fprintf to stdout go to console
|
|
CONFIG_STDOUT_CONSOLE=y
|
|
|
|
# eliminate timer interrupts during the benchmark
|
|
CONFIG_SYS_CLOCK_TICKS_PER_SEC=1
|
|
CONFIG_TICKLESS_KERNEL=n
|
|
|
|
CONFIG_MAIN_STACK_SIZE=16384
|
|
CONFIG_FORCE_NO_ASSERT=y
|
|
|
|
CONFIG_TEST_HW_STACK_PROTECTION=n
|