Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753252AbbGIOsH (ORCPT ); Thu, 9 Jul 2015 10:48:07 -0400 Received: from mail.kernel.org ([198.145.29.136]:50702 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751430AbbGIOr7 (ORCPT ); Thu, 9 Jul 2015 10:47:59 -0400 Date: Thu, 9 Jul 2015 11:47:49 -0300 From: Arnaldo Carvalho de Melo To: Peter Zijlstra Cc: Ingo Molnar , Adrian Hunter , Andy Lutomirski , Vince Weaver , Thomas Gleixner , "H. Peter Anvin" , linux-kernel@vger.kernel.org, Jiri Olsa , Stephane Eranian , Borislav Petkov , Alexander Shishkin , Andi Kleen Subject: Re: [RFC PATCH] perf: Provide status of known PMUs Message-ID: <20150709144749.GA19430@kernel.org> References: <1436428080-3098-1-git-send-email-adrian.hunter@intel.com> <20150709085022.GB2859@worktop.programming.kicks-ass.net> <20150709092656.GA13336@gmail.com> <20150709115948.GS19282@twins.programming.kicks-ass.net> <20150709123205.GA9496@gmail.com> <20150709124257.GU19282@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150709124257.GU19282@twins.programming.kicks-ass.net> X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1378 Lines: 32 Em Thu, Jul 09, 2015 at 02:42:57PM +0200, Peter Zijlstra escreveu: > On Thu, Jul 09, 2015 at 02:32:05PM +0200, Ingo Molnar wrote: > > perf record error: The 'bts' PMU is not available, because the CPU does not support it > This one makes sense. > > perf record error: The 'bts' PMU is not available, because this architecture does not support it > > perf record error: The 'bts' PMU is not available, because its driver is not built into the kernel > > Because if it's the wrong architecture or CPU, I look for a box with > > the right one, if it's simply the kernel not having the necessary > > PMU driver then I'll boot a kernel with it enabled. > These not so much; why won't a generic: "Unknown PMU, check > arch/kernel" do? > The thing is, I hate that hard-coded list, its pain I don't need. Well, then we need to have tooling looking around and having tables to provide those more precise error messages, which we want to have. I guess we can do parts of that by looking at info already exported by the kernel, /proc/cpuinfo stuff, etc. But "Unknown PMU, check arch/kernel" is way too vague :-\ - Arnaldo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/