diff options
author | Peter Zijlstra <peterz@infradead.org> | 2014-02-11 15:01:16 (GMT) |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2014-02-21 20:49:07 (GMT) |
commit | cd578abb24aa67ce468c427d3356c08ea32cf768 (patch) | |
tree | 974a97cebfc368e8bee9c1beccbbd9bda00d89ef /mm/pagewalk.c | |
parent | 90ed5b0fa5eb96e1cbb34aebf6a9ed96ee1587ec (diff) | |
download | linux-cd578abb24aa67ce468c427d3356c08ea32cf768.tar.xz |
perf/x86: Warn to early_printk() in case irq_work is too slow
On Mon, Feb 10, 2014 at 08:45:16AM -0800, Dave Hansen wrote:
> The reason I coded this up was that NMIs were firing off so fast that
> nothing else was getting a chance to run. With this patch, at least the
> printk() would come out and I'd have some idea what was going on.
It will start spewing to early_printk() (which is a lot nicer to use
from NMI context too) when it fails to queue the IRQ-work because its
already enqueued.
It does have the false-positive for when two CPUs trigger the warn
concurrently, but that should be rare and some extra clutter on the
early printk shouldn't be a problem.
Cc: hpa@zytor.com
Cc: tglx@linutronix.de
Cc: dzickus@redhat.com
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: mingo@kernel.org
Fixes: 6a02ad66b2c4 ("perf/x86: Push the duration-logging printk() to IRQ context")
Signed-off-by: Peter Zijlstra <peterz@infradead.org>
Link: http://lkml.kernel.org/r/20140211150116.GO27965@twins.programming.kicks-ass.net
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'mm/pagewalk.c')
0 files changed, 0 insertions, 0 deletions