From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [ltt-dev] [UST PATCH] Tracepoints: add noargs support
Date: Wed, 13 Apr 2011 13:55:37 -0400 [thread overview]
Message-ID: <20110413175537.GB28738@Krystal> (raw)
In-Reply-To: <alpine.DEB.2.00.1104111405330.25638@as68123.uab.ericsson.se>
* Nils Carlson (nils.carlson at ericsson.com) wrote:
> Again, what do you think of UST_ prefixing the "externally visible"
> macros?
I plan to make tracepoints more widely adoped that just UST. So I would
go for e.g.:
tracepoint(name, args)
register_tracepoint(name, ...)
unregister_tracepoint(name, ...)
And about the integration with TRACE_EVENT, we could also start it soon,
but I would keep it as a separate step. I plan to come up with a
different name than "trace event" because ours will be slightly
different than the in-kernel incarnation, and I don't want to confuse
users.
Thanks,
Mathieu
>
> /Nils
>
> On Mon, 11 Apr 2011, Mathieu Desnoyers wrote:
>
>> Add support for tracepoints receiving no argument as parameters. Copied
>> from Linux kernel:
>>
>> commit 38516ab59fbc5b3bb278cf5e1fe2867c70cff32e
>> Author: Steven Rostedt <srostedt at redhat.com>
>> Date: Tue Apr 20 17:04:50 2010 -0400
>>
>> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
>> CC: Nils Carlson <nils.carlson at ericsson.com>
>> CC: Steven Rostedt <srostedt at redhat.com>
>> ---
>> include/ust/tracepoint.h | 25 +++++++++++++++++++++----
>> 1 file changed, 21 insertions(+), 4 deletions(-)
>>
>> Index: ust/include/ust/tracepoint.h
>> ===================================================================
>> --- ust.orig/include/ust/tracepoint.h
>> +++ ust/include/ust/tracepoint.h
>> @@ -175,10 +175,27 @@ static inline void tracepoint_update_pro
>> { }
>> #endif /* CONFIG_TRACEPOINTS */
>>
>> -#define DECLARE_TRACE(name, proto, args) \
>> - __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), \
>> - PARAMS(void *__data, proto), \
>> - PARAMS(__data, args))
>> +/*
>> + * The need for the DECLARE_TRACE_NOARGS() is to handle the prototype
>> + * (void). "void" is a special value in a function prototype and can
>> + * not be combined with other arguments. Since the DECLARE_TRACE()
>> + * macro adds a data element at the beginning of the prototype,
>> + * we need a way to differentiate "(void *data, proto)" from
>> + * "(void *data, void)". The second prototype is invalid.
>> + *
>> + * DECLARE_TRACE_NOARGS() passes "void" as the tracepoint prototype
>> + * and "void *__data" as the callback prototype.
>> + *
>> + * DECLARE_TRACE() passes "proto" as the tracepoint protoype and
>> + * "void *__data, proto" as the callback prototype.
>> + */
>> +#define DECLARE_TRACE_NOARGS(name) \
>> + __DECLARE_TRACE(name, void, , void *__data, __data)
>> +
>> +#define DECLARE_TRACE(name, proto, args) \
>> + __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), \
>> + PARAMS(void *__data, proto), \
>> + PARAMS(__data, args))
>>
>> /*
>> * Connect a probe to a tracepoint.
>>
>> --
>> 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
prev parent reply other threads:[~2011-04-13 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 23:19 Mathieu Desnoyers
2011-04-11 12:06 ` Nils Carlson
2011-04-13 17:55 ` Mathieu Desnoyers [this message]
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=20110413175537.GB28738@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