From: Christoph Hellwig <hch@infradead.org>
To: Ron Rechenmacher <ron@fnal.gov>
Cc: linux-kernel@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] tracing: Export key trace event symbols
Date: Mon, 20 Apr 2015 23:10:34 -0700 [thread overview]
Message-ID: <20150421061034.GA9253@infradead.org> (raw)
In-Reply-To: <553571C3.1060505@fnal.gov>
On Mon, Apr 20, 2015 at 04:38:11PM -0500, Ron Rechenmacher wrote:
> If symbols are not exported, modules can no longer register additional
> (module specified) tracepoints like they use to be able to (i.e linux-3.15.x).
> Somewhere on or about commit de7b2973903c6cc50b31ee5682a69b2219b9919d
> (Author: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> Date: Tue Apr 8 17:26:21 2014 -0400
> tracepoint: Use struct pointer instead of name hash for reg/unreg tracepoints)
> modules which attempted to register additional tracing functions would
> get "Unknown symbol" errors. For example: "... Unknown symbol
> __tracepoint_sched_switch (err 0)"
> Symbols can be exported using the kernel's EXPORT_TRACEPOINT_SYMBOL_GPL macro
> to allow modules to once again register their own tracing functions (for at
> least some key points in the kernel as provided by this patch).
Which (in-tree) module fails with this? I don't think anyone should
actually register a symbol.
next prev parent reply other threads:[~2015-04-21 6:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 21:38 [PATCH] tracing: Export key trace event symbols Ron Rechenmacher
2015-04-21 6:10 ` Christoph Hellwig [this message]
2015-04-21 12:04 ` Ron Rechenmacher
2015-04-21 12:19 ` Ron Rechenmacher
2015-04-21 13:38 ` Steven Rostedt
2015-04-21 12:22 ` Christoph Hellwig
2015-04-21 13:13 ` Ron Rechenmacher
2015-04-21 13:23 ` Christoph Hellwig
2015-04-21 13:26 ` Ron Rechenmacher
2015-04-21 13:53 ` Steven Rostedt
2015-04-21 15:00 ` Ron Rechenmacher
2015-04-21 15:49 ` Steven Rostedt
2015-04-21 22:23 ` Ron Rechenmacher
2015-04-21 22:44 ` Steven Rostedt
2015-04-22 2:24 ` Ron Rechenmacher
2015-04-22 12:53 ` Steven Rostedt
2015-04-22 12:55 ` Steven Rostedt
2015-04-22 14:47 ` Arnaldo Carvalho de Melo
2015-04-22 15:36 ` David Ahern
2015-04-22 15:44 ` Steven Rostedt
2015-04-22 16:35 ` Ron Rechenmacher
2015-04-22 17:00 ` Steven Rostedt
2015-04-23 15:28 ` Pawel Moll
2015-04-23 15:33 ` Pawel Moll
2015-04-21 13:31 ` Steven Rostedt
2015-04-24 21:24 ` Steven Rostedt
2015-04-24 21:39 ` Mathieu Desnoyers
2015-04-27 19:12 ` Ron Rechenmacher
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=20150421061034.GA9253@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ron@fnal.gov \
--cc=rostedt@goodmis.org \
/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.