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

11 lines
243 B
Plaintext
Raw Normal View History

tests: add ringbuffer api test and combine original test We already have a test for ring buffers, this combines it with an API test. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-01-14 07:48:33 +08:00
CONFIG_ZTEST=y
tests: lib: move ringbuffer to new ztest API Move test ringbuffer to use new ztest API. Signed-off-by: li biao <biao1x.li@intel.com>
2022-08-18 12:53:26 +08:00
CONFIG_ZTEST_NEW_API=y
tests: lib: ringbuffer: Update test to use ztress Updated test to use stress testing framework instead of implementing own framework. Signed-off-by: Krzysztof Chruscinski <krzysztof.chruscinski@nordicsemi.no>
2021-12-16 18:58:56 +08:00
CONFIG_ZTRESS=y
kconfig: Rename the TEST_EXTRA stack size option to align with the rest All stack sizes should end with STACK_SIZE. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2022-02-18 00:09:09 +08:00
CONFIG_TEST_EXTRA_STACK_SIZE=1024
tests: add ringbuffer api test and combine original test We already have a test for ring buffers, this combines it with an API test. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-01-14 07:48:33 +08:00
CONFIG_IRQ_OFFLOAD=y
CONFIG_RING_BUFFER=y
tests: lib: ringbuffer: Add tests for preemption Added test cases that validates if ring buffer handles correctly case with single producer single consumer from different contexts. Signed-off-by: Krzysztof Chruscinski <krzysztof.chruscinski@nordicsemi.no>
2021-07-30 14:18:36 +08:00
CONFIG_TEST_RANDOM_GENERATOR=y
tests: lib: ringbuffer: Update test to use ztress Updated test to use stress testing framework instead of implementing own framework. Signed-off-by: Krzysztof Chruscinski <krzysztof.chruscinski@nordicsemi.no>
2021-12-16 18:58:56 +08:00
CONFIG_ENTROPY_GENERATOR=y
CONFIG_XOSHIRO_RANDOM_GENERATOR=y
tests/lib/ringbuffer: Run with one CPU The stress ('scuse me, "zstress") cases here are all written to exercise reader/writer threads at different priority combinations. That's defeated if the threads are allowed to run on different CPUs (because being "low" priority doesn't matter if you have a spare CPU to run on). There is also extensive use of stack buffers to pass data through the ring buffer zero copy implementation, which runs afoul of the KERNEL_COHERENCE rules on intel_adsp platforms (where stack memory is incoherent between CPUs and can't be shared like that). Fix both issues by just setting CONFIG_MP_NUM_CPUS=1 Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2022-01-22 05:08:42 +08:00
CONFIG_MP_NUM_CPUS=1