<div dir="ltr">Hi,<div><br></div><div>The sys_release wasn't recognized by unit trace, I had to add the sys_release type a second time in the array of the unit-trace script since the type number was 11. I can record the task set release now but I have a new problem now. This is my output: </div>
<div><br></div><div><br></div><div>.</div><div>.</div><div>.</div><div><br></div><div><div>Event ID: 7</div><div>Job: 0.0</div><div>Type: sys_release2</div><div>Time: 672784686695748</div><div><br></div><div>Event ID: 8</div>
<div>Job: 6904.1</div><div>Type: resume</div><div>Time: 672784686702656</div><div><br></div><div>Event ID: 9</div><div>Job: 6904.2</div><div>Type: release</div><div>Time: 672784686705186</div><div><br></div><div>Event ID: 10</div>
<div>Job: 6904.2</div><div>Type: switch_to</div><div>Time: 672784686727392</div><div><br></div><div>Event ID: 11</div><div>Job: 6904.3</div><div>Type: switch_away</div><div>Time: 672784686731107</div><div><br></div><div>Event ID: 12</div>
<div>Job: 6904.3</div><div>Type: completion</div><div>Time: 672784686736223</div><div><br></div><div>Event ID: 13</div><div>Job: 6904.4</div><div>Type: release</div><div>Time: 672785686000000</div></div><div><br></div><div>
Rtspin has a period of 100ms. The resume of job 1 is ignored I only look at release and completion. Job 2 is released but had no completion(no worries I want soft real-time results). Job 3 only has completion time. The real problem for me is the time difference between the release of job 4 and job 2. It's nowhere near 200ms the other jobs are released just fine, but they are all shifted because of job 4 releasing late.(This problem only occurs when using synchronous release)</div>
<div><br></div><div>Any ideas?</div><div><br></div><div>Thanks,</div><div>Thijs</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-04-17 12:48 GMT+02:00 Thijs Raets <span dir="ltr"><<a href="mailto:thijsraets@gmail.com" target="_blank">thijsraets@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>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?</div>
<div><br></div><div>Kind regards,</div>
<div>Thijs</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-04-17 0:15 GMT+02:00 Glenn Elliott <span dir="ltr"><<a href="mailto:gelliott@cs.unc.edu" target="_blank">gelliott@cs.unc.edu</a>></span>:<div>
<div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi Thijs,<div><br></div><div>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”.</div>
<div><br></div><div>The “experiment-scripts” package (<a href="https://github.com/LITMUS-RT/experiment-scripts" target="_blank">https://github.com/LITMUS-RT/experiment-scripts</a>) 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.</div>
<div><br></div><div>-Glenn</div><div><br></div><div><br><div><div><div><div>On Apr 16, 2014, at 12:14 PM, Thijs Raets <<a href="mailto:thijsraets@gmail.com" target="_blank">thijsraets@gmail.com</a>> wrote:</div>
<br></div></div><blockquote type="cite"><div><div><div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">Hi, </span><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">
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?</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">Thanks in advance,</div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">
Thijs</div></div></div></div>
_______________________________________________<br>litmus-dev mailing list<br><a href="mailto:litmus-dev@lists.litmus-rt.org" target="_blank">litmus-dev@lists.litmus-rt.org</a><br><a href="https://lists.litmus-rt.org/listinfo/litmus-dev" target="_blank">https://lists.litmus-rt.org/listinfo/litmus-dev</a><br>
</blockquote></div><br></div></div><br>_______________________________________________<br>
litmus-dev mailing list<br>
<a href="mailto:litmus-dev@lists.litmus-rt.org" target="_blank">litmus-dev@lists.litmus-rt.org</a><br>
<a href="https://lists.litmus-rt.org/listinfo/litmus-dev" target="_blank">https://lists.litmus-rt.org/listinfo/litmus-dev</a><br>
<br></blockquote></div></div></div><br></div>
</blockquote></div><br></div>