All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Frederic Weisbecker <fweisbec@gmail.com>, Ingo <mingo@elte.hu>,
	Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
	Steven Rostedt <rostedt@goodmis.org>,
	Zhaolei <zhaolei@cn.fujitsu.com>,
	kosaki.motohiro@jp.fujitsu.com,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] ftrace: add tracepoint for timer
Date: Mon, 29 Jun 2009 09:03:51 +0800	[thread overview]
Message-ID: <4A4812F7.1010305@cn.fujitsu.com> (raw)
In-Reply-To: <20090625050908.GB6071@nowhere>



Frederic Weisbecker wrote:
> On Wed, Jun 17, 2009 at 05:39:19PM +0800, 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
>>
>> Great thanks to Thomas for giving me so many valuable advices.
>>
>> Those tracepoints are wanted and useful:
>> 1: We can detect a timer's delay
>> 2: We can monitor the lifecycle and behaviors of a timer
>>
>> Thus they help in analysing and debuging.
>>
>> Example ftrace output:
>>    insmod-3743  [001] 217105.738770: timer_init: timer=e0b3e4c8
>>    insmod-3743  [001] 217105.738868: timer_start: timer=e0b3e4c8 func=timer_fun expires=442863 timeout=50
>>    <idle>-0     [001] 217105.935436: timer_expire: timer=e0b3e4c8 func=timer_fun jiffies=442863
>>    <idle>-0     [001] 217105.935440: timer_cancel: timer=e0b3e4c8 func=timer_fun
>>
>> We expect the timer expires at 442863, after 50 jiffies, actually the timer
>> expires at 442863, so it is delayed by 0 jiffies.
>>
>> Changelog v1->v2:
>> 1: Add jiffies info into timer
>> 2: Combine debugobjects and trace as Thomas's suggestion
>>  
>> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
>> Signed-off-by: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
> 
> 
> Thomas, are you fine with these patches?
> If so, I can prepare a pull request to Ingo, unless he prefers to
> apply them himself.
> 

Hi Thomas,

What is your opinion on this patch?
Can I get your acked-by if you think this patch is useful for us?

Thanks,
Xiao

> Thanks,
> Frederic.
> 
> 

      reply	other threads:[~2009-06-29  1:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17  9:39 [PATCH v2 1/2] ftrace: add tracepoint for timer Xiao Guangrong
2009-06-17  9:41 ` [PATCH 2/2 v2] ftrace: add tracepoint for hrtimer Xiao Guangrong
2009-06-25  5:09 ` [PATCH v2 1/2] ftrace: add tracepoint for timer Frederic Weisbecker
2009-06-29  1:03   ` Xiao Guangrong [this message]

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=4A4812F7.1010305@cn.fujitsu.com \
    --to=xiaoguangrong@cn.fujitsu.com \
    --cc=fweisbec@gmail.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.