oprofile: remove double ring buffering
authorAndi Kleen <andi@firstfloor.org>
Thu, 1 Apr 2010 01:17:25 +0000 (03:17 +0200)
committerGreg Kroah-Hartman <gregkh@suse.de>
Mon, 5 Jul 2010 18:10:27 +0000 (11:10 -0700)
commit6f92c079c8a248a1b714f34c221356bbda97b585
treef175df7bf7f69800b7ff70f52e11355cd43c5d96
parent3da87f443367a88f89f0ecf70ff2eb57fbef3ecf
oprofile: remove double ring buffering

commit cb6e943ccf19ab6d3189147e9d625a992e016084 upstream.

oprofile used a double buffer scheme for its cpu event buffer
to avoid races on reading with the old locked ring buffer.

But that is obsolete now with the new ring buffer, so simply
use a single buffer. This greatly simplifies the code and avoids
a lot of sample drops on large runs, especially with call graph.

Based on suggestions from Steven Rostedt

For stable kernels from v2.6.32, but not earlier.

Signed-off-by: Andi Kleen <ak@linux.intel.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Robert Richter <robert.richter@amd.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
drivers/oprofile/cpu_buffer.c