<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">I’m afraid not. This is one reason why it’s not found in the LITMUS^RT github repositories, but rather in B. Brandenburg’s.<div><br></div><div>Here are a few tips:<div><br></div><div>1) The repo compiles with ‘scons’ instead of 'make’.</div><div>2) st_show can be used to view the sched trace data. The code for this program in src/showst.c. Read this code to figure out the command line arguments.</div><div>3) Use showst.c as a model for your own custom analysis code. Most important: the core loop (showst.c:68) to showst.c extracts logged events in temporal order.</div><div><div>4) include/sched_trace.h has data structures that mirror the data structures from litmus-rt/include/litmus/sched_trace.h. First, double check that the data structures match your kernel’s. Second, look at the fields and events to understand what data is logged by each event type.</div><div><br></div><div>Suppose you want to write code that finds the response time (release time minus completion time) for every job. Each job can be uniquely identified by a pid/job number pair. These fields are found in the st_trace_header struct, which is a part of every sched_trace event. st_release_data has the job release time. st_completion_data has the completion time. Use the st_trace_header in each release/completion to match release events with completion events.</div><div><br></div><div>If you find a field that you don’t understand, go back to your kernel’s source code and find where the event is actually logged. Hopefully you’ll be able to figure it out by digging into the code. If you really get stumped, post a question here. Finally, it’s pretty easy to add your own trace events to sched_trace, but you’ll have to dig into kernel code.</div><div><br></div><div>-Glenn</div><div><br></div><div><br><div><div>On Nov 20, 2013, at 3:35 PM, ayoade gbadebo <<a href="mailto:gbaduz@gmail.com">gbaduz@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class=""><img class="" id=":n0" src="https://mail.google.com/mail/u/0/images/cleardot.gif" alt=""></div><div><span style="font-family:arial,sans-serif;font-size:13px">Hi,</span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Is there a readme file on how to use this tool?</span></div>
<span style="font-family:arial,sans-serif;font-size:13px"> </span><a href="https://github.com/brandenburg/sched-trace-tools" style="font-family:arial,sans-serif;font-size:13px" target="_blank">https://github.com/brandenburg/sched-trace-tools</a><div class="">
<div id=":mc" class="" tabindex="0"><img class="" src="https://mail.google.com/mail/u/0/images/cleardot.gif"></div></div></div>
_______________________________________________<br>litmus-dev mailing list<br><a href="mailto:litmus-dev@lists.litmus-rt.org">litmus-dev@lists.litmus-rt.org</a><br>https://lists.litmus-rt.org/listinfo/litmus-dev<br></blockquote></div><br></div></div></div></body></html>