Legacy Issue Number: 12862
Source: Universidad de Cantabria ( Patricia López)
The priority of a FixedPriorityParameter to attach to a SchedulableResource must be of an NFP_Priority type in order to handle it from tools that deal with VSL and parametric descriptions. This is also the case of the priorityCeiling of a MutualExclusionResource. It is convenient to clarified or indicated how to specify the preemption level of the SchedulableResources by means of its scheduling parameters when the StackBasedProtocol is used. If the priority is used for that it should be stated, If an additional parameter is included, then its type should be also an NFP_Type
Reported: MARTE 1.0b2 — Fri, 26 Sep 2008 04:00 GMT
Disposition: Resolved — MARTE 1.0
In order to handle them from tools that deal with VSL and parametric descriptions the
most useful type for priority and ceiling is clearly NFP_Integer, it seems that the use of
Integer instead has been just a typo, and it is easy to solve with no harmful implications.
For simplicity on the one hand, and for the co-existence of both protocols in a combined
EDF-FP platform on the other hand, it is convenient to use the Ceiling attribute to hold
both, the priorityCeiling and the preemptionLevel of a mutualExclusionResource under
the priorityCeiling and StackBased protection protocols respectively. Since both may be
handled with an NFP_Integer type, the restriction already stated in the explanation of the
ceiling attribute (section 10.3.2.9 page 104) is applicable also.
This is the case for some other values using integer types in GRM, so a consistent
modification of them is worth doing.
Updated: Sat, 7 Mar 2015 21:28 GMT