tracing: Move trace_flags from global to a trace_array field
In preparation to make trace options per instance, the global trace_flags
needs to be moved from being a global variable to a field within the trace
instance trace_array structure.
There's still more work to do, as there's some functions that use
trace_flags without passing in a way to get to the current_trace array. For
those, the global_trace is used directly (from trace.c). This includes
setting and clearing the trace_flags. This means that when a new instance is
created, it just gets the trace_flags of the global_trace and will not be
able to modify them. Depending on the functions that have access to the
trace_array, the flags of an instance may not affect parts of its trace,
where the global_trace is used. These will be fixed in future changes.
Signed-off-by:
Steven Rostedt <rostedt@goodmis.org>
Showing
- kernel/trace/blktrace.c 4 additions, 3 deletionskernel/trace/blktrace.c
- kernel/trace/trace.c 54 additions, 38 deletionskernel/trace/trace.c
- kernel/trace/trace.h 2 additions, 3 deletionskernel/trace/trace.h
- kernel/trace/trace_events.c 2 additions, 1 deletionkernel/trace/trace_events.c
- kernel/trace/trace_functions_graph.c 29 additions, 21 deletionskernel/trace/trace_functions_graph.c
- kernel/trace/trace_irqsoff.c 15 additions, 13 deletionskernel/trace/trace_irqsoff.c
- kernel/trace/trace_kdb.c 5 additions, 3 deletionskernel/trace/trace_kdb.c
- kernel/trace/trace_output.c 9 additions, 5 deletionskernel/trace/trace_output.c
- kernel/trace/trace_sched_wakeup.c 13 additions, 13 deletionskernel/trace/trace_sched_wakeup.c
- kernel/trace/trace_syscalls.c 2 additions, 1 deletionkernel/trace/trace_syscalls.c
Loading
Please register or sign in to comment