Files
rtems/testsuites/tmtests
Sebastian Huber 62c528e633 rtems: _Semaphore_Get_interrupt_disable()
Use _Objects_Get_local() for _Semaphore_Get_interrupt_disable() to get
rid of the location parameter.  Move remote object handling to semaphore
MPCI support.
2016-05-20 16:17:00 +02:00
..
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2015-12-24 16:52:34 -06:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2014-04-07 16:48:01 +02:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2014-03-25 08:06:37 +01:00
2015-03-05 11:23:10 +01:00
2016-03-02 08:51:55 +01:00
2016-03-02 08:51:55 +01:00

This directory contains the RTEMS Classic API Timing Test Suite.
The tests in this directory are used to measure the execution
time of RTEMS directive and some critical internal functions.
The results of these test are useful for comparison of RTEMS
performance 

+ between versions of RTEMS
+ between different boards 
+ across different architectures

These tests attempt to benchmark RTEMS as the user would.  They measure
the execution time for a directive (under various circumstances)
from the time RTEMS is entered until it is executed.  Where possible,
the time is the average of at least 100 invocations of the directive.

The accuracy of the times reported by these benchmarks is very dependent
on the resolution of the timer being used.  It is also important to
insure that all sources of hardware interrupts are disabled during
execution of the tests.  This insures that the directive time reported
does not include any interrupt time.