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

11 lines
248 B
Plaintext
Raw Normal View History

tests: add threads scheduling test case with unified kernel this commit cover thread scheduling relevant apis k_current_get() k_sched_lock() k_sched_unlock() k_yield() k_sleep() k_wakeup() k_busy_wait() k_sched_time_slice_set() Change-Id: Ie449db3dda910bc1bafc0b5a04633f284e7f1dc3 Signed-off-by: jing wang <jing.j.wang@intel.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-12-23 09:16:04 +08:00
CONFIG_ZTEST=y
tests: kernel: scheule_api: move to new ztest API Move tests/kernel/sched/schedule_api to new ztest API. Signed-off-by: Ming Shao <ming.shao@intel.com>
2022-08-15 14:39:45 +08:00
CONFIG_ZTEST_NEW_API=y
tests: kernel: added test case k_is_preempt_thread tests/kernel/threads_scheduling/schedule_api: added test case to cover k_is_preempt_thread. Jira: ZEP-1242 Change-Id: I4327438dffaa59abcfe1e41813b45abee88506b2 Signed-off-by: Sharron LIU <sharron.liu@intel.com>
2017-02-13 16:04:50 +08:00
CONFIG_IRQ_OFFLOAD=y
tests: kernel: Stress test for preemptive scheduling. Tests if preemptive threads are picked up as per priority. This creates 10 threads with priority in increasing order from 1 to N and each thread prints an Alphabet. This test fails when threads are picked up out of order. Jira: ZEP-2370 Signed-off-by: Youvedeep Singh <youvedeep.singh@intel.com>
2017-07-27 20:02:50 +08:00
CONFIG_NUM_PREEMPT_PRIORITIES=30
test: scheduling: add configuration item When using Red/black tree ready queue as scheduling algorithm, there are no limit to the number of priority levels. So set the CONFIG_NUM_COOP_PRIORITIES to 30, testcase test_bad_prooritiesi() will prove both cooperative and preemptive thread have no quantitative limit. Signed-off-by: Ying ming <mingx.ying@intel.com>
2020-11-30 13:28:08 +08:00
CONFIG_NUM_COOP_PRIORITIES=30
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_SCHED_SCALABLE=y
test: scheduling: add test case Add a test case of preemptive thread scheduling. The scheduler will select the highest priority and waiting longest thread to be the current thread. Signed-off-by: Ying ming <mingx.ying@intel.com>
2020-08-12 16:00:13 +08:00
CONFIG_MAX_THREAD_BYTES=5
tests: schedule_api: test syscalls from usermode We didn't have any coverage of the system call handlers for k_wakeup() and k_is_preempt(). Increase RAM requirements due to stack alignment constraints on MPU platforms when user mode is enabled. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2019-06-12 07:13:45 +08:00
CONFIG_TEST_USERSPACE=y
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
test: schedule_api : test some negative test Add error test of api to improve branch and line coverage in sched.c. Signed-off-by: Ying ming <mingx.ying@intel.com>
2021-03-11 11:17:03 +08:00
CONFIG_ZTEST_FATAL_HOOK=y