From 84e6f15c828869eb7d293096cfcfa0563b5752b3 Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Thu, 10 Nov 2016 12:02:28 +0100 Subject: score: Robust thread dispatch On SMP configurations, it is a fatal error to call blocking operating system with interrupts disabled, since this prevents delivery of inter-processor interrupts. This could lead to executing threads which are not allowed to execute resulting in undefined behaviour. The ARM Cortex-M port has a similar problem, since the interrupt state is not a part of the thread context. Update #2811. --- cpukit/sapi/src/interrtext.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'cpukit/sapi/src/interrtext.c') diff --git a/cpukit/sapi/src/interrtext.c b/cpukit/sapi/src/interrtext.c index edf09dbd93..ce69461cab 100644 --- a/cpukit/sapi/src/interrtext.c +++ b/cpukit/sapi/src/interrtext.c @@ -57,7 +57,8 @@ static const char *const internal_error_text[] = { "INTERNAL_ERROR_POSIX_INIT_THREAD_ENTRY_IS_NULL", "INTERNAL_ERROR_THREAD_QUEUE_DEADLOCK", "INTERNAL_ERROR_THREAD_QUEUE_ENQUEUE_STICKY_FROM_BAD_STATE", - "INTERNAL_ERROR_BAD_THREAD_DISPATCH_DISABLE_LEVEL" + "INTERNAL_ERROR_BAD_THREAD_DISPATCH_DISABLE_LEVEL", + "INTERNAL_ERROR_BAD_THREAD_DISPATCH_ENVIRONMENT" }; const char *rtems_internal_error_text( rtems_fatal_code error ) -- cgit v1.2.3