71e1c8ac42
When creating trace events for ftrace, the header file with the TRACE_EVENT macros must also have a macro called TRACE_SYSTEM. This macro describes the name of the system the TRACE_EVENTS are defined for. It also doubles as a way for the define_trace.h file to include the file that included it. For example: in irq.h #define TRACE_SYSTEM irq [...] #include <trace/define_trace.h> The define_trace will use TRACE_SYSTEM to include irq.h. But if the name of the trace system does not match the name of the trace header file, one can override it with: Which will change define_trace.h to inclued foo_trace.h instead of foo.h The sample comments this, but people that use the sample code will more likely use the code and not read the comments. This patch changes the sample code to use the TRACE_INCLUDE_FILE to better show developers how to use it. [ Impact: make sample less confusing to developers ] Reported-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
130 lines
3.8 KiB
C
130 lines
3.8 KiB
C
/*
|
|
* Notice that this file is not protected like a normal header.
|
|
* We also must allow for rereading of this file. The
|
|
*
|
|
* || defined(TRACE_HEADER_MULTI_READ)
|
|
*
|
|
* serves this purpose.
|
|
*/
|
|
#if !defined(_TRACE_EVENT_SAMPLE_H) || defined(TRACE_HEADER_MULTI_READ)
|
|
#define _TRACE_EVENT_SAMPLE_H
|
|
|
|
/*
|
|
* All trace headers should include tracepoint.h, until we finally
|
|
* make it into a standard header.
|
|
*/
|
|
#include <linux/tracepoint.h>
|
|
|
|
/*
|
|
* If TRACE_SYSTEM is defined, that will be the directory created
|
|
* in the ftrace directory under /debugfs/tracing/events/<system>
|
|
*
|
|
* The define_trace.h belowe will also look for a file name of
|
|
* TRACE_SYSTEM.h where TRACE_SYSTEM is what is defined here.
|
|
*
|
|
* If you want a different system than file name, you can override
|
|
* the header name by defining TRACE_INCLUDE_FILE
|
|
*
|
|
* If this file was called, goofy.h, then we would define:
|
|
*
|
|
* #define TRACE_INCLUDE_FILE goofy
|
|
*
|
|
*/
|
|
#undef TRACE_SYSTEM
|
|
#define TRACE_SYSTEM sample
|
|
|
|
/*
|
|
* The TRACE_EVENT macro is broken up into 5 parts.
|
|
*
|
|
* name: name of the trace point. This is also how to enable the tracepoint.
|
|
* A function called trace_foo_bar() will be created.
|
|
*
|
|
* proto: the prototype of the function trace_foo_bar()
|
|
* Here it is trace_foo_bar(char *foo, int bar).
|
|
*
|
|
* args: must match the arguments in the prototype.
|
|
* Here it is simply "foo, bar".
|
|
*
|
|
* struct: This defines the way the data will be stored in the ring buffer.
|
|
* There are currently two types of elements. __field and __array.
|
|
* a __field is broken up into (type, name). Where type can be any
|
|
* type but an array.
|
|
* For an array. there are three fields. (type, name, size). The
|
|
* type of elements in the array, the name of the field and the size
|
|
* of the array.
|
|
*
|
|
* __array( char, foo, 10) is the same as saying char foo[10].
|
|
*
|
|
* fast_assign: This is a C like function that is used to store the items
|
|
* into the ring buffer.
|
|
*
|
|
* printk: This is a way to print out the data in pretty print. This is
|
|
* useful if the system crashes and you are logging via a serial line,
|
|
* the data can be printed to the console using this "printk" method.
|
|
*
|
|
* Note, that for both the assign and the printk, __entry is the handler
|
|
* to the data structure in the ring buffer, and is defined by the
|
|
* TP_STRUCT__entry.
|
|
*/
|
|
TRACE_EVENT(foo_bar,
|
|
|
|
TP_PROTO(char *foo, int bar),
|
|
|
|
TP_ARGS(foo, bar),
|
|
|
|
TP_STRUCT__entry(
|
|
__array( char, foo, 10 )
|
|
__field( int, bar )
|
|
),
|
|
|
|
TP_fast_assign(
|
|
strncpy(__entry->foo, foo, 10);
|
|
__entry->bar = bar;
|
|
),
|
|
|
|
TP_printk("foo %s %d", __entry->foo, __entry->bar)
|
|
);
|
|
#endif
|
|
|
|
/***** NOTICE! The #if protection ends here. *****/
|
|
|
|
|
|
/*
|
|
* There are several ways I could have done this. If I left out the
|
|
* TRACE_INCLUDE_PATH, then it would default to the kernel source
|
|
* include/trace/events directory.
|
|
*
|
|
* I could specify a path from the define_trace.h file back to this
|
|
* file.
|
|
*
|
|
* #define TRACE_INCLUDE_PATH ../../samples/trace_events
|
|
*
|
|
* But I chose to simply make it use the current directory and then in
|
|
* the Makefile I added:
|
|
*
|
|
* CFLAGS_trace-events-sample.o := -I$(PWD)/samples/trace_events/
|
|
*
|
|
* This will make sure the current path is part of the include
|
|
* structure for our file so that we can find it.
|
|
*
|
|
* I could have made only the top level directory the include:
|
|
*
|
|
* CFLAGS_trace-events-sample.o := -I$(PWD)
|
|
*
|
|
* And then let the path to this directory be the TRACE_INCLUDE_PATH:
|
|
*
|
|
* #define TRACE_INCLUDE_PATH samples/trace_events
|
|
*
|
|
* But then if something defines "samples" or "trace_events" then we
|
|
* could risk that being converted too, and give us an unexpected
|
|
* result.
|
|
*/
|
|
#undef TRACE_INCLUDE_PATH
|
|
#undef TRACE_INCLUDE_FILE
|
|
#define TRACE_INCLUDE_PATH .
|
|
/*
|
|
* TRACE_INCLUDE_FILE is not needed if the filename and TRACE_SYSTEM are equal
|
|
*/
|
|
#define TRACE_INCLUDE_FILE trace-events-sample
|
|
#include <trace/define_trace.h>
|