Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1377718 > unrolled thread

Re: "perf: interrupt took too long" messages even with perf_cpu_time_max_percent==0

Started byMarkus Trippelsdorf <markus@trippelsdorf.de>
First post2016-04-13 12:10 +0200
Last post2016-04-13 12:10 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: "perf: interrupt took too long" messages even with  perf_cpu_time_max_percent==0 Markus Trippelsdorf <markus@trippelsdorf.de> - 2016-04-13 12:10 +0200

#1377718 — Re: "perf: interrupt took too long" messages even with perf_cpu_time_max_percent==0

FromMarkus Trippelsdorf <markus@trippelsdorf.de>
Date2016-04-13 12:10 +0200
SubjectRe: "perf: interrupt took too long" messages even with perf_cpu_time_max_percent==0
Message-ID<rnpUd-86v-7@gated-at.bofh.it>
On 2016.04.02 at 13:00 +0200, Peter Zijlstra wrote:
> 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?

Yes, it obviously fixes the issue.

-- 
Markus

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web