From 6be690d24cb7ea353b8c826c4b637f8b39235bbd Mon Sep 17 00:00:00 2001 From: Gerwin Klein Date: Wed, 10 Jul 2024 16:04:29 +1000 Subject: [PATCH] scheduler: resume does preempt If we're seeing failures on this test, they need to be investigated. The resume invocation is definitely supposed to call the scheduler and leave with the highest priority thread running. Signed-off-by: Gerwin Klein --- apps/sel4test-tests/src/tests/scheduler.c | 8 -------- 1 file changed, 8 deletions(-) diff --git a/apps/sel4test-tests/src/tests/scheduler.c b/apps/sel4test-tests/src/tests/scheduler.c index 71aef0cb..56e909cc 100644 --- a/apps/sel4test-tests/src/tests/scheduler.c +++ b/apps/sel4test-tests/src/tests/scheduler.c @@ -182,14 +182,6 @@ static int suspend_test_helper_1(seL4_CPtr t1, seL4_CPtr t2a, seL4_CPtr t2b) /* We should have been preempted immediately, so by the time we run again, * the suspend_test_step should be 5. */ - -#if 1 // WE HAVE A BROKEN SCHEDULER IN SEL4 - /* FIXME: The seL4 scheduler is broken, and seL4_TCB_Resume will not - * preempt. The only way to get preempted is to force it ourselves (or wait - * for a timer tick). */ - seL4_Yield(); -#endif - CHECK_STEP(suspend_test_step, 5); return sel4test_get_result();