Re: [PATCH 01/18] trace: Allow <linux/tracepoint.h> to createempty tracepoints

From: Jan Kara
Date: Thu Mar 25 2010 - 21:30:32 EST


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@xxxxxxx>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/