From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] Some questions about Lttng
Date: Tue, 26 Jun 2012 02:06:09 -0400 [thread overview]
Message-ID: <20120626060609.GD11445@Krystal> (raw)
In-Reply-To: <4FE8141D.3030107@emc.com>
* changz (zheng.chang at emc.com) wrote:
[...]
> Mathieu, thank you so much.
> May I know if following two features have been in your schedule list? If
> yes, what's the target release?
> a. trace_printf API
In schedule list, by the end of 2012.
> b. dynamic tracing for lttng-ust
No ETA at the moment for this feature. It's a "wishlist" feature, but
it is not planned for any specific point in time.
Thanks,
Mathieu
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2012-06-26 6:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 3:50 Zheng.Chang
2012-06-19 9:28 ` Francis Giraldeau
2012-06-19 16:36 ` Mathieu Desnoyers
2012-06-20 5:30 ` Zheng.Chang
2012-06-20 13:03 ` Mathieu Desnoyers
2012-06-21 4:59 ` Zheng.Chang
2012-06-21 12:45 ` Mathieu Desnoyers
2012-06-25 7:32 ` changz
2012-06-26 6:06 ` Mathieu Desnoyers [this message]
2012-06-26 8:59 ` changz
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=20120626060609.GD11445@Krystal \
--to=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