<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;"><br><div><div>On Dec 15, 2013, at 9:13 AM, Luo, Zheng <<a href="mailto:luozheng@wustl.edu">luozheng@wustl.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr" fpstyle="1" aria-label="Message body" tabindex="0" id="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div name="divtagdefaultwrapper" id="divtagdefaultwrapper" style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; margin: 0px;"><div>Hi every,</div><div><br></div><div>I try to use the st_trace, however the program can not start correctly. I think when I compile the kernel, I already enable the trace flag (I attached the image). However it still can not find the sched_trace 0-7.</div><div><br></div><div>I send the screen shots and the .config too. Can anyone tell me that where I did wrong?</div><div><br></div><p style="margin-top: 0px; margin-bottom: 0px;"></p><div><br></div><span><Screenshot 2013-12-15 08:04:15.png></span><p style="margin-top: 0px; margin-bottom: 0px;"></p><div style="margin-top: 0px; margin-bottom: 0px;"><br></div><p style="margin-top: 0px; margin-bottom: 0px;"></p><span><Screenshot 2013-12-15 08:03:17.png></span><p style="margin-top: 0px; margin-bottom: 0px;"></p><div style="margin-top: 0px; margin-bottom: 0px;"><br></div><div style="margin-top: 0px; margin-bottom: 0px;"><br></div><div><div style="margin-top: 0px; margin-bottom: 0px;"><br></div><div name="divtagdefaultwrapper" style="font-family: Calibri, Arial, Helvetica, sans-serif; margin: 0px;">Zheng Luo<br></div></div></div><span><config></span>_______________________________________________<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">https://lists.litmus-rt.org/listinfo/litmus-dev</a></div></blockquote></div><div><br></div><br><div>Hi Zheng,</div><div><br></div><div>Take a look at litmus-rt/litmus/Kconfig. In the file you can see the configurable compile-time options in Litmus and their dependencies. You need to select CONFIG_SCHED_TASK_TRACE to enable the tracing features you want. As you can see in the Kconfig, CONFIG_SCHED_TASK_TRACE depends upon CONFIG_FEATHER_TRACE. Looking at your screenshot, I see that (1) CONFIG_FEATHER_TRACE is not set and (2) you don’t even have the option to select CONFIG_FEATHER_TRACE. This is because CONFIG_FEATHER_TRACE has the dependency “!CONFIG_RELOCATABLE” (again, look at the FEATHER_TRACE entry in the Kconfig). So:</div><div><br></div><div>1) Disable a relocatable kernel. I can’t recall where it is exactly, but it is probably somewhere in the general settings. In the menuconfig, you can hit “/“ and search (just like how search works in vim) for the string RELOCATABLE.</div><div>2) Enable feather trace.</div><div>3) Enable sched task trace</div><div><br></div><div>Note that “TRACE() debugging” generates text-based logs that can be read from /dev/litmus/log. It is purely for debugging. If you need to take performance measurements of Litmus, it is best to disable TRACE() debugging.</div><div><br></div><div>-Glenn</div></body></html>