From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Mathieu Desnoyers <compudj@krystal.dyndns.org>,
Tom Zanussi <tzanussi@gmail.com>,
Masami Hiramatsu <mhiramat@redhat.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Jason Baron <jbaron@redhat.com>,
"Frank Ch. Eigler" <fche@redhat.com>,
acme@ghostprotocols.net, Steven Rostedt <srostedt@redhat.com>
Subject: [PATCH 04/10] tracing: add subsystem irq for irq events
Date: Sat, 28 Feb 2009 04:06:50 -0500 [thread overview]
Message-ID: <20090228090937.575418744@goodmis.org> (raw)
In-Reply-To: 20090228090646.265765024@goodmis.org
[-- Attachment #1: 0004-tracing-add-subsystem-irq-for-irq-events.patch --]
[-- Type: text/plain, Size: 861 bytes --]
From: Steven Rostedt <srostedt@redhat.com>
Add the TRACE_SYSTEM irq for the irq events.
Signed-off-by: Steven Rostedt <srostedt@redhat.com>
---
include/trace/irq_event_types.h | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/include/trace/irq_event_types.h b/include/trace/irq_event_types.h
index 5d0919f..47a2be1 100644
--- a/include/trace/irq_event_types.h
+++ b/include/trace/irq_event_types.h
@@ -5,6 +5,9 @@
# error Unless you know what you are doing.
#endif
+#undef TRACE_SYSTEM
+#define TRACE_SYSTEM irq
+
TRACE_FORMAT(irq_handler_entry,
TPPROTO(int irq, struct irqaction *action),
TPARGS(irq, action),
@@ -15,3 +18,5 @@ TRACE_FORMAT(irq_handler_exit,
TPARGS(irq, action, ret),
TPFMT("irq=%d handler=%s return=%s",
irq, action->name, ret ? "handled" : "unhandled"));
+
+#undef TRACE_SYSTEM
--
1.5.6.5
--
next prev parent reply other threads:[~2009-02-28 9:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-28 9:06 [PATCH 00/10] [git pull] for tip/tracing/ftrace Steven Rostedt
2009-02-28 9:06 ` [PATCH 01/10] tracing: move trace point formats to files in include/trace directory Steven Rostedt
2009-02-28 9:06 ` [PATCH 02/10] tracing: add subsystem level to trace events Steven Rostedt
2009-02-28 9:06 ` [PATCH 03/10] tracing: make the set_event and available_events subsystem aware Steven Rostedt
2009-02-28 9:06 ` Steven Rostedt [this message]
2009-02-28 9:06 ` [PATCH 05/10] tracing: add subsystem sched for sched events Steven Rostedt
2009-02-28 9:06 ` [PATCH 06/10] tracing: add interface to write into current tracer buffer Steven Rostedt
2009-02-28 9:06 ` [PATCH 07/10] tracing: add raw trace point recording infrastructure Steven Rostedt
2009-03-02 7:51 ` Tom Zanussi
2009-03-02 12:22 ` Frédéric Weisbecker
2009-03-02 13:23 ` Steven Rostedt
2009-02-28 9:06 ` [PATCH 08/10] tracing: add raw fast tracing interface for trace events Steven Rostedt
2009-02-28 9:06 ` [PATCH 09/10] tracing: create the C style tracing for the sched subsystem Steven Rostedt
2009-02-28 9:06 ` [PATCH 10/10] tracing: create the C style tracing for the irq subsystem Steven Rostedt
2009-02-28 9:17 ` [PATCH 00/10] [git pull] for tip/tracing/ftrace Ingo Molnar
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=20090228090937.575418744@goodmis.org \
--to=rostedt@goodmis.org \
--cc=acme@ghostprotocols.net \
--cc=akpm@linux-foundation.org \
--cc=compudj@krystal.dyndns.org \
--cc=fche@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jbaron@redhat.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=srostedt@redhat.com \
--cc=tzanussi@gmail.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