From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753152AbcHBJab (ORCPT ); Tue, 2 Aug 2016 05:30:31 -0400 Received: from terminus.zytor.com ([198.137.202.10]:43170 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753015AbcHBJaU (ORCPT ); Tue, 2 Aug 2016 05:30:20 -0400 Date: Tue, 2 Aug 2016 01:28:09 -0700 From: tip-bot for David Ahern Message-ID: Cc: acme@redhat.com, hpa@zytor.com, jolsa@redhat.com, peterz@infradead.org, linux-kernel@vger.kernel.org, mingo@kernel.org, tglx@linutronix.de, dsa@cumulusnetworks.com, torvalds@linux-foundation.org, alexander.shishkin@linux.intel.com Reply-To: jolsa@redhat.com, peterz@infradead.org, acme@redhat.com, hpa@zytor.com, torvalds@linux-foundation.org, tglx@linutronix.de, dsa@cumulusnetworks.com, alexander.shishkin@linux.intel.com, linux-kernel@vger.kernel.org, mingo@kernel.org In-Reply-To: <1470084569-438-1-git-send-email-dsa@cumulusnetworks.com> References: <1470084569-438-1-git-send-email-dsa@cumulusnetworks.com> To: linux-tip-commits@vger.kernel.org Subject: [tip:perf/urgent] perf/core: Change log level for duration warning to KERN_INFO Git-Commit-ID: 0d87d7ec22a0879d3926faa4f4f4412a5dee1fba X-Mailer: tip-git-log-daemon Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Commit-ID: 0d87d7ec22a0879d3926faa4f4f4412a5dee1fba Gitweb: http://git.kernel.org/tip/0d87d7ec22a0879d3926faa4f4f4412a5dee1fba Author: David Ahern AuthorDate: Mon, 1 Aug 2016 13:49:29 -0700 Committer: Ingo Molnar CommitDate: Tue, 2 Aug 2016 10:23:57 +0200 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 Cc: Alexander Shishkin Cc: Arnaldo Carvalho de Melo Cc: Jiri Olsa Cc: Linus Torvalds Cc: Peter Zijlstra Cc: Thomas Gleixner Link: http://lkml.kernel.org/r/1470084569-438-1-git-send-email-dsa@cumulusnetworks.com Signed-off-by: Ingo Molnar --- kernel/events/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/events/core.c b/kernel/events/core.c index 356a6c7..a19550d 100644 --- a/kernel/events/core.c +++ b/kernel/events/core.c @@ -448,7 +448,7 @@ static u64 __report_allowed; static void perf_duration_warn(struct irq_work *w) { - printk_ratelimited(KERN_WARNING + printk_ratelimited(KERN_INFO "perf: interrupt took too long (%lld > %lld), lowering " "kernel.perf_event_max_sample_rate to %d\n", __report_avg, __report_allowed,