From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>,
linux-kernel@vger.kernel.org, mingo@elte.hu, fweisbec@gmail.com,
rostedt@goodmis.org, zhaolei@cn.fujitsu.com,
Li Zefan <lizf@cn.fujitsu.com>
Subject: Re: [PATCH v3] ftrace: add a tracepoint for __raise_softirq_irqoff()
Date: Wed, 13 May 2009 23:50:37 -0400 [thread overview]
Message-ID: <20090514035037.GA8159@Krystal> (raw)
In-Reply-To: <4A0B859B.8070801@cn.fujitsu.com>
* Lai Jiangshan (laijs@cn.fujitsu.com) wrote:
> Mathieu Desnoyers wrote:
> >
> > I partially agree with you :
> >
> > Yes, we should try to fix TRACE_EVENT, but we should fix it _before_ we
> > start using it widely. Circular header dependencies is a real problem
> > with TRACE_EVENT right now.
> >
> > Until we fix this, I will be tempted to stay with a known-good solution,
> > which is DECLARE/DEFINE_TRACE.
> >
> >
>
> I partially agree with you:
>
> Yes, Circular header dependencies is a real problem with TRACE_EVENT
> right now. It is also a problem with DECLARE_TRACE. It's a stubborn
> disease with C-Language (for complex headers). Can we fix C-Language?
>
> o Macros in header (!CREATE_TRACE_POINTS)
>
> When CREATE_TRACE_POINTS is not defined, TRACE_EVENT is definitely
> the same as DECLARE_TRACE. Actually, TRACE_EVENT is:
>
> #define TRACE_EVENT(name, proto, args, struct, assign, print) \
> DECLARE_TRACE(name, PARAMS(proto), PARAMS(args))
>
> So TRACE_EVENT and DECLARE_TRACE are the same in header files.
> And so TRACE_EVENT and DECLARE_TRACE have the same advantages and
> disadvantages. More TRACE_EVENT equals to a known-good solution.
>
> o Macros in c-file
>
> tracepoint uses DEFINE_TRACE only.
>
> ftrace uses CREATE_TRACE_POINTS + TRACE_EVENT:
> #define CREATE_TRACE_POINTS
> #include <trace/events/sched.h> (which uses TRACE_EVENT)
>
> ftrace generates more code which uses the tracepoints.
>
> >
> > Then add a forward declaration of
> >
> > struct softirqaction;
> >
> > At the top of trace/irq.h. I did it in quite a few places in the LTTng
> > tree. TP_PROTO just needs a forward declaration, not the full structure
> > declaration.
> >
>
> Thank you for your valuable suggestions.
>
> You are the father of tracepoint and LTTng, your experience in
> LTTng is very useful for ftrace.
>
> I'm glad for your suggestions.
>
>
> Xiao Guangrong, could you add forward declarations of
>
> struct irqaction;
> struct softirq_action;
>
> at the top of trace/irq.h as Mathieu's suggestions.
> (and remove "#include <linux/interrupt.h>")
>
You will probably still need something like :
#ifdef CREATE_TRACE_POINTS
#include <linux/interrupt.h>
#else
struct irqaction;
struct softirq_action;
#endif
So that FTRACE has the header dependencies it needs to build.
Mathieu
> Lai
>
>
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2009-05-14 3:50 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 6:41 [PATCH v3] ftrace: add a tracepoint for __raise_softirq_irqoff() Xiao Guangrong
2009-05-05 6:53 ` Li Zefan
2009-05-07 0:57 ` Xiao Guangrong
2009-05-05 16:16 ` Mathieu Desnoyers
2009-05-11 7:28 ` Xiao Guangrong
2009-05-11 13:40 ` Mathieu Desnoyers
2009-05-11 14:09 ` Steven Rostedt
2009-05-11 14:27 ` Mathieu Desnoyers
2009-05-11 14:53 ` Steven Rostedt
2009-05-11 15:13 ` Mathieu Desnoyers
2009-05-12 9:50 ` Xiao Guangrong
2009-05-12 13:14 ` Mathieu Desnoyers
2009-05-14 10:53 ` [PATCH v4] " Xiao Guangrong
2009-05-14 12:40 ` Mathieu Desnoyers
2009-05-14 13:26 ` Steven Rostedt
2009-05-14 13:51 ` Mathieu Desnoyers
2009-05-15 1:53 ` Xiao Guangrong
2009-05-18 3:06 ` Zhaolei
2009-05-19 8:24 ` Ingo Molnar
2009-05-21 5:39 ` Zhaolei
2009-06-12 2:36 ` Lai Jiangshan
2009-06-12 9:51 ` [PATCH RFC] softirq: fix ksoftirq starved Lai Jiangshan
2009-06-17 14:53 ` Ingo Molnar
2009-06-18 3:19 ` Lai Jiangshan
2009-06-18 8:22 ` Peter Zijlstra
2009-06-20 15:48 ` Ingo Molnar
2009-07-03 9:35 ` [PATCH v4] ftrace: add a tracepoint for __raise_softirq_irqoff() Lai Jiangshan
2009-07-03 9:44 ` Ingo Molnar
2009-07-09 12:58 ` Lai Jiangshan
2009-05-14 2:44 ` [PATCH v3] " Lai Jiangshan
2009-05-14 3:50 ` Mathieu Desnoyers [this message]
2009-05-14 6:06 ` Lai Jiangshan
2009-05-14 8:05 ` Xiao Guangrong
2009-05-14 12:36 ` Mathieu Desnoyers
2009-05-14 13:25 ` Steven Rostedt
2009-05-06 13:49 ` Jason Baron
2009-05-07 1:16 ` Xiao Guangrong
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=20090514035037.GA8159@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=fweisbec@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=xiaoguangrong@cn.fujitsu.com \
--cc=zhaolei@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox