Messages in this thread | | | Date | Wed, 12 Mar 2014 20:47:07 +0000 (UTC) | From | Mathieu Desnoyers <> | Subject | Re: [for-next][PATCH 08/20] tracing: Warn if a tracepoint is not set via debugfs |
| |
----- Original Message ----- > From: "Andi Kleen" <andi@firstfloor.org> > To: "Mathieu Desnoyers" <mathieu.desnoyers@efficios.com> > Cc: "Steven Rostedt" <rostedt@goodmis.org>, "Frank Ch. Eigler" <fche@redhat.com>, linux-kernel@vger.kernel.org, "Ingo > Molnar" <mingo@kernel.org>, "Frederic Weisbecker" <fweisbec@gmail.com>, "Andrew Morton" <akpm@linux-foundation.org>, > "Johannes Berg" <johannes.berg@intel.com>, "Linus Torvalds" <torvalds@linux-foundation.org>, "Peter Zijlstra" > <peterz@infradead.org>, "Thomas Gleixner" <tglx@linutronix.de>, "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>, > "lttng-dev" <lttng-dev@lists.lttng.org>, "Rusty Russell" <rusty@rustcorp.com.au>, "Andi Kleen" <andi@firstfloor.org> > Sent: Wednesday, March 12, 2014 4:35:15 PM > Subject: Re: [for-next][PATCH 08/20] tracing: Warn if a tracepoint is not set via debugfs > > > So I understand that you wish to banish tracepoints from static inline > > functions within headers to ensure they only appear within a single module. > > This seems to be a step backward, but let's assume we stick to that rule. > > Then how do you envision dealing with Link-Time Optimisations (LTO) ? > > I assume it uses the file name defines set by Kbuild?
Just to make sure I understand your question: I understand that you are asking whether tracepoints use file name defines at all in the naming of a tracepoint. The answer to this question is: No, they do not.
> These don't change with > LTO. It's whatever was specified at compile time. Also LTO doesn't > inline over module boundaries (if the module is not built in)
Good to know. Can it inline core kernel functions into a module ?
Thanks,
Mathieu
> > -Andi >
-- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com
| |