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

24 lines
508 B
Plaintext
Raw Normal View History

tests: add CONFIG_TEST for marking tests Mark tests with CONFIG_TEST to allow for test specific setup and configuration. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-01-07 05:15:53 +08:00
CONFIG_TEST=y
First commit Signed-off-by: <inaky.perez-gonzalez@intel.com>
2015-04-11 07:44:37 +08:00
# all printf, fprintf to stdout go to console
CONFIG_STDOUT_CONSOLE=y
# eliminate timer interrupts during the benchmark
tests: app_kernel: Add user support Add user thread support to message queue, semaphore, mutex and pipe tests. Mailbox and memory map tests are restricted from executing from user threads. Signed-off-by: Peter Mitsis <peter.mitsis@intel.com>
2023-10-19 01:23:59 +08:00
CONFIG_SYS_CLOCK_TICKS_PER_SEC=1
tests/kernel/benchmarks: Disable TICKLESS_KERNEL for "no tick" tests These tests was written to try to eliminate timer interrupts, but the mechanism chosen (setting TICKS_PER_SECOND to 1) is dangerously susceptible to overflow conditions on systems with fast cycle counters and high timeout durations. Actually the tests pass just fine if you use a conventional tick rate and use a tickless-capable driver (which eliminates interrupts too, which is the whole point), but there's no easy way in kconfig to do an "if" to select that condition for capable systems only. Just disable tickless to keep the same behavior. Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2018-10-10 05:21:12 +08:00
tests: benchmarks: use main thread for benchmark Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-08-24 20:21:50 +08:00
CONFIG_MAIN_THREAD_PRIORITY=6
tests: benchmarks: force assertions off These would interfere with size/footprint data. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-05-25 04:12:33 +08:00
CONFIG_FORCE_NO_ASSERT=y
benchmarks: app_kernel: Disable userspace for benchmarks Disable userspace for benchmarks because it changes the KPI numbers. It will be re-enabled once the required code is in place. Signed-off-by: Adithya Baglody <adithya.nagaraj.baglody@intel.com>
2018-05-31 13:05:31 +08:00
tests: explicitly disable HW Stack Protection when needed Some ARM platforms, now, enable HW Stack Protection by default in the Board definition. So if some tests need to run without stack protection, it is not sufficient to disable TEST_HW_STACK_PROTECTION; we need to explicitly disable HW_STACK_PROTECTION. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2020-09-24 16:56:44 +08:00
# Disable HW Stack Protection (see #28664)
benchmarks: app_kernel: Disable userspace for benchmarks Disable userspace for benchmarks because it changes the KPI numbers. It will be re-enabled once the required code is in place. Signed-off-by: Adithya Baglody <adithya.nagaraj.baglody@intel.com>
2018-05-31 13:05:31 +08:00
CONFIG_TEST_HW_STACK_PROTECTION=n
tests: explicitly disable HW Stack Protection when needed Some ARM platforms, now, enable HW Stack Protection by default in the Board definition. So if some tests need to run without stack protection, it is not sufficient to disable TEST_HW_STACK_PROTECTION; we need to explicitly disable HW_STACK_PROTECTION. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2020-09-24 16:56:44 +08:00
CONFIG_HW_STACK_PROTECTION=n
tests: add FP formatting to all tests that require it Tests that include floating-point format specifications may need cbprintf FP support. Make sure it's available. Signed-off-by: Peter Bigot <peter.bigot@nordicsemi.no>
2020-11-16 23:11:30 +08:00
CONFIG_CBPRINTF_FP_SUPPORT=y
benchmarks: app_kernel: limits to 1 CPU The app_kernel test hangs or crashes on qemu_x86_64 when more than one CPU is enabled. So limits the number of CPUs to 1 even when SMP is enabled. This issue has probably been masked for some time because the test was previously marked as being "slow". Signed-off-by: Martin Åberg <martin.aberg@gaisler.com>
2021-01-08 04:16:05 +08:00
# Can only run under 1 CPU
tests: move to using CONFIG_MP_MAX_NUM_CPUS For tests that set CONFIG_MP_NUM_CPUS, switch to using CONFIG_MP_MAX_NUM_CPUS instead as we work to phase out CONFIG_MP_NUM_CPUS. Signed-off-by: Kumar Gala <kumar.gala@intel.com>
2022-10-20 06:54:41 +08:00
CONFIG_MP_MAX_NUM_CPUS=1
tests: Add CONFIG_PIPES to tests that use pipes Use of pipes is now configurable. All tests that use pipes must enable that feature. (Note: no sample projects currently use pipes.) Signed-off-by: Peter Mitsis <peter.mitsis@intel.com>
2022-08-15 21:20:20 +08:00
# Enable pipes
CONFIG_PIPES=y
tests: app_kernel: Add custom syscalls Adds two custom syscalls. The first allows a user thread to change its priority to a higher priority level. The second is used to obtain a timestamp from a user thread. Signed-off-by: Peter Mitsis <peter.mitsis@intel.com>
2023-10-20 03:53:53 +08:00
CONFIG_APPLICATION_DEFINED_SYSCALL=y
CONFIG_TIMING_FUNCTIONS=y