zephyr/tests/kernel/poll/prj.conf

CONFIG_ZTEST=y
CONFIG_POLL=y
CONFIG_DYNAMIC_OBJECTS=y
CONFIG_TEST_USERSPACE=y
CONFIG_SMP=n
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: Mass SMP disablement on non-SMP-safe tests (Chunk 3 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`