From 7dfb4b970cbd22cef170b2f45a41f445406a2ce5 Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Thu, 19 May 2016 11:20:58 +0200 Subject: 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. --- cpukit/score/include/rtems/score/schedulercbs.h | 2 ++ 1 file changed, 2 insertions(+) (limited to 'cpukit/score/include/rtems/score/schedulercbs.h') 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. * -- cgit v1.2.3