mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: Re: "perf: interrupt took too long" messages even with perf_cpu_time_max_percent==0
Date: Sat, 2 Apr 2016 13:00:17 +0200	[thread overview]
Message-ID: <20160402110017.GP3448@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160402093239.GA305@x4>

On Sat, Apr 02, 2016 at 11:32:39AM +0200, Markus Trippelsdorf wrote:
> Current git kernel sometimes shows:
> 
>  perf: interrupt took too long (71 > 52), lowering kernel.perf_event_max_sample_rate to 300
>  perf: interrupt took too long (103 > 88), lowering kernel.perf_event_max_sample_rate to 300
>  perf: interrupt took too long (130 > 128), lowering kernel.perf_event_max_sample_rate to 300
>  perf: interrupt took too long (175 > 162), lowering kernel.perf_event_max_sample_rate to 300
>  perf: interrupt took too long (219 > 218), lowering kernel.perf_event_max_sample_rate to 300
> ...
> 
> when running e.g. "perf top" even when  
> /proc/sys/kernel/perf_cpu_time_max_percent is set to 0.


Ah, was 0 also meant to disable it?

Does the below help?

---
 kernel/events/core.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/kernel/events/core.c b/kernel/events/core.c
index 8c3b35f2a269..21ba024c9ed1 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -412,7 +412,8 @@ int perf_cpu_time_max_percent_handler(struct ctl_table *table, int write,
 	if (ret || !write)
 		return ret;
 
-	if (sysctl_perf_cpu_time_max_percent == 100) {
+	if (sysctl_perf_cpu_time_max_percent == 100 ||
+	    sysctl_perf_cpu_time_max_percent == 0) {
 		printk(KERN_WARNING
 		       "perf: Dynamic interrupt throttling disabled, can hang your system!\n");
 		WRITE_ONCE(perf_sample_allowed_ns, 0);

  reply	other threads:[~2016-04-02 11:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-02  9:32 Markus Trippelsdorf
2016-04-02 11:00 ` Peter Zijlstra [this message]
2016-04-02 11:17   ` Markus Trippelsdorf
2016-04-02 11:23     ` Markus Trippelsdorf
2016-04-02 16:33     ` Peter Zijlstra
2016-04-13 10:03   ` Markus Trippelsdorf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160402110017.GP3448@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    --cc=mingo@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome