From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org> To: ahmadkhorrami <ahmadkhorrami@ut.ac.ir> Cc: linux-trace-users <linux-trace-users@vger.kernel.org>, lttng-dev <lttng-dev@lists.lttng.org>, rostedt <rostedt@goodmis.org>, Namhyung Kim <namhyung@kernel.org> Subject: Re: [lttng-dev] Capturing User-Level Function Calls/Returns Date: Wed, 15 Jul 2020 14:45:18 -0400 (EDT) [thread overview] Message-ID: <83963025.14828.1594838718290.JavaMail.zimbra@efficios.com> (raw) Message-ID: <20200715184518.qa_q_rasB2taHCNvQ2bGRAlLaAJn5aZ78i-u5IAQUb4@z> (raw) In-Reply-To: <20200715142849.0bfe909a@oasis.local.home> ----- On Jul 15, 2020, at 2:28 PM, rostedt rostedt@goodmis.org wrote: > On Wed, 15 Jul 2020 20:37:16 +0430 > ahmadkhorrami <ahmadkhorrami@ut.ac.ir> wrote: > >> Hi, >> What is the most efficient way to capture occurrence of a function >> call/return of a binary program in userspace? >> It seems the answer is Uprobes. 1) Am I right? >> But Uprobes use "int" instruction which leads to a switch into kernel >> mode. 2) Wouldn't it be better to avoid this transition? >> I'm looking forward to your reply and will be happy to read your >> opinions. >> Regards. > > > Hi, I believe LTTng has utilities that can help you trace user space > programs. Indeed, it is documented here: https://lttng.org/docs/#doc-liblttng-ust-cyg-profile If your program is generating function entry/exit at a very high rate (which goes beyond your available I/O throughput and lasts longer than the memory you have available for ring buffers), you will also probably want to use the "blocking-timeout" option documented at: https://lttng.org/docs/#doc-enabling-disabling-channels Thanks, Mathieu > > I think there's also a users ftrace like utility that Namhyung was > working on. But I don't know where in the development that is. > > -- Steve -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com _______________________________________________ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2020-07-15 18:45 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <e9c7400ff0075f3beba2863c4432a905@ut.ac.ir> 2020-07-15 18:28 ` Steven Rostedt 2020-07-15 18:28 ` [lttng-dev] " Steven Rostedt via lttng-dev 2020-07-15 18:45 ` Mathieu Desnoyers [this message] 2020-07-15 18:45 ` Mathieu Desnoyers via lttng-dev 2020-07-15 21:39 ` ahmadkhorrami 2020-07-15 21:39 ` [lttng-dev] " ahmadkhorrami via lttng-dev 2020-07-15 21:48 ` Steven Rostedt 2020-07-15 21:48 ` [lttng-dev] " Steven Rostedt via lttng-dev 2020-07-15 22:25 ` ahmadkhorrami 2020-07-15 22:25 ` [lttng-dev] " ahmadkhorrami via lttng-dev 2020-07-16 1:06 ` Michel Dagenais via lttng-dev 2020-07-16 1:06 ` [lttng-dev] " Michel Dagenais via lttng-dev 2020-07-16 1:49 ` Frank Ch. Eigler 2020-07-16 1:49 ` Frank Ch. Eigler via lttng-dev 2020-07-16 16:26 ` ahmadkhorrami 2020-07-16 16:26 ` ahmadkhorrami via lttng-dev 2020-07-16 16:20 ` ahmadkhorrami 2020-07-16 16:20 ` ahmadkhorrami via lttng-dev 2020-07-16 16:34 ` ahmadkhorrami 2020-07-16 16:34 ` ahmadkhorrami via lttng-dev 2020-07-16 1:04 ` Namhyung Kim 2020-07-16 1:04 ` [lttng-dev] " Namhyung Kim via lttng-dev 2020-07-16 16:07 ` ahmadkhorrami 2020-07-16 16:07 ` [lttng-dev] " ahmadkhorrami via lttng-dev
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=83963025.14828.1594838718290.JavaMail.zimbra@efficios.com \ --to=lttng-dev@lists.lttng.org \ --cc=ahmadkhorrami@ut.ac.ir \ --cc=linux-trace-users@vger.kernel.org \ --cc=mathieu.desnoyers@efficios.com \ --cc=namhyung@kernel.org \ --cc=rostedt@goodmis.org \ --subject='Re: [lttng-dev] Capturing User-Level Function Calls/Returns' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).