zephyr/tests/kernel/mem_slab/mslab_threadsafe/prj.conf

CONFIG_ZTEST=y
CONFIG_SYS_CLOCK_TICKS_PER_SEC=1000
# 1 millisecond
CONFIG_TIMESLICE_SIZE=1

CONFIG_SMP=n
tests: kernel: added memory slab threadsafe test TestPurpose: verify API thread safe in multi-threads environment. Thread safe test is explained with more details here: https://gerrit.zephyrproject.org/r/#/c/9464/7/ test_mpool_threadsafe.c Please comment if you think it necessary as an extensive kernel test. Jira: ZEP-1209 Change-Id: I52a7ff393d72785622c047289e7d92286e131cc7 Signed-off-by: Sharron LIU <sharron.liu@intel.com> 2016-12-30 12:32:06 +08:00			`CONFIG_ZTEST=y`
			`CONFIG_SYS_CLOCK_TICKS_PER_SEC=1000`
			`# 1 millisecond`
			`CONFIG_TIMESLICE_SIZE=1`
tests: Mass SMP disablement on non-SMP-safe tests (Chunk 2 of 3 - this patch was split across pull requests to address CI build time limitations) Zephyr has always been a uniprocessor system, and its kernel tests are rife with assumptions and outright dependence on single-CPU operation (for example: "low priority threads will never run until this high priority thread blocks" -- not true if there's another processor to run it!) About 1/3 of our tests fail right now on x86_64 when dual processor operation is made default. Most of those can probably be recovered on a case-by-case basis with simple changes (and a few of them might represent real bugs in SMP!), but for now let's make sure the full test suite passes by turning the second CPU off. There's still plenty of SMP coverage in the remaining cases. Signed-off-by: Andy Ross <andrew.j.ross@intel.com> 2019-02-23 03:45:23 +08:00
			`CONFIG_SMP=n`