From: Masami Hiramatsu <mhiramat@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <fweisbec@gmail.com>,
Theodore Tso <tytso@mit.edu>,
Arjan van de Ven <arjan@infradead.org>,
Pekka Paalanen <pq@iki.fi>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Jason Baron <jbaron@redhat.com>, Martin Bligh <mbligh@google.com>,
Mathieu Desnoyers <compudj@krystal.dyndns.org>,
"Frank Ch. Eigler" <fche@redhat.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [PATCH 0/4][RFC] event tracer
Date: Tue, 24 Feb 2009 17:25:49 -0500 [thread overview]
Message-ID: <49A473ED.4010001@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0902241706260.12697@gandalf.stny.rr.com>
Steven Rostedt wrote:
> On Tue, 24 Feb 2009, Peter Zijlstra wrote:
>
>> On Tue, 2009-02-24 at 14:33 -0500, Steven Rostedt wrote:
>>
>>> DECLARE_TRACE_FMT(sched_kthread_stop,
>>> TPPROTO(struct task_struct *t),
>>> TPARGS(t),
>>> "task %s:%d", TPARGS(t->comm, t->pid));
>> Consistency would require something like:
>>
>> DECLARE_TRACE_FMT(sched_kthread_stop,
>> TPPROTO(struct task_struct *t),
>> TPARGS(t),
>> TPFMT("task %s:%d", t->comm, t->pid));
>>
>> I seem to remember Jason proposing something like this in the past.
>
> Hmm, I'll have to look at that. (althought I was going to use a different
> TPARGS for the format args.)
>
> I have, for now:
>
> event_printk("(%s)" fmt "\n", #call, fmtargs);
>
> I guess I can redefine the TPFMT too.
>
> #undef TPFMT
> #define TPFMT(fmt, args...) \
> "(%s)" fmt "\n", #call, ##args
>
> and then I could do
>
> event_printk(fmt);
Why don't you do as below? :)
event_printk_line("(" #call ")" ##fmtandargs);
Anyway, your proposal is good for me, because it will recover
an information which tracepoint has lost.
Thank you!
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
next prev parent reply other threads:[~2009-02-24 22:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 19:33 [PATCH 0/4][RFC] event tracer Steven Rostedt
2009-02-24 19:33 ` [PATCH 1/4][RFC] tracing: add event trace infrastructure Steven Rostedt
2009-02-24 19:42 ` Andrew Morton
2009-02-24 19:46 ` Ingo Molnar
2009-02-24 22:11 ` Steven Rostedt
2009-02-24 19:33 ` [PATCH 2/4][RFC] tracing: add DECLARE_TRACE_FMT to tracepoint.h Steven Rostedt
2009-02-24 19:33 ` [PATCH 3/4][RFC] tracing: add schedule events to event trace Steven Rostedt
2009-02-24 19:33 ` [PATCH 4/4][RFC] tracing: make event directory structure Steven Rostedt
2009-02-24 19:39 ` [PATCH 0/4][RFC] event tracer Ingo Molnar
2009-02-24 19:42 ` Peter Zijlstra
2009-02-24 22:10 ` Steven Rostedt
2009-02-24 22:25 ` Masami Hiramatsu [this message]
2009-02-24 22:31 ` Steven Rostedt
2009-02-25 1:01 ` Mathieu Desnoyers
2009-02-25 1:15 ` Steven Rostedt
2009-02-25 1:46 ` Mathieu Desnoyers
2009-02-25 0:59 ` Mathieu Desnoyers
2009-02-25 2:10 ` Frank Ch. Eigler
2009-02-25 14:19 ` Jason Baron
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=49A473ED.4010001@redhat.com \
--to=mhiramat@redhat.com \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=compudj@krystal.dyndns.org \
--cc=fche@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jbaron@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=pq@iki.fi \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
/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