OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/tests/kernel/workq/work_queue_api/prj.conf

9 lines
173 B
Plaintext
Raw Normal View History

tests: kernel: added test_workq_api Change-Id: Iaadba1a720130a496a83c245c7da4b95dff168fd Signed-off-by: Sharron LIU <sharron.liu@intel.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-11-30 15:14:22 +08:00
CONFIG_ZTEST=y
CONFIG_IRQ_OFFLOAD=y
kernel: add user mode work_q capability This allows for workqueues to be started in user mode. No additional kernel objects or system calls are defined other than starting the workqueue in user mode; for permission purposes the embedded queue and thread objects are sufficient. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-11-13 06:25:19 +08:00
CONFIG_HEAP_MEM_POOL_SIZE=1024
CONFIG_THREAD_NAME=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
kernel: Introduce k_work_poll This commit adds new k_work_poll interface. It allows to submit given work to a workqueue automatically when one of the watched pollable objects changes its state. Signed-off-by: Piotr Zięcik <piotr.ziecik@nordicsemi.no> Signed-off-by: Peter A. Bigot <pab@pabigot.com>
2019-09-27 15:16:25 +08:00
CONFIG_POLL=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
tests: resolve shippable errors During previous commit Shippable let me know about errors for some boards, resolved them. Signed-off-by: Maksim Masalski <maksim.masalski@intel.com>
2020-05-12 16:13:48 +08:00
CONFIG_MAX_THREAD_BYTES=3