From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752575AbcFIPRU (ORCPT ); Thu, 9 Jun 2016 11:17:20 -0400 Received: from one.firstfloor.org ([193.170.194.197]:49108 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752315AbcFIPRT (ORCPT ); Thu, 9 Jun 2016 11:17:19 -0400 Date: Thu, 9 Jun 2016 08:17:16 -0700 From: Andi Kleen To: Arnaldo Carvalho de Melo Cc: Andi Kleen , peterz@infradead.org, x86@kernel.org, linux-kernel@vger.kernel.org, jolsa@kernel.org, Andi Kleen Subject: Re: [PATCH 2/2] perf stat: Remove nmi watchdog check code again Message-ID: <20160609151715.GM13997@two.firstfloor.org> References: <1465478079-19993-1-git-send-email-andi@firstfloor.org> <1465478079-19993-2-git-send-email-andi@firstfloor.org> <20160609134208.GM11589@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160609134208.GM11589@kernel.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 09, 2016 at 10:42:08AM -0300, Arnaldo Carvalho de Melo wrote: > Em Thu, Jun 09, 2016 at 06:14:39AM -0700, Andi Kleen escreveu: > > From: Andi Kleen > > > > Now that the NMI watchdog runs with reference cycles, and does not > > Now as in when? We should at least warn the user that the kernel used is > one where the NMI watchdog will not get in the way of topdown. Is there > a programmatic way to discover that? If the other patch gets merged at the same time as the TopDown patches it's only a few days in tip which don't support it, no released kernel. So no need to check for this case. -Andi