From: Frederic Weisbecker <fweisbec@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Minchan Kim <minchan.kim@gmail.com>, Mel Gorman <mel@csn.ul.ie>,
Christoph Hellwig <hch@infradead.org>,
Rik van Riel <riel@redhat.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Peter Zijlstra <peterz@infradead.org>,
Theodore Tso <tytso@mit.edu>,
Mathieu Desnoyers <compudj@krystal.dyndns.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Zhaolei <zhaolei@cn.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Jason Baron <jbaron@redhat.com>,
Jiaying Zhang <jiayingz@google.com>,
Tom Zanussi <tzanussi@gmail.com>
Subject: Re: [PATCH 4/8] tracing/events: modify irq print to new format
Date: Wed, 10 Jun 2009 00:22:19 +0200 [thread overview]
Message-ID: <20090609222217.GE6057@nowhere> (raw)
In-Reply-To: <20090609215339.384594898@goodmis.org>
On Tue, Jun 09, 2009 at 05:52:15PM -0400, Steven Rostedt wrote:
> From: Steven Rostedt <srostedt@redhat.com>
>
> Use new format for better parsing of irq events.
>
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
> ---
> include/trace/events/irq.h | 38 +++++++++++++++++++-------------------
> 1 files changed, 19 insertions(+), 19 deletions(-)
>
> diff --git a/include/trace/events/irq.h b/include/trace/events/irq.h
> index b0c7ede..c6c0ff1 100644
> --- a/include/trace/events/irq.h
> +++ b/include/trace/events/irq.h
> @@ -7,18 +7,19 @@
> #undef TRACE_SYSTEM
> #define TRACE_SYSTEM irq
>
> -#define softirq_name(sirq) { sirq##_SOFTIRQ, #sirq }
> -#define show_softirq_name(val) \
> - __print_symbolic(val, \
> - softirq_name(HI), \
> - softirq_name(TIMER), \
> - softirq_name(NET_TX), \
> - softirq_name(NET_RX), \
> - softirq_name(BLOCK), \
> - softirq_name(TASKLET), \
> - softirq_name(SCHED), \
> - softirq_name(HRTIMER), \
> - softirq_name(RCU))
> +#define softirq_name(sirq) sirq##_SOFTIRQ, #sirq
> +#define show_softirq_name_format(val) \
> + "%d=%s,%d=%s,%d=%s,%d=%s,%d=%s,%d=%s,%d=%s,%d=%s,%d=%s>"
> +#define show_softirq_name_args() \
> + softirq_name(HI), \
> + softirq_name(TIMER), \
> + softirq_name(NET_TX), \
> + softirq_name(NET_RX), \
> + softirq_name(BLOCK), \
> + softirq_name(TASKLET), \
> + softirq_name(SCHED), \
> + softirq_name(HRTIMER), \
> + softirq_name(RCU)
>
> /**
> * irq_handler_entry - called immediately before the irq action handler
> @@ -47,7 +48,7 @@ TRACE_EVENT(irq_handler_entry,
> __assign_str(name, action->name);
> ),
>
> - TP_printk("irq=%d handler=%s", __entry->irq, __get_str(name))
> + TP_FORMAT("irq=<int:irq> handler=<string:name>")
> );
>
> /**
> @@ -77,8 +78,7 @@ TRACE_EVENT(irq_handler_exit,
> __entry->ret = ret;
> ),
>
> - TP_printk("irq=%d return=%s",
> - __entry->irq, __entry->ret ? "handled" : "unhandled")
> + TP_FORMAT("irq=<int:irq> return=<if:ret:handled:unhandled>")
> );
>
> /**
> @@ -106,8 +106,8 @@ TRACE_EVENT(softirq_entry,
> __entry->vec = (int)(h - vec);
> ),
>
> - TP_printk("softirq=%d action=%s", __entry->vec,
> - show_softirq_name(__entry->vec))
> + TP_FORMAT("softirq=<int:vec> action=<sym:vec:" show_softirq_name_format(),
Just to zap the confusion, I would suggest to explicitly close the '>' here instead
of inside the macro. The current state suggests a kind of imbalance at a first glance.
> + show_softirq_name_args())
> );
>
> /**
> @@ -135,8 +135,8 @@ TRACE_EVENT(softirq_exit,
> __entry->vec = (int)(h - vec);
> ),
>
> - TP_printk("softirq=%d action=%s", __entry->vec,
> - show_softirq_name(__entry->vec))
> + TP_FORMAT("softirq=<int:vec> action=<sym:vec:" show_softirq_name_format(),
And ditto.
Frederic.
> + show_softirq_name_args())
> );
>
> #endif /* _TRACE_IRQ_H */
> --
> 1.6.3.1
>
> --
next prev parent reply other threads:[~2009-06-09 22:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 21:52 [PATCH 0/8] [GIT PULL] simplify the print fmt in the event format files Steven Rostedt
2009-06-09 21:52 ` [PATCH 1/8] tracing: add trace_seq_vprint interface Steven Rostedt
2009-06-09 21:52 ` [PATCH 2/8] tracing: add protection around module events unload Steven Rostedt
2009-06-09 21:52 ` [PATCH 3/8] tracing/events: nicer print format for parsing Steven Rostedt
2009-06-09 21:52 ` [PATCH 4/8] tracing/events: modify irq print to new format Steven Rostedt
2009-06-09 22:22 ` Frederic Weisbecker [this message]
2009-06-09 22:46 ` Steven Rostedt
2009-06-09 21:52 ` [PATCH 5/8] tracing/events: modify sched " Steven Rostedt
2009-06-09 21:52 ` [PATCH 6/8] tracing/events: modify kmem " Steven Rostedt
2009-06-09 21:52 ` [PATCH 7/8] tracing/events: modify lockdep " Steven Rostedt
2009-06-09 21:52 ` [PATCH 8/8] tracing: add entry size to iterator Steven Rostedt
2009-06-09 23:23 ` [PATCH 0/8] [GIT PULL] simplify the print fmt in the event format files Ingo Molnar
2009-06-09 23:26 ` Ingo Molnar
2009-06-09 23:37 ` Steven Rostedt
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=20090609222217.GE6057@nowhere \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=compudj@krystal.dyndns.org \
--cc=hch@infradead.org \
--cc=jbaron@redhat.com \
--cc=jiayingz@google.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=minchan.kim@gmail.com \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tytso@mit.edu \
--cc=tzanussi@gmail.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®