From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: 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: Thu, 22 Jul 2010 15:48:36 +0200 [thread overview]
Message-ID: <20100722134836.GA6881@elte.hu> (raw)
In-Reply-To: <1279805440.3319.2.camel@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> On Thu, 2010-07-22 at 13:20 +0200, Johannes Berg wrote:
> > On Thu, 2010-07-22 at 19:13 +0800, Lin Ming wrote:
> > > iwlwifi and iwlwifi_io tracepoint events are exported like below,
> >
> > > drivers/net/wireless/iwlwifi/iwl3945-base.c | 15 +++++++++++++++
> > > 1 files changed, 15 insertions(+), 0 deletions(-)
> >
> > err, how about iwlagn?
>
> A lot of work went into making the include/trace/events/*.h be able to
> automate the work. Now it seems that we are going to hand code a lot, and a
> developer that adds a new system or such will now need to understand the
> internals of perf to use it. That was what I strived to avoid when creating
> the TRACE_EVENT() macros.
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.
Thanks,
Ingo
next prev parent reply other threads:[~2010-07-22 13:49 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 [this message]
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
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=20100722134836.GA6881@elte.hu \
--to=mingo@elte.hu \
--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=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.