[ltt-dev] [RFC] UST Tracepoint API Changes

[Mathieu Desnoyers]

Hi,

Following discussions at LinuxCon, there are two changes I would like to
propose for the TRACEPOINT_EVENT API. Comments are welcome:

1) Change the first argument of TRACEPOINT_EVENT, defined as:

  < [com_company_]project_[component_]event >

  for two arguments, separated by a comma:

  < [com_company_]project[_component] >, < event >

This would be more in line with the Dtrace "provider, event" scheme,
which is already very much in use for instrumentation. This would allow
application developers to make the mapping to dtrace instrumentation
they might already have more easiy.

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.
tracep_ sounds too much like ptrace.
tracept_ might be good enough. It's only downside might be to sound like
"trace-pity" when we say it out loud. ;-)

Thanks,

Mathieu

-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com