mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>,
	Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	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, 7 Jul 2009 18:03:00 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0907071739330.19480@localhost.localdomain> (raw)
In-Reply-To: <20090707140600.GA5178@Krystal>

Mathieu,

On Tue, 7 Jul 2009, Mathieu Desnoyers wrote:
> > Err, where is this an action or a call ? Care to look at the call site
> > of this tracepoint. It's at the end of do_setitimer() and records the
> > _state_ of the itimer _after_ the syscall was handled.
> > 
> 
> Hrm, right. The patch context misled me. I thought it was at the end of
> it_real_fn(), but it's actually in do_setitimer().
> 
> OK, looking at it from it's actual context, it makes perfect sense to
> name it that way.
> 
> And it could even be used as-is to iterate on all timers at trace start
> as we do in this tracer I won't name. ;-)

:)

> BTW, I was merely pointing out the risk of a name clash here. And I
> had to refer to the tree where this piece of code exists to support the
> point. My intent was not to advertise anything.

While I really do not care much about potential name clashes with out
of tree code, looking at your wrong analysis of the patch and your
mentioning of that unnamed tracer triggered my rant button :)

       tglx

  reply	other threads:[~2009-07-07 16:03 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 [this message]
2009-07-06 19:17   ` Thomas Gleixner
2009-07-07  9:30     ` 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.0907071739330.19480@localhost.localdomain \
    --to=tglx@linutronix.de \
    --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=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®