From: nils.carlson@ludd.ltu.se (Nils Carlson)
Subject: [ltt-dev] [RFC] UST instrumentation API
Date: Wed, 20 Apr 2011 20:03:30 +0200 [thread overview]
Message-ID: <00251A6D-FE11-49D1-B078-E854C9724D83@ludd.ltu.se> (raw)
Message-ID: <20110420180330.BAfVkKzr28nympUUifn-XxhjB_qEV78jQgQJiYwR8cs@z> (raw)
In-Reply-To: <20110419215635.GA15969@Krystal>
On Apr 19, 2011, at 11:56 PM, Mathieu Desnoyers wrote:
>
> How about:
>
> "TRACEPOINT_EVENT()" and "#define TRACEPOINT_CREATE" ?
>
> Ideally, I'd like to settle this API and release a UST 0.13 this week,
> so people who want to start instrumenting their code can use the new
> Markers API while we move to the TRACEPOINT_EVENT infrastructure.
>
Tracepoint event sounds good... you sort of connect tracepoints with
events then.... :-)
TRACEPOINT_CREATE would be what exactly? Afraid I got a bit lost...
/Nils
> Thanks,
>
> Mathieu
>
>>
>>>
>>>>
>>>>>
>>>>> UST Markers (main API members):
>>>>>
>>>>> #include<ust/marker.h>
>>>>>
>>>>> ust_marker(name, "fmt", ...)
>>>>> UST_MARKER_NOARGS
>>>>> GET_UST_MARKER()
>>>>> DEFINE_UST_MARKER(name, ...)
>>>>> ust_marker_probe_unregister()
>>>>> ust_marker_probe_register()
>>>>> ust_marker_synchronize_unregister()
>>>>> UST_MARKER_LIB
>>>>>
>>>>> Will be eventually phased-out with the new TRACEPOINT_TEMPLATE()
>>>>> and
>>>>> CTF:
>>>>> DEFINE_UST_MARKER_TP()
>>>>> ust_marker_tp()
>>>>>
>>>>
>>>> No problem. Simpler is better and this API will be UST specific so
>>>> rtfm at that point :).
>>>
>>> Just one question, these are UST internal right? I mean, not to be
>>> confused with the ustctl functions?
>>
>> Not sure I understand your question. But the "ust_marker()" is an API
>> exposed to application willing to do ad-hoc tracing relying
>> directly on
>> UST. These application libraries using ust_marker() would have to
>> define
>> UST_MARKER_LIB. UST_MARKER_NOARGS is also needed. For the rest, I
>> agree
>> that it's more UST-internal.
>>
>> Thanks,
>>
>> Mathieu
>>
>>>
>>> /Nils
>>>
>>>>
>>>> Thanks
>>>> David
>>>>
>>>>> Feedback is welcome,
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Mathieu
>>>>>
>>>>
>>>> --
>>>> David Goulet
>>>> LTTng project, DORSAL Lab.
>>>>
>>>> PGP/GPG : 1024D/16BD8563
>>>> BE3C 672B 9331 9796 291A 14C6 4AF7 C14B 16BD 8563
>>>>
>>>> _______________________________________________
>>>> ltt-dev mailing list
>>>> ltt-dev at lists.casi.polymtl.ca
>>>> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>>>
>>
>> --
>> Mathieu Desnoyers
>> Operating System Efficiency R&D Consultant
>> EfficiOS Inc.
>> http://www.efficios.com
>
> --
> Mathieu Desnoyers
> Operating System Efficiency R&D Consultant
> EfficiOS Inc.
> http://www.efficios.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20110420/8b834a8c/attachment-0002.htm>
next prev parent reply other threads:[~2011-04-20 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 20:59 Mathieu Desnoyers
2011-04-14 14:53 ` David Goulet
2011-04-14 19:02 ` Nils Carlson
2011-04-14 19:28 ` Mathieu Desnoyers
2011-04-19 21:56 ` Mathieu Desnoyers
2011-04-20 18:03 ` Nils Carlson [this message]
2011-04-20 18:03 ` Nils Carlson
2011-04-20 18:03 ` Nils Carlson
2011-04-20 18:10 ` Mathieu Desnoyers
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=00251A6D-FE11-49D1-B078-E854C9724D83@ludd.ltu.se \
--to=nils.carlson@ludd.ltu.se \
/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