From: Wenji Huang <wenji.huang@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: tracing: Multi definition of TRACE_INCLUDE_FILE
Date: Thu, 14 Jan 2010 10:46:44 +0800 [thread overview]
Message-ID: <4B4E8594.4020707@oracle.com> (raw)
In-Reply-To: <20100114024147.GB15301@goodmis.org>
Hi Steven,
Steven Rostedt wrote:
> On Wed, Jan 06, 2010 at 03:40:40PM +0800, Wenji Huang wrote:
>> Hi,
>>
>> There are multi definition of TRACE_INCLUDE_FILE on
>> include/trace/events/{syscalls, kvm}.h
>> It will result in compilation error when some
>> out-of-tree tools like Systemtap processes kernel
>> tracepoints in a way to put header files into module.
>>
>
> Does the following patch fix your issues?
>
Yes, that could be.
Thanks,
wenji
> -- Steve
>
>
> diff --git a/include/trace/events/kvm.h b/include/trace/events/kvm.h
> index dbe1084..532d658 100644
> --- a/include/trace/events/kvm.h
> +++ b/include/trace/events/kvm.h
> @@ -4,6 +4,7 @@
> #include <linux/tracepoint.h>
>
> #undef TRACE_SYSTEM
> +#undef TRACE_INCLUDE_FILE
> #define TRACE_SYSTEM kvm
> #define TRACE_INCLUDE_FILE kvm
>
> diff --git a/include/trace/events/syscalls.h b/include/trace/events/syscalls.h
> index fb726ac..52290bb 100644
> --- a/include/trace/events/syscalls.h
> +++ b/include/trace/events/syscalls.h
> @@ -1,4 +1,5 @@
> #undef TRACE_SYSTEM
> +#undef TRACE_INCLUDE_FILE
> #define TRACE_SYSTEM raw_syscalls
> #define TRACE_INCLUDE_FILE syscalls
>
prev parent reply other threads:[~2010-01-14 2:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 7:40 tracing: Multi definition of TRACE_INCLUDE_FILE Wenji Huang
2010-01-14 2:41 ` Steven Rostedt
2010-01-14 2:46 ` Wenji Huang [this message]
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=4B4E8594.4020707@oracle.com \
--to=wenji.huang@oracle.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox