From 797c232daded0ae9557d6d9ca1b3f2815345d471 Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Tue, 22 Jan 2008 15:20:34 +0000 Subject: 2008-01-22 Joel Sherrill * libi2c/README_libi2c: Correct spelling error. * score/src/threadclearstate.c: Improve comment. --- cpukit/score/src/threadclearstate.c | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) (limited to 'cpukit/score') diff --git a/cpukit/score/src/threadclearstate.c b/cpukit/score/src/threadclearstate.c index 8a175fd8cd..f8525b2716 100644 --- a/cpukit/score/src/threadclearstate.c +++ b/cpukit/score/src/threadclearstate.c @@ -75,9 +75,15 @@ void _Thread_Clear_state( /* * If the thread that was unblocked is more important than the heir, - * then we have a new heir. In addition, if the current thread - * is preemptible or we are waking up one of the "pseudo-ISR" system - * threads, then we need to do a context switch. + * then we have a new heir. This may or may not result in a + * context switch. + * + * Normal case: + * If the current thread is preemptible, then we need to do + * a context switch. + * Pseudo-ISR case: + * Even if the thread isn't preemptible, if the new heir is + * a pseudo-ISR system task, we need to do a context switch. */ if ( the_thread->current_priority < _Thread_Heir->current_priority ) { _Thread_Heir = the_thread; -- cgit v1.2.3