diff options
| author | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2016-05-19 11:20:58 +0200 |
|---|---|---|
| committer | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2016-05-20 16:11:02 +0200 |
| commit | 7dfb4b970cbd22cef170b2f45a41f445406a2ce5 (patch) | |
| tree | d26b77b23f3e95c52b2b89e147b4e2dd557395b7 /cpukit/score/include/rtems/score/schedulercbs.h | |
| parent | fat: Fix for invalid cluster sizes (diff) | |
| download | rtems-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/schedulercbs.h')
| -rw-r--r-- | cpukit/score/include/rtems/score/schedulercbs.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/cpukit/score/include/rtems/score/schedulercbs.h b/cpukit/score/include/rtems/score/schedulercbs.h index 5558d6e919..e390532343 100644 --- a/cpukit/score/include/rtems/score/schedulercbs.h +++ b/cpukit/score/include/rtems/score/schedulercbs.h @@ -39,6 +39,8 @@ extern "C" { */ /**@{*/ +#define SCHEDULER_CBS_MAXIMUM_PRIORITY SCHEDULER_EDF_MAXIMUM_PRIORITY + /** * Entry points for the Constant Bandwidth Server Scheduler. * |