summaryrefslogtreecommitdiffstats
path: root/firmware/tehuti
diff options
context:
space:
mode:
authorSteven Rostedt (Red Hat) <srostedt@redhat.com>2013-03-07 22:48:09 -0500
committerSteven Rostedt <rostedt@goodmis.org>2013-03-15 00:35:53 -0400
commit55034cd6e648155393b0d665eef76b38d49ad6bf (patch)
tree3d51bc6a1f8c7bdf7f728113b3853f4c20441be9 /firmware/tehuti
parentf4e781c0a89d5810729772290441ac7d61f321ec (diff)
downloadop-kernel-dev-55034cd6e648155393b0d665eef76b38d49ad6bf.zip
op-kernel-dev-55034cd6e648155393b0d665eef76b38d49ad6bf.tar.gz
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 'firmware/tehuti')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud