linux/drivers/oprofile
Robert Richter 61bccf191f oprofile: Remove 'WQ on CPUx, prefer CPUy' warning
Under certain workloads we see the following warnings:

 WQ on CPU0, prefer CPU1
 WQ on CPU0, prefer CPU2
 WQ on CPU0, prefer CPU3

It warns the user that the wq to access a per-cpu buffers runs not on
the same cpu. This happens if the wq is rescheduled on a different cpu
than where the buffer is located. This was probably implemented to
detect performance issues. Not sure if there actually is one as the
buffers are copied to a single buffer anyway which should be the
actual bottleneck.

We wont change WQ implementation. Since a user can do nothing the
warning is pointless. Removing it.

Cc: Andi Kleen <andi@firstfloor.org>
Signed-off-by: Robert Richter <robert.richter@amd.com>
2012-08-27 14:49:39 +02:00
..
buffer_sync.c oprofile: Fix locking dependency in sync_start() 2011-05-31 16:33:34 +02:00
buffer_sync.h
cpu_buffer.c oprofile: Remove 'WQ on CPUx, prefer CPUy' warning 2012-08-27 14:49:39 +02:00
cpu_buffer.h oprofile: Remove deprecated use of flush_scheduled_work() 2010-10-29 11:54:18 +02:00
event_buffer.c locking, oprofile: Annotate oprofilefs lock as raw 2011-09-13 11:12:05 +02:00
event_buffer.h oprofile: Use linux/mutex.h 2011-05-24 12:45:59 +02:00
nmi_timer_int.c oprofile, x86: Reimplement nmi timer mode using perf event 2011-11-04 16:27:18 +01:00
oprof.c oprofile, x86: Reimplement nmi timer mode using perf event 2011-11-04 16:27:18 +01:00
oprof.h oprofile: Fix oprofile_timer_exit() breakage 2011-12-07 11:16:38 +01:00
oprofile_files.c oprofile: Fix uninitialized memory access when writing to writing to oprofilefs 2011-12-19 17:18:43 +01:00
oprofile_perf.c oprofile, perf: Use per-cpu framework 2012-06-22 16:31:20 +02:00
oprofile_stats.c
oprofile_stats.h atomic: use <linux/atomic.h> 2011-07-26 16:49:47 -07:00
oprofilefs.c simple_open: automatically convert to simple_open() 2012-04-05 15:25:50 -07:00
timer_int.c oprofile: Remove exit function for timer mode 2011-11-04 15:04:35 +01:00