From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: Norbert Lange <nolange79@gmail.com>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] [PATCH v2] Improve tracef/tracelog to use the stack for small strings
Date: Mon, 1 Aug 2022 11:24:27 -0400 (EDT) [thread overview]
Message-ID: <1848659433.93617.1659367467800.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <CADYdroPCRa92zKoAQfB+DW4vte-srd4+w+=vbLZN_eqwdSXZMw@mail.gmail.com>
----- On Aug 1, 2022, at 10:44 AM, Norbert Lange via lttng-dev lttng-dev@lists.lttng.org wrote:
[...]
>
> Any chance of not having to link liblttng-ust for the tracelog/tracef functions,
> like all other tracepoints (only hard dependency on liblttng-ust-tracepoint)?
> My involvement is limited to "complain-only" for that one, but think of
> how technically great that would be!
Here is how we could do this:
1) move the implementation of src/lib/lttng-ust/tracelog.c to its own .so, e.g.
liblttng-ust-tracelog.so,
2) modify the tracelog/tracef public headers so they dlopen() this new .so from
a library constructor, similarly to what tracepoint.h does.
We'd need to make sure the symbols from tracelog.c are still emitted in
liblttng-ust.so, _and_ have another version (with a prefix/suffix) emitted from
liblttng-ust-tracelog.so, so we don't break ABI.
Thoughts ?
Thanks,
Mathieu
--
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:[~2022-08-01 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 14:35 [lttng-dev] [PATCH v2] Improve tracef/tracelog to use the stack for small strings Norbert Lange via lttng-dev
2022-08-01 14:44 ` Norbert Lange via lttng-dev
2022-08-01 15:24 ` Mathieu Desnoyers via lttng-dev [this message]
2022-08-01 15:12 ` Mathieu Desnoyers 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=1848659433.93617.1659367467800.JavaMail.zimbra@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=nolange79@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;
as well as URLs for NNTP newsgroup(s).