diff options
| author | Steven Rostedt (Red Hat) <srostedt@redhat.com> | 2013-03-07 22:48:09 -0500 |
|---|---|---|
| committer | Steven Rostedt <rostedt@goodmis.org> | 2013-03-15 00:35:53 -0400 |
| commit | 55034cd6e648155393b0d665eef76b38d49ad6bf (patch) | |
| tree | 3d51bc6a1f8c7bdf7f728113b3853f4c20441be9 /kernel/trace/trace_events.c | |
| parent | f4e781c0a89d5810729772290441ac7d61f321ec (diff) | |
| download | linux-55034cd6e648155393b0d665eef76b38d49ad6bf.tar.gz linux-55034cd6e648155393b0d665eef76b38d49ad6bf.tar.bz2 linux-55034cd6e648155393b0d665eef76b38d49ad6bf.zip | |
tracing: Add alloc_snapshot kernel command line parameter
If debugging the kernel, and the developer wants to use
tracing_snapshot() in places where tracing_snapshot_alloc() may
be difficult (or more likely, the developer is lazy and doesn't
want to bother with tracing_snapshot_alloc() at all), then adding
alloc_snapshot
to the kernel command line parameter will tell ftrace to allocate
the snapshot buffer (if configured) when it allocates the main
tracing buffer.
I also noticed that ring_buffer_expanded and tracing_selftest_disabled
had inconsistent use of boolean "true" and "false" with "0" and "1".
I cleaned that up too.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'kernel/trace/trace_events.c')
| -rw-r--r-- | kernel/trace/trace_events.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c index a376ab5eec5c..38b54c5edeb9 100644 --- a/kernel/trace/trace_events.c +++ b/kernel/trace/trace_events.c @@ -1844,8 +1844,8 @@ static char bootup_event_buf[COMMAND_LINE_SIZE] __initdata; static __init int setup_trace_event(char *str) { strlcpy(bootup_event_buf, str, COMMAND_LINE_SIZE); - ring_buffer_expanded = 1; - tracing_selftest_disabled = 1; + ring_buffer_expanded = true; + tracing_selftest_disabled = true; return 1; } |