summaryrefslogtreecommitdiffstats
path: root/drivers/iommu
diff options
context:
space:
mode:
authorDave Hansen <dave.hansen@linux.intel.com>2013-05-30 10:45:59 -0700
committerIngo Molnar <mingo@kernel.org>2013-06-19 12:50:47 +0200
commitae0def05ed856343181bf1eca4fab3e09056df6d (patch)
treee6c1b8d0ee5764fa43f690a2e56a11e20527b41b /drivers/iommu
parent43b4578071c0e6d87761e113e05d45776cc75437 (diff)
downloadop-kernel-dev-ae0def05ed856343181bf1eca4fab3e09056df6d.zip
op-kernel-dev-ae0def05ed856343181bf1eca4fab3e09056df6d.tar.gz
perf/x86: Only print PMU state when also WARN()'ing
intel_pmu_handle_irq() has a warning in it if it does too many loops. It is a WARN_ONCE(), but the perf_event_print_debug() call beneath it is unconditional. For the first warning, you get a nice backtrace and message, but subsequent ones just dump the PMU state with no leading messages. I doubt this is what was intended. This patch will only print the PMU state when paired with the WARN_ON() text. It effectively open-codes WARN_ONCE()'s one-time-only logic. My suspicion is that the code really just wants to make sure we do not sit in the loop and spit out a warning for every loop iteration after the 100th. From what I've seen, this is very unlikely to happen since we also clear the PMU state. After this patch, instead of seeing the PMU state dumped each time, you will just see: [57494.894540] perf_event_intel: clearing PMU state on CPU#129 [57579.539668] perf_event_intel: clearing PMU state on CPU#10 [57587.137762] perf_event_intel: clearing PMU state on CPU#134 [57623.039912] perf_event_intel: clearing PMU state on CPU#114 [57644.559943] perf_event_intel: clearing PMU state on CPU#118 ... Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com> Signed-off-by: Peter Zijlstra <peterz@infradead.org> Link: http://lkml.kernel.org/r/20130530174559.0DB049F4@viggo.jf.intel.com Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'drivers/iommu')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud