From: Dave Chinner <david@fromorbit.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Johannes Berg <johannes@sipsolutions.net>,
Lin Ming <ming.m.lin@intel.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Robert Richter <robert.richter@amd.com>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>, Greg KH <greg@kroah.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Paul Mundt <lethal@linux-sh.org>,
"eranian@gmail.com" <eranian@gmail.com>,
"Gary.Mohr@Bull.com" <Gary.Mohr@bull.com>,
"arjan@linux.intel.com" <arjan@linux.intel.com>,
"Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
Paul Mackerras <paulus@samba.org>,
"David S. Miller" <davem@davemloft.net>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Will Deacon <will.deacon@arm.com>,
Maynard Johnson <mpjohn@us.ibm.com>, Carl Love <carll@us.ibm.com>,
Kay Sievers <kay.sievers@vrfy.org>,
lkml <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC][PATCH v1 06/15] perf: export tracepoint events via sysfs: iwlwifi and iwlwifi_io
Date: Fri, 23 Jul 2010 14:20:41 +1000 [thread overview]
Message-ID: <20100723042041.GF32635@dastard> (raw)
In-Reply-To: <1279851241.3319.31.camel@gandalf.stny.rr.com>
On Thu, Jul 22, 2010 at 10:14:00PM -0400, Steven Rostedt wrote:
> On Fri, 2010-07-23 at 11:37 +1000, Dave Chinner wrote:
> > 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 <rostedt@goodmis.org> 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...
>
> I was working on creating a "TRACE_CATEGORY()" that allowed you to put
> tracepoints into categories. Thus, these tracepoints will all still be
> in the XFS system, but you can add hierarchical categories that let you
> group and enable tracepoints in these groups.
Yes, that's pretty much what I was thinking of.
> But I stopped this work since it was more ftrace specific than perf, and
> I need to figure out how to continue my work on ftrace and at the same
> time merge it towards perf. This has been taking much longer than I have
> expected. Perhaps I should just finish that work, and then see how we
> can make perf work with it too?
I'm not fussed - it's more of a wishlist item right now. If it's in
the pipeline, then I'm happy to wait until you've done all the hard
work for me. ;)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2010-07-23 4:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 11:13 [RFC][PATCH v1 06/15] perf: export tracepoint events via sysfs: iwlwifi and iwlwifi_io Lin Ming
2010-07-22 11:20 ` Johannes Berg
2010-07-22 13:30 ` Steven Rostedt
2010-07-22 13:48 ` Ingo Molnar
2010-07-22 13:54 ` Steven Rostedt
2010-07-23 1:37 ` Dave Chinner
2010-07-23 2:14 ` Steven Rostedt
2010-07-23 2:45 ` Lin Ming
2010-07-23 3:57 ` Steven Rostedt
2010-07-23 4:20 ` Dave Chinner [this message]
2010-07-23 0:53 ` Lin Ming
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100723042041.GF32635@dastard \
--to=david@fromorbit.com \
--cc=Gary.Mohr@bull.com \
--cc=acme@redhat.com \
--cc=arjan@linux.intel.com \
--cc=carll@us.ibm.com \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=eranian@gmail.com \
--cc=fweisbec@gmail.com \
--cc=greg@kroah.com \
--cc=johannes@sipsolutions.net \
--cc=kay.sievers@vrfy.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=mpjohn@us.ibm.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=reinette.chatre@intel.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=robert.richter@amd.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
--cc=yanmin_zhang@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.