linux-toradex.git/include/trace/perf.h, branch v4.6-rc3

tracing: Move non perf code out of perf.h

2015-09-23T13:31:34+00:00

Commit ee53bbd17257 "tracing: Move the perf code out of trace_event.h" moved
more than just the perf code out of trace_event.h, but also removed a bit of
the tracing code too. Move it back.

Signed-off-by: Steven Rostedt

tracing: Rename ftrace_get_offsets_##call() to trace_event_get_offsets_##call()

2015-05-14T01:49:01+00:00

The name "ftrace" really refers to the function hook infrastructure. It
is not about the trace_events. The function ftrace_get_offsets_##call()
is used to find the offset into dynamically allocated trace event fields
for printing. It has nothing to do with function tracing. Rename it.

Signed-off-by: Steven Rostedt

tracing: Rename ftrace_define_fields_##call() to trace_event_define_fields_##call()

2015-05-14T01:49:00+00:00

The name "ftrace" really refers to the function hook infrastructure. It
is not about the trace_events. The function ftrace_define_fields_##call()
is used to define how to process the trace_event fields. It has nothing to
do with function tracing. Rename it.

Signed-off-by: Steven Rostedt

tracing: Rename ftrace_event_type_funcs_##call to trace_event_type_funcs_##call

2015-05-14T01:48:59+00:00

The name "ftrace" really refers to the function hook infrastructure. It
is not about the trace_events. The structure ftrace_event_type_funcs_##call
is used to define how the trace_events will be printed. It has nothing to
do with function tracing. Rename it.

Signed-off-by: Steven Rostedt

tracing: Rename ftrace_data_offset_##call to trace_event_data_offset_##call

2015-05-14T01:48:58+00:00

The name "ftrace" really refers to the function hook infrastructure. It
is not about the trace_events. The structure ftrace_data_offset_##call is
used to find the offsets of dynamically allocated fields in trace_events.
It has nothing to do with function tracing. Rename it.

Signed-off-by: Steven Rostedt

tracing: Rename ftrace_raw_##call event structures to trace_event_raw_##call

2015-05-14T01:48:40+00:00

The name "ftrace" really refers to the function hook infrastructure. It
is not about the trace_events. The ftrace_raw_##call structures are built
by macros for trace events. They have nothing to do with function tracing.
Rename them.

Signed-off-by: Steven Rostedt

tracing: Rename ftrace_trigger_soft_disabled() to trace_trigger_soft_disabled()

2015-05-13T19:25:39+00:00

The name "ftrace" really refers to the function hook infrastructure. It
is not about the trace_events. The ftrace_trigger_soft_disabled() tests if a
trace_event is soft disabled (called but not traced), and returns true if
it is. It has nothing to do with function tracing and should be renamed.

Signed-off-by: Steven Rostedt

tracing: Rename FTRACE_EVENT_FL_* flags to EVENT_FILE_FL_*

2015-05-13T19:24:57+00:00

The name "ftrace" really refers to the function hook infrastructure. It
is not about the trace_events. The FTRACE_EVENT_FL_* flags are flags to
do with the trace_event files in the tracefs directory. They are not related
to function tracing. Rename them to a more descriptive name.

Signed-off-by: Steven Rostedt

tracing: Rename ftrace_output functions to trace_output

2015-05-13T18:06:41+00:00

The name "ftrace" really refers to the function hook infrastructure. It
is not about the trace_events. The ftrace_output_*() and ftrace_raw_output_*()
functions represent the trace_event code. Rename them to just trace_output
or trace_raw_output.

Signed-off-by: Steven Rostedt

tracing: Rename ftrace_event_buffer to trace_event_buffer.

2015-05-13T18:06:36+00:00

The name "ftrace" really refers to the function hook infrastructure. It
is not about the trace_events. The ftrace_event_buffer functions and data
structures are for trace_events and not for function hooks. Rename them
to trace_event_buffer*.

Signed-off-by: Steven Rostedt