From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759402Ab0GVNyM (ORCPT ); Thu, 22 Jul 2010 09:54:12 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.123]:44307 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753519Ab0GVNyI (ORCPT ); Thu, 22 Jul 2010 09:54:08 -0400 X-Authority-Analysis: v=1.1 cv=NvN00vXXLC/2Fo3NdLZJXFUM7u9qr/FOWvgMjmHRJhk= c=1 sm=0 a=yRs0Bdu_tHsA:10 a=Q9fys5e9bTEA:10 a=gMqfjgEr1zLu/65IO0LwxA==:17 a=meVymXHHAAAA:8 a=kNsVYhaQj4BY5jO9OqAA:9 a=vuuV3eiUBbbAYRsEzbAOWqQMKx0A:4 a=PUjeQqilurYA:10 a=jeBq3FmKZ4MA:10 a=gMqfjgEr1zLu/65IO0LwxA==:117 X-Cloudmark-Score: 0 X-Originating-IP: 74.67.89.75 Subject: Re: [RFC][PATCH v1 06/15] perf: export tracepoint events via sysfs: iwlwifi and iwlwifi_io From: Steven Rostedt To: Ingo Molnar Cc: Johannes Berg , Lin Ming , Reinette Chatre , Robert Richter , Corey Ashford , Peter Zijlstra , Greg KH , Frederic Weisbecker , Paul Mundt , "eranian@gmail.com" , "Gary.Mohr@Bull.com" , "arjan@linux.intel.com" , "Zhang, Yanmin" , Paul Mackerras , "David S. Miller" , Russell King , Arnaldo Carvalho de Melo , Will Deacon , Maynard Johnson , Carl Love , Kay Sievers , lkml , Thomas Gleixner In-Reply-To: <20100722134836.GA6881@elte.hu> References: <1279797230.20942.87.camel@minggr.sh.intel.com> <1279797640.12439.11.camel@jlt3.sipsolutions.net> <1279805440.3319.2.camel@gandalf.stny.rr.com> <20100722134836.GA6881@elte.hu> Content-Type: text/plain; charset="ISO-8859-15" Date: Thu, 22 Jul 2010 09:54:04 -0400 Message-ID: <1279806844.3319.3.camel@gandalf.stny.rr.com> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2010-07-22 at 15:48 +0200, Ingo Molnar wrote: > * Steven Rostedt wrote: > Yeah - and the point of this submission is to allow the discussion of how to > achieve these registrations. > > Driver authors will want to have some control - for example the place where > the events directory shows up in sysfs within the driver's directory structure > - etc. > > But we indeed want to automate it as much as possible. Perhaps we can create a TRACE_EVENT_PATH() macro, that allows the developer to specify the path that the event will be seen in sysfs? -- Steve