zephyr/tests/benchmarks/timing_info/prj_userspace.conf

CONFIG_TEST=y
CONFIG_EXECUTION_BENCHMARKING=y
CONFIG_TEST_RANDOM_GENERATOR=y
CONFIG_HEAP_MEM_POOL_SIZE=256
CONFIG_MAIN_STACK_SIZE=2048
CONFIG_FORCE_NO_ASSERT=y
CONFIG_APPLICATION_DEFINED_SYSCALL=y
CONFIG_TEST_USERSPACE=y
tests: benchmarks: timing_info: Add userspace related KPIs. Added new KPIs for the userspace benchmarks. 1. Drop to user mode. 2. User thread Creation. 3. Syscall overhead. 4. Validation overhead k object init. 5. Validation overhead k object permission. Signed-off-by: Adithya Baglody <adithya.nagaraj.baglody@intel.com> 2018-07-23 17:19:57 +08:00			`CONFIG_TEST=y`
			`CONFIG_EXECUTION_BENCHMARKING=y`
			`CONFIG_TEST_RANDOM_GENERATOR=y`
			`CONFIG_HEAP_MEM_POOL_SIZE=256`
			`CONFIG_MAIN_STACK_SIZE=2048`
			`CONFIG_FORCE_NO_ASSERT=y`
			`CONFIG_APPLICATION_DEFINED_SYSCALL=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`