[LITMUS^RT] Trace unit ?

[Sanjib Das]

Dear All,
I do like to know the measurement time units of the following  IDs

   -

   SCHED_START, SCHED_END: Used to measure the time spent to make a
   scheduling decision.
   -

   CXS_START, CXS_END: Used to record the time spent to make a context
   switch.
   -

   SCHED2_START, SCHED2_END: Used to measure the time spent to perform
   post-context-switch cleanup and management activities. This is part of the
   scheduling overhead but for technical reasons cannot be measured as part of
   the interval [SCHED_START, SCHED_END].
   -

   TICK_START, TICK_END: Used to measure the overhead incurred due to
   Linux's periodic system tick. As of LITMUSRT 2014.2, no LITMUSRT-specific
   activity takes place during a system tick.
   -

   QUANTUM_BOUDARY_START, QUANTUM_BOUNDARY_END`: Used to measure the
   overhead incurred in quantum-driven plugins (e.g., PFAIR) at the start of
   each quantum. Available since LITMUSRT 2014.2.
   -

   PLUGIN_SCHED_START, PLUGIN_SCHED_END: Like [SCHED_START, SCHED_END], but
   only measures the time spent by the active scheduling plugin. There is no
   equivalent SCHED2 counterpart because the scheduling plugins do not
   directly contribute to the SCHED2 overhead.
   -

   RELEASE_START, RELEASE_END: Used to measure the time spent to enqueue a
   newly-released job in a ready queue.
   -

   RELEASE_LATENCY: Used to measure the difference between when a timer
   *should* have fired, and when it actually *did* fire. In contrast to all
   other time stamps, *this overhead is directly measured in nanoseconds*
   (and not in processor cycles as the other overheads).


Except RELEASE_LATENCY, are all the others measured in milliseconds ?

Or how can I determine that .


Thanks in advance

Sanjib
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.litmus-rt.org/pipermail/litmus-dev/attachments/20140619/4479b7de/attachment.html>