tracing: Use RING_BUFFER_ALL_CPUS for TRACE_PIPE_ALL_CPU
authorSteven Rostedt <srostedt@redhat.com>
Wed, 23 Jan 2013 20:22:59 +0000 (15:22 -0500)
committerSteven Rostedt <rostedt@goodmis.org>
Fri, 15 Mar 2013 04:34:41 +0000 (00:34 -0400)
commitae3b5093ad6004b52e2825f3db1ad8200a2724d8
treefb4918a6300a3d3016cf06da2de192a58514ee71
parentae63b31e4d0e2ec09c569306ea46f664508ef717
tracing: Use RING_BUFFER_ALL_CPUS for TRACE_PIPE_ALL_CPU

Both RING_BUFFER_ALL_CPUS and TRACE_PIPE_ALL_CPU are defined as
-1 and used to say that all the ring buffers are to be modified
or read (instead of just a single cpu, which would be >= 0).

There's no reason to keep TRACE_PIPE_ALL_CPU as it is also started
to be used for more than what it was created for, and now that
the ring buffer code added a generic RING_BUFFER_ALL_CPUS define,
we can clean up the trace code to use that instead and remove
the TRACE_PIPE_ALL_CPU macro.

Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
kernel/trace/trace.c
kernel/trace/trace.h
kernel/trace/trace_kdb.c