From: Witold Baryluk <baryluk@smp.if.uj.edu.pl>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Rob Herring <robherring2@gmail.com>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Kevin Hilman <khilman@ti.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/3][RFC] tracing/rcu: Add _rcuidle() tracepoint to handle rcu_idle_exit() tracepoints
Date: Tue, 14 Feb 2012 19:09:48 +0100 [thread overview]
Message-ID: <20120214180947.GA30057@smp.if.uj.edu.pl> (raw)
Hi,
I have some problem with cpuidle tracing:
https://bugzilla.kernel.org/show_bug.cgi?id=42742
so I applied 3 patches from https://lkml.org/lkml/headers/2012/2/7/231
> Steven Rostedt (3):
> tracing/rcu: Add trace_##name##__rcuidle() static tracepoint for inside rcu_idle_exit() sections
> x86/tracing: Denote the power and cpuidle tracepoints as _rcuidle()
> cpuidle/tracing: Denote the tracepoints as being in rcu_idle_exit() section
All 3 patches applied cleanly but for unknown reasons to me compilation fails:
CC arch/x86/kernel/process.o
arch/x86/kernel/process.c: In function ‘default_idle’:
arch/x86/kernel/process.c:380:3: error: implicit declaration of function ‘trace_power_start_rcuidle’ [-Werror=implicit-function-declaration]
arch/x86/kernel/process.c:394:3: error: implicit declaration of function ‘trace_power_end_rcuidle’ [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
I think this is because
static inline void trace_##name##_rcuidle(proto) \
should have only 1 argument passed.
but more are passed
trace_cpu_idle_rcuidle(PWR_EVENT_EXIT, smp_processor_id());
trace_power_start_rcuidle(POWER_CSTATE, next_state, dev->cpu);
However this explanation fails because
trace_power_end_rcuidle(smp_processor_id());
have single argument, and because without patches
arch/x86/kernel/process.c compiles without a problem. and there is
nothing in my 'git diff' which should justify such change.
It is mainline Linus kernel with just this 3 patches added.
Any idea?
gcc version 4.6.2 (Debian 4.6.2-14)
Debian GNU/Linux, wheezy i386. (IA-32)
Intel Pentium M processor.
--
Witold Baryluk
next reply other threads:[~2012-02-14 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 18:09 Witold Baryluk [this message]
2012-02-15 19:16 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2012-02-07 14:56 Steven Rostedt
2012-02-07 15:37 ` Paul E. McKenney
2012-02-07 16:09 ` Steven Rostedt
2012-02-07 20:17 ` Josh Triplett
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=20120214180947.GA30057@smp.if.uj.edu.pl \
--to=baryluk@smp.if.uj.edu.pl \
--cc=akpm@linux-foundation.org \
--cc=khilman@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nicolas.pitre@linaro.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=robherring2@gmail.com \
--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
all inboxes | Powered by JetHome®