From: Thomas Gleixner <tglx@linutronix.de>
To: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Cc: mingo@elte.hu, LKML <linux-kernel@vger.kernel.org>,
Zhaolei <zhaolei@cn.fujitsu.com>,
kosaki.motohiro@jp.fujitsu.com,
Steven Rostedt <rostedt@goodmis.org>,
fweisbec@gmail.com
Subject: Re: [PATCH 1/3] ftrace: add tracepoint for timer
Date: Tue, 26 May 2009 23:40:34 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.0905262334030.1762@localhost.localdomain> (raw)
In-Reply-To: <4A167615.7050208@cn.fujitsu.com>
On Fri, 22 May 2009, Xiao Guangrong wrote:
> This patch is modify from Mathieu's patch base on ingo's suggestion, the original patch
> can be found here:
> http://marc.info/?l=linux-kernel&m=123791201816247&w=2
I have a hard time to connect this patch to the original one.
> +TRACE_EVENT(timer_start,
> +
> + TP_PROTO(struct timer_list *timer, int cpu),
> +
> + TP_ARGS(timer, cpu),
> +
> + TP_STRUCT__entry(
> + __field( void *, timer )
> + __field( void *, function )
> + __field( unsigned long, expires )
> + __field( int, cpu )
> + ),
> +
> + TP_fast_assign(
> + __entry->timer = timer;
> + __entry->function = timer->function;
> + __entry->expires = timer->expires;
> + __entry->cpu = cpu;
> + ),
> +
> + TP_printk("timer=%p func=%pf expires=%lu cpu=%d", __entry->timer,
> + __entry->function, __entry->expires, __entry->cpu)
> +);
How do we connect the trace to the jiffies value when the timer
was started ?
> +
> +TRACE_EVENT(timer_expire,
> +
> + TP_PROTO(struct timer_list *timer),
> +
> + TP_ARGS(timer),
> +
> + TP_STRUCT__entry(
> + __field( void *, timer )
> + __field( void *, function )
> + ),
> +
> + TP_fast_assign(
> + __entry->timer = timer;
> + __entry->function = timer->function;
> + ),
> +
> + TP_printk("timer=%p func=%pf", __entry->timer, __entry->function)
> +);
Ditto.
> +TRACE_EVENT(timer_cancel,
> +
> + TP_PROTO(struct timer_list *timer),
> +
> + TP_ARGS(timer),
> +
> + TP_STRUCT__entry(
> + __field( void *, timer )
> + __field( void *, function )
> + ),
> +
> + TP_fast_assign(
> + __entry->timer = timer;
> + __entry->function = timer->function;
> + ),
> +
> + TP_printk("timer=%p func=%pf", __entry->timer, __entry->function)
> +);
Same here.
> @@ -547,6 +550,7 @@ void init_timer_key(struct timer_list *timer,
> {
> debug_timer_init(timer);
> __init_timer(timer, name, key);
> + trace_timer_init(timer);
Can we please avoid to have two debug calls in one 2 line function ?
> }
> EXPORT_SYMBOL(init_timer_key);
>
> @@ -565,6 +569,7 @@ static inline void detach_timer(struct timer_list *timer,
> struct list_head *entry = &timer->entry;
>
> debug_timer_deactivate(timer);
> + trace_timer_cancel(timer);
Ditto. Please create one debug entity which covers both.
....
Thanks,
tglx
next prev parent reply other threads:[~2009-05-26 21:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 9:53 Xiao Guangrong
2009-05-26 21:40 ` Thomas Gleixner [this message]
2009-05-27 7:36 ` Xiao Guangrong
2009-05-27 10:10 ` Thomas Gleixner
2009-05-29 2:00 ` Zhaolei
2009-05-29 9:55 ` Thomas Gleixner
2009-06-01 9:08 ` Zhaolei
2009-06-03 2:52 ` Xiao Guangrong
2009-06-03 16:39 ` Thomas Gleixner
2009-06-04 5:38 ` Xiao Guangrong
2009-06-04 8:44 ` Thomas Gleixner
2009-06-10 9:42 ` Xiao Guangrong
2009-06-10 10:58 ` Thomas Gleixner
2009-06-03 2:50 ` 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=alpine.LFD.2.00.0905262334030.1762@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=fweisbec@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®