From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Mathieu Desnoyers <compudj@krystal.dyndns.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Li Zefan <lizf@cn.fujitsu.com>, Christoph Hellwig <hch@lst.de>,
Wu Fengguang <fengguang.wu@intel.com>
Subject: [PATCH 0/2][RFC] tracing: Showing symbols for TRACE_EVENT
Date: Fri, 12 Feb 2010 14:09:07 -0500 [thread overview]
Message-ID: <20100212190907.954438555@goodmis.org> (raw)
[Re-sending since my first try was missing a '>' from Frederic's
email address, and it screwed up quilt mail ]
The __print_symbolic() macro is used by TRACE_EVENT TP_printk to convert
numbers into symbols. But if those numbers are defined as ENUMS, it works
fine for ftrace trace output, but a parser reading the binary trace
will not know how to translate the enum into a number.
The first patch creates a EXTRACT_TRACE_SYMBOL(sym) macro that
a <events>.h file can add to extract out all the enums that it uses
in TRACE_EVENTs. These symbols will then appear in the event_symbols
file in the events/ directory.
The second patch converts softirq symbols in include/trace/events/irq.h
This is an RFC patch set. I want to get your feedback before I push
this out of my git repo.
Thanks,
-- Steve
next reply other threads:[~2010-02-12 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 19:09 Steven Rostedt [this message]
2010-02-12 19:09 ` [PATCH 1/2][RFC] tracing: Add EXTRACT_TRACE_SYMBOL() macro Steven Rostedt
2010-02-12 19:09 ` [PATCH 2/2][RFC] tracing: Add extract out softirq names used by irq trace events Steven Rostedt
2010-02-13 10:39 ` Peter Zijlstra
2010-02-13 11:11 ` Steven Rostedt
2010-02-25 23:48 ` Frederic Weisbecker
2010-02-26 2:26 ` Steven Rostedt
2010-02-27 10:39 ` Frederic Weisbecker
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=20100212190907.954438555@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=compudj@krystal.dyndns.org \
--cc=fengguang.wu@intel.com \
--cc=fweisbec@gmail.com \
--cc=hch@lst.de \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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.