[RTEMS Project] #2795: Overrun Handling for general real-time models
RTEMS trac
trac at rtems.org
Tue Jan 24 14:46:59 UTC 2017
#2795: Overrun Handling for general real-time models
-------------------------------------+-------------------------------------
Reporter: khchen | Owner: Gedare Bloom
| <gedare@…>
Type: enhancement | Status: reopened
Priority: high | Milestone: 4.12
Component: cpukit | Version: 4.11
Severity: blocker | Resolution:
Keywords: Overrun, RMS, SP, |
Scheduler, Periodicity |
-------------------------------------+-------------------------------------
Comment (by kh.chen):
Replying to [comment:14 sebastian.huber]:
> The output of sprmsched01 depends on the target timing:
>
> {{{
> *** BEGIN OF TEST SPRMSCHED 1 ***
>
> Ticks per second in your system: 1000
> Task 0 starts at tick 10.
> Job 1 Task 0 ends at tick 6141.
> Job 1 Task 1 starts at tick 6144.
> Job 1 Task 1 ends at tick 7169.
> Job 2 Task 1 starts at tick 8144.
> Job 2 Task 1 ends at tick 9168.
> Task 0 starts at tick 10009.
> Job 2 Task 0 ends at tick 16140.
> Job 3 Task 1 starts at tick 16145.
> Job 3 Task 1 ends at tick 17169.
> RTEMS_TIMEOUT
> Job 4 Task 1 starts at tick 17172.
> Job 4 Task 1 ends at tick 18196.
> Job 5 Task 1 starts at tick 18199.
> Job 5 Task 1 ends at tick 19223.
> Job 6 Task 1 starts at tick 19226.
> Job 6 Task 1 ends at tick 20250.
> Job 7 Task 1 starts at tick 20253.
> Job 7 Task 1 ends at tick 21277.
> Job 8 Task 1 starts at tick 21280.
> Job 8 Task 1 ends at tick 22304.
> Job 9 Task 1 starts at tick 22307.
> Job 9 Task 1 ends at tick 23331.
> RTEMS_SUCCESSFUL
> Job 10 Task 1 starts at tick 24145.
> Job 10 Task 1 ends at tick
25169.
> Job 11 Task 1 starts at tick 26144.
> Job 11 Task 1 ends at tick
27168.
> Job 12 Task 1 starts at tick 28144.
> Job 12 Task 1 ends at tick
29168.
> *** END OF TEST SPRMSCHED 1 ***
> }}}
>
> Its not clear if the test objectives are checked. Why is
rtems_rate_monotonic_postponed_jobs_count() not used at all?
That function I prepared is for the requirement from the application
layer.
It will not be used directly within the overrun handling.
Since I only focused on the timing behaviors before, so I prepared this
test without testing that.
Now I can add in the test and print out the number of postponed jobs.
--
Ticket URL: <http://devel.rtems.org/ticket/2795#comment:15>
RTEMS Project <http://www.rtems.org/>
RTEMS Project
More information about the bugs
mailing list