----- Original Message ----- > From: "Andi Kleen" <[email protected]> > To: "Mathieu Desnoyers" <[email protected]> > Cc: "Steven Rostedt" <[email protected]>, "Frank Ch. Eigler" > <[email protected]>, [email protected], "Ingo > Molnar" <[email protected]>, "Frederic Weisbecker" <[email protected]>, > "Andrew Morton" <[email protected]>, > "Johannes Berg" <[email protected]>, "Linus Torvalds" > <[email protected]>, "Peter Zijlstra" > <[email protected]>, "Thomas Gleixner" <[email protected]>, "Greg > Kroah-Hartman" <[email protected]>, > "lttng-dev" <[email protected]>, "Rusty Russell" > <[email protected]>, "Andi Kleen" <[email protected]> > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
