Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752542Ab0A3Inj (ORCPT ); Sat, 30 Jan 2010 03:43:39 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751567Ab0A3Ini (ORCPT ); Sat, 30 Jan 2010 03:43:38 -0500 Received: from casper.infradead.org ([85.118.1.10]:47206 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750773Ab0A3Ini (ORCPT ); Sat, 30 Jan 2010 03:43:38 -0500 Subject: Re: [RFC] perf_events: support for uncore a.k.a. nest units From: Peter Zijlstra To: Corey Ashford Cc: Ingo Molnar , LKML , Andi Kleen , Paul Mackerras , Stephane Eranian , Frederic Weisbecker , Xiao Guangrong , Dan Terpstra , Philip Mucci , Maynard Johnson , Carl Love , Steven Rostedt , Arnaldo Carvalho de Melo , Masami Hiramatsu In-Reply-To: <4B6369B2.1060508@linux.vnet.ibm.com> References: <4B560ACD.4040206@linux.vnet.ibm.com> <1263994448.4283.1052.camel@laptop> <1264023204.4283.1124.camel@laptop> <4B57907E.5000207@linux.vnet.ibm.com> <20100121072118.GA10585@elte.hu> <4B58A750.2060607@linux.vnet.ibm.com> <4B58AAF7.60507@linux.vnet.ibm.com> <20100127102834.GA27357@elte.hu> <4B60990C.1030804@linux.vnet.ibm.com> <1264676244.4283.2093.camel@laptop> <4B61D0CB.4090809@linux.vnet.ibm.com> <1264705607.4283.2120.camel@laptop> <4B620AD4.8000108@linux.vnet.ibm.com> <1264758747.4283.2150.camel@laptop> <4B6369B2.1060508@linux.vnet.ibm.com> Content-Type: text/plain; charset="UTF-8" Date: Sat, 30 Jan 2010 09:42:59 +0100 Message-ID: <1264840979.24455.51.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 819 Lines: 19 On Fri, 2010-01-29 at 15:05 -0800, Corey Ashford wrote: > So you'd read the id from the sysfs topology tree, and then pass that id to the > interface? That's an interesting approach that eliminates the need to pass a > string pmu path to the kernel. No, the attr.pmu_id would reflect the location in the tree (pci location, or spu number), the pmu id reported would identify the kind of pmu driver used for that particular device. I realized this confusion after sending but didn't clarify, we should come up with a good alternative name for either (or both) uses. -- 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/