From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757636Ab0GWBhp (ORCPT ); Thu, 22 Jul 2010 21:37:45 -0400 Received: from bld-mail18.adl2.internode.on.net ([150.101.137.103]:49413 "EHLO mail.internode.on.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755913Ab0GWBho (ORCPT ); Thu, 22 Jul 2010 21:37:44 -0400 Date: Fri, 23 Jul 2010 11:37:16 +1000 From: Dave Chinner To: Steven Rostedt Cc: Ingo Molnar , 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 Subject: Re: [RFC][PATCH v1 06/15] perf: export tracepoint events via sysfs: iwlwifi and iwlwifi_io Message-ID: <20100723013716.GA7362@dastard> 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> <1279806844.3319.3.camel@gandalf.stny.rr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1279806844.3319.3.camel@gandalf.stny.rr.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 22, 2010 at 09:54:04AM -0400, Steven Rostedt wrote: > 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? Perhaps you could build that into the event class definition as well so each separate class in a subsystem can be placed in it's own sub-directory? That would make turning on and off specific classes trace points so much simpler than it now, espcially for XFS where we now have > 250 tracepoints that are mostly defined by event classes already... Cheers, Dave. -- Dave Chinner david@fromorbit.com