From: chafraysse--- via lttng-dev <lttng-dev@lists.lttng.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] LTTng UST structure support
Date: Mon, 16 Jan 2023 10:38:28 +0100 (CET) [thread overview]
Message-ID: <1512260626.80256142.1673861908243.JavaMail.root@zimbra43-e7.priv.proxad.net> (raw)
In-Reply-To: <79319a2d-0898-0243-1572-26e476cac681@efficios.com>
Hi Mathieu,
Thanks for your reply :)
I'll stick to bt2 modules in the meantime then
I'll already be saving a ton of time with those and the CTF spec which is great !
Best regards,
Charles
----- Mail original -----
De: "Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>
À: chafraysse@free.fr, lttng-dev@lists.lttng.org
Envoyé: Jeudi 12 Janvier 2023 21:10:57
Objet: Re: [lttng-dev] LTTng UST structure support
On 2023-01-09 09:02, chafraysse--- via lttng-dev wrote:
> Hi,
>
> I'm looking for a CTF writer to serialize instrumentations in an
> embedded Linux/Rust framework
> LTTng UST looked like a very strong option, but I want to serialize
> structures as CTF compound type structures and I did not see those
> supported in the doc or api
This is correct. I am currently working on a new project called
"libside" (see https://git.efficios.com/?p=libside.git;a=summary) which
features support for compound types.
However, we still need to do the heavy-lifting implementation work of
integrating this with LTTng-UST. This is the plan towards supporting
compound types in LTTng-UST.
> I'd love to have confirmation that I did not just miss something :)
> If LTTng UST is out for me I will probably try to use the ctf-writer
> module of babeltrace 2 instead
For now the ctf-writer modules of bt2 would be an alternative to
consider, but remember that it is not designed for low-impact tracing
such as lttng-ust. So it depends on how much tracer overhead/runtime
impact you can afford in your use-case.
Thanks,
Mathieu
>
> Best regards,
>
> Charles
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
Mathieu Desnoyers
EfficiOS Inc.
https://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:[~2023-01-16 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 14:02 chafraysse--- via lttng-dev
2023-01-12 20:10 ` Mathieu Desnoyers via lttng-dev
2023-01-16 9:38 ` chafraysse--- via lttng-dev [this message]
2023-02-02 16:06 ` chafraysse--- via lttng-dev
2023-02-02 23:18 ` Jérémie Galarneau via lttng-dev
2023-02-09 9:15 ` chafraysse--- via lttng-dev
2023-02-09 21:54 ` Jérémie Galarneau via lttng-dev
2023-02-10 18:12 ` chafraysse--- 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=1512260626.80256142.1673861908243.JavaMail.root@zimbra43-e7.priv.proxad.net \
--to=lttng-dev@lists.lttng.org \
--cc=chafraysse@free.fr \
--cc=mathieu.desnoyers@efficios.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