From: Drew Richardson <drew.richardson@arm.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Joe Perches <joe@perches.com>,
Ben Greear <greearb@candelatech.com>,
Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, Pawel Moll <pawel.moll@arm.com>
Subject: [PATCH] Export irq tracepoints for use by kernel modules
Date: Tue, 22 Apr 2014 07:24:20 -0700 [thread overview]
Message-ID: <20140422142419.GD21121@dreric01-Precision-T1600> (raw)
After commit de7b2973903c6cc50b31ee5682a69b2219b9919d ("tracepoint:
Use struct pointer instead of name hash for reg/unreg tracepoints"),
any tracepoints used in a kernel module must be exported.
Signed-off-by: Drew Richardson <drew.richardson@arm.com>
Acked-by: Pawel Moll <pawel.moll@arm.com>
---
kernel/softirq.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/kernel/softirq.c b/kernel/softirq.c
index b50990a5bea0..3a21a6c29406 100644
--- a/kernel/softirq.c
+++ b/kernel/softirq.c
@@ -30,6 +30,12 @@
#define CREATE_TRACE_POINTS
#include <trace/events/irq.h>
+EXPORT_TRACEPOINT_SYMBOL_GPL(irq_handler_entry);
+EXPORT_TRACEPOINT_SYMBOL_GPL(irq_handler_exit);
+EXPORT_TRACEPOINT_SYMBOL_GPL(softirq_entry);
+EXPORT_TRACEPOINT_SYMBOL_GPL(softirq_exit);
+EXPORT_TRACEPOINT_SYMBOL_GPL(softirq_raise);
+
/*
- No shared variables, all the data are CPU local.
- If a softirq needs serialization, let it serialize itself
--
1.8.3.2
next reply other threads:[~2014-04-22 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 14:24 Drew Richardson [this message]
2014-04-22 14:26 ` Christoph Hellwig
2014-04-22 15:00 ` Drew Richardson
2014-04-22 15:03 ` Christoph Hellwig
2014-04-22 15:01 ` Josh Boyer
2014-04-22 17:38 ` Drew Richardson
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=20140422142419.GD21121@dreric01-Precision-T1600 \
--to=drew.richardson@arm.com \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=greearb@candelatech.com \
--cc=hch@infradead.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pawel.moll@arm.com \
--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 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®