Add documentation for profiling

This commit is contained in:
Sebastian Huber
2014-03-12 09:23:34 +01:00
parent 4575ae0a40
commit 0bf59cf0ae
2 changed files with 23 additions and 0 deletions

View File

@@ -283,6 +283,17 @@ Interrupt Controller model which does not require the BSP to implement
@code{set_vector}. BSPs for these architectures must provide a different
set of support routines.
@section Interrupt Delay Profiling
The RTEMS profiling needs support by the BSP for the interrupt delay times. In
case profiling is enabled via the RTEMS build configuration option
@code{--enable-profiling} (in this case the pre-processor symbol
@code{RTEMS_PROFILING} is defined) a BSP may provide data for the interrupt
delay times. The BSP can feed interrupt delay times with the
@code{_Profiling_Update_max_interrupt_delay()} function
(@code{#include <rtems/score/profiling.h>}). For an example please have a look
at @code{c/src/lib/libbsp/sparc/leon3/clock/ckinit.c}.
@section Programmable Interrupt Controller API
A BSP can use the PIC API to install Interrupt Service Routines through

View File

@@ -362,6 +362,18 @@ provide the following two functions
counter values.
@end itemize
@section Interrupt Profiling
The RTEMS profiling needs support by the CPU port for the interrupt entry and
exit times. In case profiling is enabled via the RTEMS build configuration
option @code{--enable-profiling} (in this case the pre-processor symbol
@code{RTEMS_PROFILING} is defined) the CPU port may provide data for the
interrupt entry and exit times of the outer-most interrupt. The CPU port can
feed interrupt entry and exit times with the
@code{_Profiling_Outer_most_interrupt_entry_and_exit()} function
(@code{#include <rtems/score/profiling.h>}). For an example please have a look
at @code{cpukit/score/cpu/arm/arm_exc_interrupt.S}.
@c
@c
@c