David Ahern 0d87d7ec22 perf/core: Change log level for duration warning to KERN_INFO ... When the perf interrupt handler exceeds a threshold warning messages are displayed on console: [12739.31793] perf interrupt took too long (2504 > 2500), lowering kernel.perf_event_max_sample_rate to 50000 [71340.165065] perf interrupt took too long (5005 > 5000), lowering kernel.perf_event_max_sample_rate to 25000 Many customers and users are confused by the message wondering if something is wrong or they need to take action to fix a problem. Since a user can not do anything to fix the issue, the message is really more informational than a warning. Adjust the log level accordingly. Signed-off-by: David Ahern <dsa@cumulusnetworks.com> Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com> Cc: Arnaldo Carvalho de Melo <acme@redhat.com> Cc: Jiri Olsa <jolsa@redhat.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Link: http://lkml.kernel.org/r/1470084569-438-1-git-send-email-dsa@cumulusnetworks.com Signed-off-by: Ingo Molnar <mingo@kernel.org>		2016-08-02 10:23:57 +02:00
..
callchain.c	perf core: Per event callchain limit	2016-05-30 12:41:44 -03:00
core.c	perf/core: Change log level for duration warning to KERN_INFO	2016-08-02 10:23:57 +02:00
hw_breakpoint.c	perf: Collapse and fix event_function_call() users	2016-01-21 18:54:24 +01:00
internal.h	bpf, events: fix offset in skb copy handler	2016-07-25 10:34:11 -07:00
Makefile	ftrace: allow architectures to specify ftrace compile options	2015-01-29 09:19:19 +01:00
ring_buffer.c	perf/core: Disable the event on a truncated AUX record	2016-05-12 14:46:11 +02:00
uprobes.c	uprobes: wait for mmap_sem for write killable	2016-05-23 17:04:14 -07:00