Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751064AbbGIIuq (ORCPT ); Thu, 9 Jul 2015 04:50:46 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:34595 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750798AbbGIIuj (ORCPT ); Thu, 9 Jul 2015 04:50:39 -0400 Date: Thu, 9 Jul 2015 10:50:22 +0200 From: Peter Zijlstra To: Adrian Hunter Cc: Ingo Molnar , Arnaldo Carvalho de Melo , 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: <20150709085022.GB2859@worktop.programming.kicks-ass.net> References: <1436428080-3098-1-git-send-email-adrian.hunter@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1436428080-3098-1-git-send-email-adrian.hunter@intel.com> User-Agent: Mutt/1.5.22.1 (2013-10-16) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1200 Lines: 36 On Thu, Jul 09, 2015 at 10:48:00AM +0300, Adrian Hunter wrote: > Known PMUs may not be present for various reasons. > Provide a way for the user to know what the reason > is. Not a bad idea, but I do wonder where we should draw the line on what is 'known'. The patch as proposed will have bts/pt listed as 'known' for every arch out there. By that logic, x86 should list the ppc/sparc/mips/arm/etc.. PMUs as known and wrong_arch too, which might be a tad excessive. Can we limit it to PMUs for which we've (attempted to) load the drivers? That would obviously make a few of your status bits redundant, but then you've not explained why we're interested in it. > Supported > Driver error > Driver not loaded > Not supported by hardware > Wrong vendor > Unknown status There would work. > Driver not in kernel config > Not supported by kernel > Wrong architecture These will be hard, for if we don't load the driver we don't 'know' of them. -- 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/