Setting a deadline is not a schedule point. This makes it a perfect place to verify the behavior of the new k_reschedule() routine at both thread and ISR level. Signed-off-by: Peter Mitsis <peter.mitsis@intel.com>
13 lines
302 B
Plaintext
13 lines
302 B
Plaintext
CONFIG_ZTEST=y
|
|
CONFIG_MP_MAX_NUM_CPUS=1
|
|
CONFIG_TEST_RANDOM_GENERATOR=y
|
|
CONFIG_SCHED_DEADLINE=y
|
|
CONFIG_BT=n
|
|
|
|
# Deadline is not compatible with MULTIQ, so we have to pick something
|
|
# specific instead of using the board-level default.
|
|
CONFIG_SCHED_DUMB=y
|
|
|
|
CONFIG_IRQ_OFFLOAD=y
|
|
CONFIG_IRQ_OFFLOAD_NESTED=n
|