Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753148AbcDBLXz (ORCPT ); Sat, 2 Apr 2016 07:23:55 -0400 Received: from ud10.udmedia.de ([194.117.254.50]:50180 "EHLO mail.ud10.udmedia.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752569AbcDBLXy (ORCPT ); Sat, 2 Apr 2016 07:23:54 -0400 Date: Sat, 2 Apr 2016 13:23:51 +0200 From: Markus Trippelsdorf To: Peter Zijlstra Cc: linux-kernel@vger.kernel.org, Ingo Molnar , Arnaldo Carvalho de Melo , Alexander Shishkin Subject: Re: "perf: interrupt took too long" messages even with perf_cpu_time_max_percent==0 Message-ID: <20160402112351.GC305@x4> References: <20160402093239.GA305@x4> <20160402110017.GP3448@twins.programming.kicks-ass.net> <20160402111726.GB305@x4> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160402111726.GB305@x4> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 327 Lines: 11 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