<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hi John,</div><div><br></div><div>what Felipe points out is correct: st_trace only traces real-time tasks. However, launching the script with rt_launch will not work because shell scripts fork of new processes, and real-time status is not inherited across a fork in LITMUS^RT.</div><div><br></div><div>If you are looking for a dummy workload to test your tracing setup, checkout rtspin in liblitmus. If you want to script task behavior for testing purposes, use Python, Perl, Lua, or some other scripting language that runs its interpreter as a single process (and launch the interpreter with rt_launch).</div><div><br></div><div>- Björn</div><div><br>On 13.11.2013, at 09:28, Felipe Cerqueira <<a href="mailto:felipeqcerqueira@gmail.com">felipeqcerqueira@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div><div><div>Hi John,<br><br></div>st_trace only traces task events such as releases, deadlines and context-switches of real-time jobs.<br></div></div>For it to work with the bash script, you need to launch your program with rt_launch, found in liblitmus folder.<br>
<div>Otherwise the process will be considered a best-effort task and will not show up in the scheduling trace.<br><br></div><div>Thanks,<br>Felipe<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
2013/11/13 Litmus ForLinux <span dir="ltr"><<a href="mailto:litmustiger@gmail.com" target="_blank">litmustiger@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>I am a novice in Linux Kernel coding and I have found LITMUS to be interesting. I compiled and installed LITMUS-RT in my Linux (Ubuntu 12.04) as per the instructions given in the LITMUS website. Also I compiled feather trace tool in my LITMUS system.(including LIBLITMUS dependencies).</div>
<div><br></div><div>How to use feather tool and trace the process (by its release and execution time) using the litmus logs. I execute a background process and tried to trace the process using feather tool. Following are the steps : </div>
<div><br></div><div>1. I wrote following shell script (task.sh)-</div><div> ls </div><div> sleep 20</div><div> ls</div><div> sleep 20</div><div><br></div><div>Then I executed the script in the background - sh task.sh &</div>
<div>2. Once the process starts to run in the background, I executed st_trace immediately.</div><div>3. Trace tool starts executing and it gives a message - <br>"Press Enter to end tracing" </div><div>I pressed enter after some time and got following - </div>
<div>"Disabling 10 events .... /dev/litmus_sched_trace1: 0 bytes read."</div><div><br></div><div>Because of this, are no contents inside the log file. If I try to execute some other task as mentioned in the feather trace tool documentation, "./st_trace global-exp" I encounter same "0 bytes read" message. </div>
<div><br></div><div>Please help me to resolve this issue. I want to have to log file generated.</div><div><br></div><div>Thanks</div><div>John</div><div><br></div></div>
<br>_______________________________________________<br>
litmus-dev mailing list<br>
<a href="mailto:litmus-dev@lists.litmus-rt.org">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><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>litmus-dev mailing list</span><br><span><a href="mailto:litmus-dev@lists.litmus-rt.org">litmus-dev@lists.litmus-rt.org</a></span><br><span><a href="https://lists.litmus-rt.org/listinfo/litmus-dev">https://lists.litmus-rt.org/listinfo/litmus-dev</a></span><br></div></blockquote></body></html>