From: matthew.khouzam@ericsson.com (Matthew Khouzam)
Subject: [ltt-dev] [RFC] UST Tracepoint API Changes
Date: Mon, 7 Nov 2011 16:53:47 -0500 [thread overview]
Message-ID: <4EB8536B.9020200@ericsson.com> (raw)
In-Reply-To: <20111105121611.GA18477@Krystal>
trace_printf sounds great, people already think printf when they have to
debug so this is a natural fit.
On 11-11-05 08:16 AM, Mathieu Desnoyers wrote:
> * Matthew Khouzam (matthew.khouzam at ericsson.com) wrote:
>> On 11-11-02 10:00 AM, Mathieu Desnoyers wrote:
> [...]
>>> 2) Not sure about the following one: TRACEPOINT_EVENT is quite long to
>>> type in, and so it "tracepoint()", and the upcoming
>>> "tracepoint_printf()". I'm thinking about going for shorter names, but I
>>> also want to try not to get conflicts with existing code out there.
>>> Ideas on a shorter yet explanatory name would be very welcome.
>>>
>>> tp_* seems a little bit short and prone to conflicts.
>> sounds like toilet paper, and it is used a lot with other projects.
> agreed.
>
>>> tracep_ sounds too much like ptrace.
>> also, the p is ambiguous, why not just trace_ at that point?
> yep.
>
>>> tracept_ might be good enough. It's only downside might be to sound like
>>> "trace-pity" when we say it out loud. ;-)
>> pt is the unsaid shorthand for point. it would be easily understood by
>> most IMO. but at this point you are three letters away from tracepoint_
>> I would suggest going full length and letting those who don't like
>> typing either the option to use a code completing IDE like eclipse-cdt,
>> or making macros that make sense to them.
> I'm thinking that we could keep:
>
> TRACEPOINT_EVENT()/tracepoint() for the production-style
> instrumentation. It is meant to be well-thought anyway, so it does not
> hurt if it takes a bit more time to type in.
>
> For debug-style instrumentation, trace_printf() looks really
> interesting, and I don't find matches with google (the first matches are
> trace_printk(), in the kernel).
>
> Thoughts ?
>
> Mathieu
>
>>> Thanks,
>>>
>>> Mathieu
>>>
>> _______________________________________________
>> ltt-dev mailing list
>> ltt-dev at lists.casi.polymtl.ca
>> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>>
prev parent reply other threads:[~2011-11-07 21:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 14:00 Mathieu Desnoyers
2011-11-04 16:56 ` Matthew Khouzam
2011-11-04 19:31 ` Mathieu Desnoyers
2011-11-05 12:16 ` Mathieu Desnoyers
2011-11-07 21:53 ` Matthew Khouzam [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=4EB8536B.9020200@ericsson.com \
--to=matthew.khouzam@ericsson.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