From: Jan Kara <jack@suse.cz>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jan Kara <jack@suse.cz>, LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH 01/18] trace: Allow <linux/tracepoint.h> to create empty tracepoints
Date: Fri, 26 Mar 2010 02:30:40 +0100 [thread overview]
Message-ID: <20100326013039.GM3145@quack.suse.cz> (raw)
In-Reply-To: <1269306409.2957.330.camel@gandalf.stny.rr.com>
On Mon 22-03-10 21:06:49, Steven Rostedt wrote:
> And I thought I was nasty with the CPP macros ;-)
Yeah, this is the darkest magic I've ever conceived with CPP ;)
...
> > -#define DEFINE_TRACE_FN(name, reg, unreg)
> > -#define DEFINE_TRACE(name)
> > -#define EXPORT_TRACEPOINT_SYMBOL_GPL(name)
> > -#define EXPORT_TRACEPOINT_SYMBOL(name)
> > +#define DEFINE_TRACE_FN_0(name, reg, unreg)
> > +#define DEFINE_TRACE_0(name)
> > +#define EXPORT_TRACEPOINT_SYMBOL_GPL_0(name)
> > +#define EXPORT_TRACEPOINT_SYMBOL_0(name)
> > +
> > +/*
> > + * Below two-level macro magic is really needed to propely expand TRACE_CONFIG
> > + * macro to 0 or 1 in the end
>
> This is a really lame comment. There should be almost as much comments
> as code when doing CPP trickery like this.
OK, I'll expand it with a bit of CPP theory about argument expansion.
> > + */
> > +#define __DECLARE_TRACE(config, name, proto, args) \
> > + DECLARE_TRACE_##config(name, PARAMS(proto), PARAMS(args))
> > +#define __DEFINE_TRACE_FN(config, name, reg, unreg) \
> > + DEFINE_TRACE_FN_##config(name, reg, unreg)
> > +#define __DEFINE_TRACE(config, name) DEFINE_TRACE_##config(name)
> > +#define __EXPORT_TRACEPOINT_SYMBOL_GPL(config, name) \
> > + EXPORT_TRACEPOINT_SYMBOL_GPL_##config(name)
> > +#define __EXPORT_TRACEPOINT_SYMBOL(config, name) \
> > + EXPORT_TRACEPOINT_SYMBOL_##config(name)
> > +
> > +#define _DECLARE_TRACE(config, name, proto, args) \
> > + __DECLARE_TRACE(config, name, PARAMS(proto), PARAMS(args))
> > +#define _DEFINE_TRACE_FN(config, name, reg, unreg) \
> > + __DEFINE_TRACE_FN(config, name, reg, unreg)
> > +#define _DEFINE_TRACE(config, name) __DEFINE_TRACE(config, name)
> > +#define _EXPORT_TRACEPOINT_SYMBOL_GPL(config, name) \
> > + __EXPORT_TRACEPOINT_SYMBOL_GPL(config, name)
> > +#define _EXPORT_TRACEPOINT_SYMBOL(config, name) \
> > + __EXPORT_TRACEPOINT_SYMBOL(config, name)
> > +
> > +#define DECLARE_TRACE(name, proto, args) \
> > + _DECLARE_TRACE(TRACE_CONFIG, name, PARAMS(proto), PARAMS(args))
> > +#define DEFINE_TRACE_FN(name, reg, unreg) \
> > + _DEFINE_TRACE_FN(TRACE_CONFIG, name, reg, unreg)
> > +#define DEFINE_TRACE(name) _DEFINE_TRACE(TRACE_CONFIG, name)
> > +#define EXPORT_TRACEPOINT_SYMBOL_GPL(name) \
> > + _EXPORT_TRACEPOINT_SYMBOL_GPL(TRACE_CONFIG, name)
> > +#define EXPORT_TRACEPOINT_SYMBOL(name) \
> > + _EXPORT_TRACEPOINT_SYMBOL(TRACE_CONFIG, name)
...
> > /*
> > + * The two chunks below are out of include file ifdef protection because
> > + * we want to be able to define TRACE_CONFIG even before second or even
> > + * later include of linux/tracepoint.h.
> > + */
> > +/*
> > + * Make tracepoints which are not converted to a new method of enabling
> > + * always compiled in
> > + */
> > +#ifndef TRACE_CONFIG
> > +#define TRACE_CONFIG 1
> > +#endif
>
> Hmm, We can have tracepoints in a header. Would this still work if a
> header with a tracepoint was not converted but it was included in a file
> that was. Of course I haven't seen the other patches yet so I don't yet
> know what a conversion looks like.
Well, if TRACE_CONFIG is not defined while the header is included,
everything is fine. If TRACE_CONFIG would be defined, then it means that
TRACE_SYSTEM is defined as well (I tried to define them at the same place)
and thus either tracepoints belong to the same system - again fine - or
they belong to a different system. But then the header would redefine
TRACE_SYSTEM which would subsequently break the file which included the
header. So what I do should work, unless TRACE_SYSTEM is already broken...
Maybe I can expand the reasoning in the comment.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2010-03-26 1:30 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 0:32 [PATCH 0/18] Allow different tracers to be compiled independently Jan Kara
2010-03-23 0:32 ` [PATCH 01/18] trace: Allow <linux/tracepoint.h> to create empty tracepoints Jan Kara
2010-03-23 1:06 ` Steven Rostedt
2010-03-26 1:30 ` Jan Kara [this message]
2010-03-23 0:32 ` [PATCH 02/18] block: Generate blktrace trace points only if blktrace is enabled Jan Kara
2010-03-23 0:32 ` [PATCH 03/18] mm: Generate kmemtrace trace points only if they are enabled Jan Kara
2010-03-23 0:32 ` [PATCH 04/18] mac80211: Generate trace points only if api tracer enabled Jan Kara
2010-03-23 1:11 ` Johannes Berg
2010-03-23 23:54 ` Steven Rostedt
2010-03-23 0:32 ` [PATCH 05/18] workqueue: Generate trace points only when workqueue " Jan Kara
2010-03-23 0:32 ` [PATCH 06/18] sched: Generate trace points only if scheduler tracing is enabled Jan Kara
2010-03-23 1:07 ` Frederic Weisbecker
2010-03-23 23:52 ` Steven Rostedt
2010-03-24 0:31 ` Frederic Weisbecker
2010-03-23 0:32 ` [PATCH 07/18] ext4: Provide config options for enabling ext4 and jbd2 tracing Jan Kara
2010-03-23 0:32 ` [PATCH 08/18] lockdep: Provide config option for enabling lock tracepoints Jan Kara
2010-03-23 0:32 ` [PATCH 09/18] module: Provide config option to enable tracing of module load / unload Jan Kara
2010-03-23 0:32 ` [PATCH 10/18] gfs2: Provide config option for enabling trace points Jan Kara
2010-03-23 12:01 ` [Cluster-devel] " Steven Whitehouse
2010-03-23 23:56 ` Steven Rostedt
2010-03-24 11:20 ` Steven Whitehouse
2010-03-24 12:09 ` Steven Rostedt
2010-03-23 0:32 ` [PATCH 11/18] i915: Provide config option for enabling tracepoints Jan Kara
2010-03-23 8:42 ` Chris Wilson
2010-03-23 0:32 ` [PATCH 12/18] timer: Provide config option for enabling timer tracepoints Jan Kara
2010-03-23 2:01 ` Thomas Gleixner
2010-03-23 3:01 ` Steven Rostedt
2010-03-23 0:32 ` [PATCH 13/18] acpi: Provide config option to enable power tracepoints Jan Kara
2010-03-23 0:32 ` [PATCH 14/18] net: Provide config option for enabling SKB tracing Jan Kara
2010-03-23 0:32 ` [PATCH 15/18] net: Provide config option for enabling NAPI tracing Jan Kara
2010-03-23 0:32 ` [PATCH 16/18] Generate empty tracepoints if syscall tracing is disabled Jan Kara
2010-03-23 0:32 ` [PATCH 17/18] kvm: Provide config option for enabling KVM trace events Jan Kara
2010-03-23 0:32 ` [PATCH 18/18] Create config option for enabling IRQ tracepoints Jan Kara
2010-03-23 1:04 ` [PATCH 0/18] Allow different tracers to be compiled independently Frederic Weisbecker
2010-03-23 3:34 ` Theodore Tso
2010-03-23 8:05 ` Ingo Molnar
2010-03-23 12:27 ` Mathieu Desnoyers
2010-03-23 13:18 ` Steven Rostedt
2010-03-26 0:20 ` Jan Kara
2010-03-26 19:09 ` Frederic Weisbecker
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=20100326013039.GM3145@quack.suse.cz \
--to=jack@suse.cz \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
/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
all inboxes | Powered by JetHome®