From: Christoph Hellwig <hch@infradead.org>
To: Philipp Reisner <philipp.reisner@linbit.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org, akpm <akpm@linux-foundation.org>,
drbd-dev@lists.linbit.com, mingo@elte.hu, rostedt@goodmis.org
Subject: Re: [Drbd-dev] [PATCH -next] drbd: trace depends on TRACING
Date: Wed, 30 Sep 2009 12:00:01 -0400 [thread overview]
Message-ID: <20090930160001.GA3765@infradead.org> (raw)
In-Reply-To: <20090930080221.GA8032@barkeeper1-xen.linbit>
On Wed, Sep 30, 2009 at 10:02:21AM +0200, Lars Ellenberg wrote:
> TRACE_EVENT macros depend on, and use TRACE_POINTS.
> And those trace points are what compiles away if !CONFIG_TRACEPOINTS, no?
Everything compiles away when the right options are not selected.
> If using tracepoints directly, not using the (admittedly elegant)
> trace-events macro system, is in fact not wanted anymore, then
> Documentation/trace/* should be changed accordingly.
I could not find anything actively suggesting to use them. And if you
look at current mainline there is in fact no user of raw tracepoints
left and none should be introduced. If you add fancy new tracing it
might be a good idea to run it past Ingo and Steve, btw.
Ingo, now that we killed all raw tracepoints users, what do you think
about removing Documentation/trace/tracepoints.txt and
samples/tracepoints so that people have no easy way to use them?
Even better would be making their use really hard, which is not too easy
as they are used by TRACE_EVENT underneath.
> So what is the plan, going forward?
The plan is that all new tracing should use TRACE_EVENT. If that
doesn't work for some reason bring it up with the tracing people
for discussion.
prev parent reply other threads:[~2009-09-30 16:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 3:38 linux-next: Tree for September 25 Stephen Rothwell
2009-09-25 13:19 ` linux-next: 20090925 - build breaks with !CONFIG_AIO Kamalesh Babulal
2009-09-26 11:37 ` Martin Schwidefsky
2009-09-25 13:31 ` linux-next: 20090925 - hvc driver build breaks with !HVC_CONSOLE Kamalesh Babulal
2009-09-25 22:20 ` [PATCH -next] i2c: uses/select RT_MUTEXES Randy Dunlap
2009-09-26 9:47 ` Jean Delvare
2009-09-25 22:20 ` [PATCH -next] input: serio_libps2 depends on serio_i8042 Randy Dunlap
2009-09-25 22:29 ` Dmitry Torokhov
2009-09-25 22:30 ` Randy Dunlap
2009-09-25 23:03 ` [PATCH -next] drbd: trace depends on TRACING Randy Dunlap
2009-09-29 15:32 ` [Drbd-dev] " Philipp Reisner
2009-09-29 15:37 ` Christoph Hellwig
2009-09-30 8:02 ` Lars Ellenberg
2009-09-30 16:00 ` Christoph Hellwig [this message]
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=20090930160001.GA3765@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=drbd-dev@lists.linbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=philipp.reisner@linbit.com \
--cc=randy.dunlap@oracle.com \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox