[LITMUS^RT] recording start real-time task

[Thijs Raets]

Hi,

That was exactly what I was looking for thank you! Is it possible that this
sys_release event appears as type "resume" in my unit-trace output?

Kind regards,
Thijs


2014-04-17 0:15 GMT+02:00 Glenn Elliott <gelliott at cs.unc.edu>:

> Hi Thijs,
>
> Are you using synchronous releases?  (The ‘-w’ option for rtspin.)  With
> ‘-w’, rtspin will block until the user execute’s liblitmus’s ‘release_ts’
> (“release task set”).  Task set release records a timestamped ’sys_release’
> event in sched_trace.  You can then discard any releases/completions that
> occur before the sys_release timestamp.  I believe this will happen
> naturally if you tell unit-trace to discard the first job of every task
> with “-s 1”.
>
> The “experiment-scripts” package (
> https://github.com/LITMUS-RT/experiment-scripts) can also be used to
> analyze traces.  However, it also requires you to use its framework to set
> up experiments (this can take some time if you need to do something out of
> the ordinary).  The tool currently only gives you information on job
> deadline misses, tardiness, and the amount of time tasks send blocked.
>  However, it’s fairly easy to extend parse/sched.py to do other forms of
> analysis, such as job response time.
>
> -Glenn
>
>
> On Apr 16, 2014, at 12:14 PM, Thijs Raets <thijsraets at gmail.com> wrote:
>
> Hi,
>
> I'm using feather trace to monitor the rtspin task. I parsed the .bin file
> with unit-trace and thus extracted release and completion. The problem is
> that I also would like to record the time at which I give the order to
> execute the rtspin task. I need this time to calculate the theoretical
> deadlines of the different jobs since the release time of the first job
> could have been postponed. I however do not know how time is registered
> within feather trace. I would like to use the same reference to record the
> start time. Where do I look?
>
> Thanks in advance,
>
> Thijs
> _______________________________________________
> litmus-dev mailing list
> litmus-dev at lists.litmus-rt.org
> https://lists.litmus-rt.org/listinfo/litmus-dev
>
>
>
> _______________________________________________
> litmus-dev mailing list
> litmus-dev at lists.litmus-rt.org
> https://lists.litmus-rt.org/listinfo/litmus-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.litmus-rt.org/pipermail/litmus-dev/attachments/20140417/451a4674/attachment.html>