Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1369928
| From | Markus Trippelsdorf <markus@trippelsdorf.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: "perf: interrupt took too long" messages even with perf_cpu_time_max_percent==0 |
| Date | 2016-04-02 13:30 +0200 |
| Message-ID | <rjrUC-30a-7@gated-at.bofh.it> (permalink) |
| References | <rjqcb-1I3-39@gated-at.bofh.it> <rjrBf-2Rm-1@gated-at.bofh.it> <rjrKW-2UX-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 2016.04.02 at 13:17 +0200, Markus Trippelsdorf wrote: > > Does the below help? > > Thanks. I will test it later. But 91a612eea9a3 makes the assumption that only > sysctl_perf_cpu_time_max_percent==100 disables the feature also in > kernel/events/core.c. Please ignore the last sentence. It doesn't make sense. -- Markus
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
"perf: interrupt took too long" messages even with perf_cpu_time_max_percent==0 Markus Trippelsdorf <markus@trippelsdorf.de> - 2016-04-02 11:40 +0200
Re: "perf: interrupt took too long" messages even with perf_cpu_time_max_percent==0 Peter Zijlstra <peterz@infradead.org> - 2016-04-02 13:10 +0200
Re: "perf: interrupt took too long" messages even with perf_cpu_time_max_percent==0 Markus Trippelsdorf <markus@trippelsdorf.de> - 2016-04-02 13:20 +0200
Re: "perf: interrupt took too long" messages even with perf_cpu_time_max_percent==0 Markus Trippelsdorf <markus@trippelsdorf.de> - 2016-04-02 13:30 +0200
Re: "perf: interrupt took too long" messages even with perf_cpu_time_max_percent==0 Peter Zijlstra <peterz@infradead.org> - 2016-04-02 18:40 +0200
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
csiph-web