[rtems commit] validation: Avoid double fatal error
Sebastian Huber
sebh at rtems.org
Tue Apr 12 06:34:34 UTC 2022
Module: rtems
Branch: master
Commit: 873e7dab34a247f36ce7c0ec6dbe39751515990b
Changeset: http://git.rtems.org/rtems/commit/?id=873e7dab34a247f36ce7c0ec6dbe39751515990b
Author: Sebastian Huber <sebastian.huber at embedded-brains.de>
Date: Tue Apr 12 08:32:11 2022 +0200
validation: Avoid double fatal error
In the SMP_FATAL_MULTITASKING_START_ON_NOT_ONLINE_PROCESSOR test case,
the boot processor ends up in the idle body. Do not issue a fatal error
here and instead enter the idle loop. The secondary processor will
terminate the system.
---
testsuites/validation/ts-fatal-start-on-not-online-processor.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/testsuites/validation/ts-fatal-start-on-not-online-processor.c b/testsuites/validation/ts-fatal-start-on-not-online-processor.c
index 9e046bbde1..9cc981e381 100644
--- a/testsuites/validation/ts-fatal-start-on-not-online-processor.c
+++ b/testsuites/validation/ts-fatal-start-on-not-online-processor.c
@@ -73,6 +73,8 @@ const char rtems_test_name[] = "FatalStartOnNotOnlineProcessor";
#define FATAL_SYSINIT_RUN ScoreSmpValFatalStartOnNotOnlineProcessor_Run
+#define CONFIGURE_IDLE_TASK_BODY _CPU_Thread_Idle_body
+
#define CONFIGURE_APPLICATION_DOES_NOT_NEED_CLOCK_DRIVER
#define CONFIGURE_MAXIMUM_PROCESSORS 2
More information about the vc
mailing list