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/poll/prj.conf

6 lines
99 B
Plaintext
Raw Normal View History

tests: add poll kernel test Change-Id: I87af7c404b9c77fd82746e5bc2baf4df74d9380c Signed-off-by: Benjamin Walsh <walsh.benj@gmail.com>
2017-01-30 05:34:53 +08:00
CONFIG_ZTEST=y
CONFIG_POLL=y
k_poll: expose to user mode k_poll is now accessible from user mode. A memory allocation takes place from the caller's resource pool to copy the provided poll_events array; this can be large enough to make allocating it on the stack not preferable. k_poll_signal are now proper kernel objects. Two APIs have been added, one to reset the signaled state and one to check the current signaled state and result value. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-05-08 07:52:57 +08:00
CONFIG_DYNAMIC_OBJECTS=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