From: Drew Richardson <drew.richardson@arm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: 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>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pawel Moll <Pawel.Moll@arm.com>
Subject: Re: [PATCH] Export irq tracepoints for use by kernel modules
Date: Tue, 22 Apr 2014 08:00:31 -0700 [thread overview]
Message-ID: <20140422150030.GA4969@dreric01-Precision-T1600> (raw)
In-Reply-To: <20140422142613.GA14535@infradead.org>
On Tue, Apr 22, 2014 at 03:26:13PM +0100, Christoph Hellwig wrote:
> On Tue, Apr 22, 2014 at 07:24:20AM -0700, Drew Richardson wrote:
> > 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.
>
> How does this matter given that there aren't any modular users?
Gator (http://git.linaro.org/arm/ds5/gator.git), an out of tree kernel
module, uses irq_handler_exit and softirq_exit. I thought it would be
helpful to export the other tracepoints from trace/events/irq.h in
case other users encountered a similar issue.
Drew
next prev parent reply other threads:[~2014-04-22 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 14:24 Drew Richardson
2014-04-22 14:26 ` Christoph Hellwig
2014-04-22 15:00 ` Drew Richardson [this message]
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=20140422150030.GA4969@dreric01-Precision-T1600 \
--to=drew.richardson@arm.com \
--cc=Pawel.Moll@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=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®