From: ahmadkhorrami <ahmadkhorrami@ut.ac.ir>
To: Linux-trace Users <linux-trace-users@vger.kernel.org>
Subject: Capturing User-Level Function Calls/Returns
Date: Wed, 15 Jul 2020 20:37:16 +0430 [thread overview]
Message-ID: <e9c7400ff0075f3beba2863c4432a905@ut.ac.ir> (raw)
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.
next reply other threads:[~2020-07-15 16:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 16:07 ahmadkhorrami [this message]
2020-07-15 18:28 ` Capturing User-Level Function Calls/Returns Steven Rostedt
2020-07-15 18:45 ` Mathieu Desnoyers
2020-07-15 21:39 ` ahmadkhorrami
2020-07-15 21:48 ` Steven Rostedt
2020-07-15 22:25 ` ahmadkhorrami
2020-07-16 1:06 ` [lttng-dev] " Michel Dagenais
2020-07-16 1:49 ` Frank Ch. Eigler
2020-07-16 16:26 ` ahmadkhorrami
2020-07-16 16:20 ` ahmadkhorrami
2020-07-16 16:34 ` ahmadkhorrami
2020-07-16 1:04 ` Namhyung Kim
2020-07-16 16:07 ` ahmadkhorrami
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=e9c7400ff0075f3beba2863c4432a905@ut.ac.ir \
--to=ahmadkhorrami@ut.ac.ir \
--cc=linux-trace-users@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).