* [ltt-dev] [UST] Instrumentation API changes done
@ 2011-04-22 18:33 Mathieu Desnoyers
2011-04-27 14:24 ` Nils Carlson
0 siblings, 1 reply; 2+ messages in thread
From: Mathieu Desnoyers @ 2011-04-22 18:33 UTC (permalink / raw)
Hi,
I would appreciate if you could have a look at the API change
implementation I pushed into UST. For now, it should cover the most
critical parts. In its current state, I think the ust_marker() API is
pretty much final, so people can start using it for debug-only in their
application and expect it not to change. For the Tracepoints, the
DECLARE/DEFINE_TRACEPOINT will eventually become internal to
TRACEPOINT_EVENT(). We can expect further changes to the
TRACEPOINT_EVENT() API, as we will very likely need to change the other
macros that come with it.
While we are there, I am tempted to kill TRACEPOINT_EVENT_FN(), because
it was only needed for specific syscall tracing, and I don't really
expect to let the instrumentation to be controlled so closely by the
application code in user-space. Thoughts ?
Also, I'd really like to push a UST 0.13 out the door with the new
instrumentation ASAP. At least people will be able to start using
ust_mark() without fear that the carpet will be removed from under their
feet. ;-)
Thanks,
Mathieu
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
^ permalink raw reply [flat|nested] 2+ messages in thread
* [ltt-dev] [UST] Instrumentation API changes done
2011-04-22 18:33 [ltt-dev] [UST] Instrumentation API changes done Mathieu Desnoyers
@ 2011-04-27 14:24 ` Nils Carlson
0 siblings, 0 replies; 2+ messages in thread
From: Nils Carlson @ 2011-04-27 14:24 UTC (permalink / raw)
Hi,
On Fri, 22 Apr 2011, Mathieu Desnoyers wrote:
> Hi,
>
> I would appreciate if you could have a look at the API change
> implementation I pushed into UST. For now, it should cover the most
> critical parts. In its current state, I think the ust_marker() API is
> pretty much final, so people can start using it for debug-only in their
> application and expect it not to change. For the Tracepoints, the
> DECLARE/DEFINE_TRACEPOINT will eventually become internal to
> TRACEPOINT_EVENT(). We can expect further changes to the
> TRACEPOINT_EVENT() API, as we will very likely need to change the other
> macros that come with it.
>
The changes look good to me. No real comments. I'll have a look at the
documentation when I can.
> While we are there, I am tempted to kill TRACEPOINT_EVENT_FN(), because
> it was only needed for specific syscall tracing, and I don't really
> expect to let the instrumentation to be controlled so closely by the
> application code in user-space. Thoughts ?
Nope. No thoughts, just emptiness here... ;-)
> Also, I'd really like to push a UST 0.13 out the door with the new
> instrumentation ASAP. At least people will be able to start using
> ust_mark() without fear that the carpet will be removed from under their
> feet. ;-)
I think it will have to wait a few days at least, but then we should be
ready.
/Nils
> Thanks,
>
> Mathieu
>
> --
> Mathieu Desnoyers
> Operating System Efficiency R&D Consultant
> EfficiOS Inc.
> http://www.efficios.com
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-04-27 14:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-04-22 18:33 [ltt-dev] [UST] Instrumentation API changes done Mathieu Desnoyers
2011-04-27 14:24 ` Nils Carlson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox