[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1329333379.10311.3.camel@acer.local.home>
Date: Wed, 15 Feb 2012 14:16:19 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Witold Baryluk <baryluk@....if.uj.edu.pl>
Cc: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Rob Herring <robherring2@...il.com>,
Nicolas Pitre <nicolas.pitre@...aro.org>,
Kevin Hilman <khilman@...com>, linux-kernel@...r.kernel.org,
Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 0/3][RFC] tracing/rcu: Add _rcuidle() tracepoint to
handle rcu_idle_exit() tracepoints
On Tue, 2012-02-14 at 19:09 +0100, Witold Baryluk wrote:
> 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:
Yeah, my testing hit this issue and I fixed it up. I pushed out my
patches to Ingo that have passed all my tests. You can get them here:
https://lkml.org/lkml/2012/2/13/528
You only need to apply patches 3,4 and 5.
-- Steve
>
> 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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists