diff options
| author | Joel Sherrill <joel.sherrill@OARcorp.com> | 2006-09-07 18:08:25 +0000 |
|---|---|---|
| committer | Joel Sherrill <joel.sherrill@OARcorp.com> | 2006-09-07 18:08:25 +0000 |
| commit | f027b909c92629e6de83cc217c3499ab99ca1060 (patch) | |
| tree | 316ff33fefe4e3cb6f422ac779895cac663b5ca7 | |
| parent | 2006-09-06 Chris Johns <chrisj@rtems.org> (diff) | |
| download | rtems-f027b909c92629e6de83cc217c3499ab99ca1060.tar.bz2 | |
2006-09-07 Ken Peters <ken.peters@jpl.nasa.gov>
PR 1171/doc
* user/timer.t: Correct documentation for rtems_timer_initiate_server.
| -rw-r--r-- | doc/ChangeLog | 5 | ||||
| -rw-r--r-- | doc/user/timer.t | 10 |
2 files changed, 12 insertions, 3 deletions
diff --git a/doc/ChangeLog b/doc/ChangeLog index 9ce6b87690..53b467c93c 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,8 @@ +2006-09-07 Ken Peters <ken.peters@jpl.nasa.gov> + + PR 1171/doc + * user/timer.t: Correct documentation for rtems_timer_initiate_server. + 2006-08-29 Joel Sherrill <joel@OARcorp.com> * cpu_supplement/cpu_supplement.texi: New file. diff --git a/doc/user/timer.t b/doc/user/timer.t index 421fc4f032..88c59d7306 100644 --- a/doc/user/timer.t +++ b/doc/user/timer.t @@ -60,7 +60,8 @@ sometimes referred to as a "keep alive" or a "deadman" timer. The Timer Server task is responsible for executing the timer service routines associated with all task-based timers. This task executes at a priority higher than any RTEMS application -task and thus can be viewed logically as the lowest priority interrupt. +task, and is created non-preemptible, and thus can be viewed logically as +the lowest priority interrupt. By providing a mechanism where timer service routines execute in task rather than interrupt space, the application is @@ -70,7 +71,9 @@ can be configured to have a floating point context in which case it would be save to perform floating point operations from a task-based timer. Most of the time, executing floating point instructions from an interrupt service routine -is not considered safe. +is not considered safe. However, since the Timer Server task +is non-preemptible, only directives allowed from an ISR can be +called in the timer service routine. The Timer Server is designed to remain blocked until a task-based timer fires. This reduces the execution overhead @@ -512,7 +515,8 @@ preempted. @findex rtems_timer_initiate_server @example rtems_status_code rtems_timer_initiate_server( - unsigned32 stack_size, + rtems_unsigned32 priority, + rtems_unsigned32 stack_size, rtems_attribute attribute_set ) ); |