From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161662AbcFGTy5 (ORCPT ); Tue, 7 Jun 2016 15:54:57 -0400 Received: from merlin.infradead.org ([205.233.59.134]:56811 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1161210AbcFGTy4 (ORCPT ); Tue, 7 Jun 2016 15:54:56 -0400 Date: Tue, 7 Jun 2016 21:54:48 +0200 From: Peter Zijlstra To: Josh Poimboeuf Cc: Ingo Molnar , linux-kernel@vger.kernel.org, Mel Gorman , Matt Fleming , Srikar Dronamraju Subject: Re: [PATCH 2/2] sched/debug: fix deadlock when enabling sched events Message-ID: <20160607195448.GL30154@twins.programming.kicks-ass.net> References: <50a0f7f2a5f8d69e0440c3430f06be7ccbe59903.1465322027.git.jpoimboe@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50a0f7f2a5f8d69e0440c3430f06be7ccbe59903.1465322027.git.jpoimboe@redhat.com> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 07, 2016 at 02:43:17PM -0500, Josh Poimboeuf wrote: > 1. Instead of just warning and allowing the tracepoints to be broken, > I'd argue that it would be better to make them work by forcing > schedstats enabled and printing a warning about that, which is what's Forcing them enabled doesn't make them useful per se; some of these tracepoint rely on previously recoded state, which now wasn't previously recorded because back then it was disabled. But yes, maybe this is better...