From: Adel Belkhiri via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: [lttng-dev] Hooking up callbacks to LTTng USDT Events
Date: Tue, 6 Feb 2024 14:32:58 -0500 [thread overview]
Message-ID: <CAMxxxdO7w__AjLhnuoxjv5TghuEoLNbBS_7N-UiUdv8YykwAPw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 373 bytes --]
Hi everyone,
Hope you're all good. I'm working on something where I need to set up
routines or callbacks for specific LTTng USDT events (sticking to user
space, not kernel). The plan is to catch these events as they happen to
spot performance issues.
If anyone's done something like this or has pointers on how to pull it off,
I'd really appreciate your advice.
Thanks!
[-- Attachment #1.2: Type: text/html, Size: 2037 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next reply other threads:[~2024-02-06 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 19:32 Adel Belkhiri via lttng-dev [this message]
2024-02-07 14:50 ` Kienan Stewart 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=CAMxxxdO7w__AjLhnuoxjv5TghuEoLNbBS_7N-UiUdv8YykwAPw@mail.gmail.com \
--to=lttng-dev@lists.lttng.org \
--cc=adel.belkhiri@gmail.com \
/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