All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
	Zhaolei <zhaolei@cn.fujitsu.com>,
	kosaki.motohiro@jp.fujitsu.com,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] ftrace: add tracepoint for itimer
Date: Tue, 07 Jul 2009 17:30:12 +0800	[thread overview]
Message-ID: <4A5315A4.9080405@cn.fujitsu.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0907062104240.19480@localhost.localdomain>

Hi Thomas,

Thanks for your review.

Thomas Gleixner wrote:
> On Mon, 6 Jul 2009, Xiao Guangrong wrote:
>> +TRACE_EVENT(itimer_state,
>> +
>> +	TP_PROTO(int which, struct itimerval *value, cputime_t expires),
>> +
>> +	TP_ARGS(which, value, expires),
>> +
>> +	TP_STRUCT__entry(
>> +		__field(	int,		which		)
>> +		__field(	void *,		timer		)
>> +		__field(	int,		state		)
>> +		__field(	cputime_t,	expires		)
>> +		__field(	long,		value_sec	)
>> +		__field(	long,		value_usec	)
>> +		__field(	long,		interval_sec	)
>> +		__field(	long,		interval_usec	)
>> +		__string(	comm,		current->comm	)
>> +	),
>> +
>> +	TP_fast_assign(
>> +		__entry->which		= which;
>> +		__entry->timer		= which == ITIMER_REAL ?
>> +						&current->signal->real_timer : NULL;
> 
>   Why do we need this information at all ? There is no value in the
>   address of real_timer AFAICT.
>   

Thanks for your review. I'll send a new patch with your comments addressed.

      reply	other threads:[~2009-07-07  9:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06  9:37 [PATCH v2 0/3] ftrace: add tracepoint for timer event Xiao Guangrong
2009-07-06  9:39 ` [PATCH v2 1/3] ftrace: add tracepoint for timer Xiao Guangrong
2009-07-06 20:08   ` Thomas Gleixner
2009-07-07  9:28     ` Xiao Guangrong
2009-07-07 17:39       ` Frederic Weisbecker
2009-07-06  9:41 ` [PATCH v2 2/3] ftrace: add tracepoint for hrtimer Xiao Guangrong
2009-07-06 20:12   ` Thomas Gleixner
2009-07-15  1:33     ` Xiao Guangrong
2009-07-06  9:42 ` [PATCH v2 3/3] ftrace: add tracepoint for itimer Xiao Guangrong
2009-07-06 13:31   ` Mathieu Desnoyers
2009-07-06 19:37     ` Thomas Gleixner
2009-07-07 14:06       ` Mathieu Desnoyers
2009-07-07 16:03         ` Thomas Gleixner
2009-07-06 19:17   ` Thomas Gleixner
2009-07-07  9:30     ` 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=4A5315A4.9080405@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.