[RFC patch 11/32] trace event module remove semicolons

From: Mathieu Desnoyers
Date: Tue May 03 2011 - 19:20:42 EST


Part of the gradual TRACE_EVENT() semicolon removal. Enables creation of array
of events, thus saving space for trace event probes.

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
CC: Steven Rostedt <rostedt@xxxxxxxxxxx>
CC: Frederic Weisbecker <fweisbec@xxxxxxxxx>
CC: Ingo Molnar <mingo@xxxxxxx>
CC: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
CC: Li Zefan <lizf@xxxxxxxxxxxxxx>
CC: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
---
include/trace/events/module.h | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)

Index: linux-2.6-lttng/include/trace/events/module.h
===================================================================
--- linux-2.6-lttng.orig/include/trace/events/module.h
+++ linux-2.6-lttng/include/trace/events/module.h
@@ -42,7 +42,7 @@ TRACE_EVENT(module_load,
),

TP_printk("%s %s", __get_str(name), show_module_flags(__entry->taints))
-);
+)

TRACE_EVENT(module_free,

@@ -59,7 +59,7 @@ TRACE_EVENT(module_free,
),

TP_printk("%s", __get_str(name))
-);
+)

#ifdef CONFIG_MODULE_UNLOAD
/* trace_module_get/put are only used if CONFIG_MODULE_UNLOAD is defined */
@@ -84,21 +84,21 @@ DECLARE_EVENT_CLASS(module_refcnt,

TP_printk("%s call_site=%pf refcnt=%d",
__get_str(name), (void *)__entry->ip, __entry->refcnt)
-);
+)

DEFINE_EVENT(module_refcnt, module_get,

TP_PROTO(struct module *mod, unsigned long ip),

TP_ARGS(mod, ip)
-);
+)

DEFINE_EVENT(module_refcnt, module_put,

TP_PROTO(struct module *mod, unsigned long ip),

TP_ARGS(mod, ip)
-);
+)
#endif /* CONFIG_MODULE_UNLOAD */

TRACE_EVENT(module_request,
@@ -121,7 +121,7 @@ TRACE_EVENT(module_request,

TP_printk("%s wait=%d call_site=%pf",
__get_str(name), (int)__entry->wait, (void *)__entry->ip)
-);
+)

#endif /* CONFIG_MODULES */


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/