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 2/3] ftrace: add tracepoint for hrtimer
Date: Tue, 26 May 2009 23:44:05 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.0905262340510.1762@localhost.localdomain> (raw)
In-Reply-To: <4A16764F.2040307@cn.fujitsu.com>
On Fri, 22 May 2009, Xiao Guangrong wrote:
> +TRACE_EVENT(hrtimer_start,
> +
> + TP_PROTO(struct hrtimer *timer),
> +
> + TP_ARGS(timer),
> +
> + TP_STRUCT__entry(
> + __field( void *, timer )
> + __field( void *, function )
> + __field( s64, expires )
> + __field( s64, softexpires )
> + ),
> +
> + TP_fast_assign(
> + __entry->timer = timer;
> + __entry->function = timer->function;
> + __entry->expires = ktime_to_ns(hrtimer_get_expires(timer));
> + __entry->softexpires = ktime_to_ns(hrtimer_get_softexpires(timer));
> + ),
Yuck, we really do not want expensive conversions in the fast
path. This can be done by printk or user space tools.
> @@ -1119,6 +1122,7 @@ void hrtimer_init(struct hrtimer *timer, clockid_t clock_id,
> {
> debug_hrtimer_init(timer);
> __hrtimer_init(timer, clock_id, mode);
> + trace_hrtimer_init(timer, clock_id, mode);
The comments I made about the timer.c tracepoints vs. debugobjects
apply here as well.
Thanks,
tglx
next prev parent reply other threads:[~2009-05-26 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 9:54 Xiao Guangrong
2009-05-26 21:44 ` Thomas Gleixner [this message]
2009-05-27 7:39 ` 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.0905262340510.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®