summaryrefslogtreecommitdiffstats
path: root/cpukit/score/include/rtems/score/priority.h
diff options
context:
space:
mode:
authorSebastian Huber <sebastian.huber@embedded-brains.de>2016-05-19 11:20:58 +0200
committerSebastian Huber <sebastian.huber@embedded-brains.de>2016-05-20 16:11:02 +0200
commit7dfb4b970cbd22cef170b2f45a41f445406a2ce5 (patch)
treed26b77b23f3e95c52b2b89e147b4e2dd557395b7 /cpukit/score/include/rtems/score/priority.h
parentfat: Fix for invalid cluster sizes (diff)
downloadrtems-7dfb4b970cbd22cef170b2f45a41f445406a2ce5.tar.bz2
score: Add per scheduler instance maximum priority
The priority values are only valid within a scheduler instance. Thus, the maximum priority value must be defined per scheduler instance. The first scheduler instance defines PRIORITY_MAXIMUM. This implies that RTEMS_MAXIMUM_PRIORITY and POSIX_SCHEDULER_MAXIMUM_PRIORITY are only valid for threads of the first scheduler instance. Further API/implementation changes are necessary to fix this. Update #2556.
Diffstat (limited to 'cpukit/score/include/rtems/score/priority.h')
-rw-r--r--cpukit/score/include/rtems/score/priority.h8
1 files changed, 0 insertions, 8 deletions
diff --git a/cpukit/score/include/rtems/score/priority.h b/cpukit/score/include/rtems/score/priority.h
index 0a772f62a2..38f3995e61 100644
--- a/cpukit/score/include/rtems/score/priority.h
+++ b/cpukit/score/include/rtems/score/priority.h
@@ -72,14 +72,6 @@ typedef uint32_t Priority_Control;
#define PRIORITY_DEFAULT_MAXIMUM 255
#endif
-/** This defines the lowest (least important) thread priority. */
-#define PRIORITY_MAXIMUM rtems_maximum_priority
-
-/**
- * This variable contains the configured number of priorities
- */
-extern uint8_t rtems_maximum_priority;
-
#ifdef __cplusplus
}
#endif