<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div><br></div><div><br></div><span id="zwchr" data-marker="__DIVIDER__">----- On Feb 26, 2016, at 1:01 PM, Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:<br></span><div data-marker="__QUOTED_TEXT__"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div>Hi Martin,<br></div><br><div>I would say that the main advantages of using LTTng in this case</div><div>would be on the tooling side, with availability of Trace Compass</div><div>and LTTng Analyses projects to navigate in the resulting CTF</div><div>traces, and get high-level overview of the various metrics that</div><div>could slow down your system.<br></div><br><div>LTTng would also allow you to correlate your kernel trace with<br></div><div>a user-space trace gathered with lttng-ust, which gives you<br></div><div>deeper insight into your applications.</div></div></blockquote><div><br></div><div>One more benefit of using lttng as builtin tracer rather than<br data-mce-bogus="1"></div><div>ftrace is that LTTng gathers much more information about the<br data-mce-bogus="1"></div><div>system call input/output parameters than ftrace. This can be<br data-mce-bogus="1"></div><div>useful to get a better understanding of what userspace is<br data-mce-bogus="1"></div><div>doing with the kernel.<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>Thanks,<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>Mathieu<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div><br></div><br><div>Thanks,<br></div><br><div>Mathieu<br></div><br><span id="zwchr">----- On Feb 26, 2016, at 3:41 AM, Martin Townsend <mtownsend1973@gmail.com> wrote:<br></span><div><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div dir="ltr">Hi Mathieu,<br><div>Thanks for the info, I didn't know about ftrace, I will take a look at this. </div><br><div>Out of interest would there be any benefits from using a built-in lttng module over ftrace?</div><br><div>Cheers,<br>Martin.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 25, 2016 at 9:18 PM, Mathieu Desnoyers <span dir="ltr"><<a href="mailto:mathieu.desnoyers@efficios.com" target="_blank">mathieu.desnoyers@efficios.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:arial,helvetica,sans-serif;font-size:12pt;color:#000000"><div>Hi Martin,<br></div><br><div>The main limitation LTTng currently has for early boot tracing is that<br></div><div>you need to first spawn a lttng-sessiond user-space process, and setup<br></div><div>tracing, before you can actually do any tracing. As long as you can<br></div><div>fit within those constraints, you should be OK.<br></div><br><div>If you really want to trace earlier than that, you might have to create<br></div><div>a dedicated early-boot tracing module that would setup tracing<br></div><div>buffers into a "dummy" session which exists only within lttng-modules,</div><div>and then allow sessiond to later hook on those buffers when user-space</div><div>is ready. Nothing exists for this at the moment. Note that since</div><div>lttng-modules master (upcoming 2.8), you can now build lttng-modules</div><div>into your kernel image, this might be useful for you. See the "kernel</div><div>built-in support" section in</div><div><a href="https://github.com/lttng/lttng-modules/blob/master/README.md" target="_blank">https://github.com/lttng/lttng-modules/blob/master/README.md</a><br></div><br><div>Since LTTng 2.0, we have left early boot tracing to other tools, such</div><div>as Ftrace, which target kernel developers use-cases, and focused</div><div>more on tracing of the system in its execution phases which are more</div><div>relevant to application developers.<br></div><br><div>If you want to go ahead and create a LTTng modules module that<br></div><div>allow early boot tracing, I'd be happy to provide ideas and review.<br></div><br><div>Thanks,<br></div><br><div>Mathieu<br></div><div><div class="h5"><br><span>----- On Feb 25, 2016, at 3:56 PM, Martin Townsend <<a href="mailto:mtownsend1973@gmail.com" target="_blank">mtownsend1973@gmail.com</a>> wrote:<br></span></div></div><div><blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><div><div class="h5"><div dir="ltr"><div><div>Hi,<br><br></div>This is a bit of a long shot but does LTTng allow you trace boot?<br><br>I'm seeing a weird problem where if I boot with systemd-bootchart if boots faster than just using systemd as the init process. I created my own init process based on systemd-bootchart and worked out it was down to the fact it called nanosleep, so I now have my own init process which hands over to systemd and creates a child that nanosleeps for the boot duration. I would really like to trace/profile the scheduler and hrtimers understand what's happening and try and get a proper fix :) Even if it means a bit of hacking kernel/LTTng, I would be willing to do this.<br><br></div>Many Thanks, Martin.<br></div><br></div></div>_______________________________________________<br>lttng-dev mailing list<br><a href="mailto:lttng-dev@lists.lttng.org" target="_blank">lttng-dev@lists.lttng.org</a><br><a href="http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev" target="_blank">http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev</a><span class="HOEnZb"><span style="color: #888888;"><br></span></span></blockquote></div><span class="HOEnZb"><span style="color: #888888;"><br><div>-- <br></div><div>Mathieu Desnoyers<br>EfficiOS Inc.<br><a href="http://www.efficios.com" target="_blank">http://www.efficios.com</a><br></div></span></span></div></div></blockquote></div></div><br></blockquote></div><br><div>-- <br></div><div>Mathieu Desnoyers<br>EfficiOS Inc.<br>http://www.efficios.com</div></div><br>_______________________________________________<br>lttng-dev mailing list<br>lttng-dev@lists.lttng.org<br>http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev<br></blockquote></div><br><div data-marker="__SIG_POST__">-- <br></div><div>Mathieu Desnoyers<br>EfficiOS Inc.<br>http://www.efficios.com</div></div></body></html>