zephyr/tests/kernel/msgq/msgq_api/prj.conf

CONFIG_ZTEST=y
CONFIG_IRQ_OFFLOAD=y
CONFIG_TEST_USERSPACE=y
CONFIG_MP_NUM_CPUS=1
tests: add zephyr message queue test case with unified kernel the commit cover basic message queue api testing across contexts and some typical scenario Change-Id: I82bb0c6a5df9d4436f5a98f78d1ad989e32282c8 Signed-off-by: jing wang <jing.j.wang@intel.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2016-12-20 11:22:25 +08:00			`CONFIG_ZTEST=y`
			`CONFIG_IRQ_OFFLOAD=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`
tests: Never disable SMP Disabling SMP mode for certain tests was a one-release thing, done to avoid having to triage every test independently (MANY are not SMP-safe), and with the knowledge that it was probably hiding bugs in the kernel. Turn it on pervasively. Tests are treated with a combination of flagging specific cases as "1cpu" where we have short-running tests that can be independently run in an otherwise SMP environment, and via setting CONFIG_MP_NUM_CPUS=1 where that's not possible (which still runs the full SMP kernel config, but with only one CPU available). Signed-off-by: Andy Ross <andrew.j.ross@intel.com> 2019-08-20 23:42:43 +08:00			`CONFIG_MP_NUM_CPUS=1`