From: Randy Dunlap <rdunlap@infradead.org>
To: paulmck@linux.vnet.ibm.com
Cc: Steven Rostedt <rostedt@goodmis.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Jan 7 (rcutorture)
Date: Mon, 07 Jan 2013 22:53:13 -0800 [thread overview]
Message-ID: <50EBC259.6080702@infradead.org> (raw)
In-Reply-To: <20130108035348.GF2525@linux.vnet.ibm.com>
On 01/07/13 19:53, Paul E. McKenney wrote:
> On Mon, Jan 07, 2013 at 07:36:19PM -0500, Steven Rostedt wrote:
>> On Mon, 2013-01-07 at 18:12 -0500, Steven Rostedt wrote:
>>> On Tue, 2013-01-08 at 09:59 +1100, Stephen Rothwell wrote:
>>>> Hi Paul,
>>>>
>>>> On Mon, 7 Jan 2013 14:16:27 -0800 "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
>>>>>
>>>>> On Mon, Jan 07, 2013 at 11:42:36AM -0800, Randy Dunlap wrote:
>>>>>>
>>>>>> on i386 or x86_64:
>>>>>>
>>>>>> ERROR: "trace_clock_local" [kernel/rcutorture.ko] undefined!
>>>>>
>>>>> Hello, Randy,
>>>>>
>>>>> Did your build include the following, also pushed to -next in that same
>>>>> batch from -rcu? Including Steven Rostedt on CC for his take.
>>>>
>>>> That commit was certainly in next-20130107.
>>>
>>> Could be bad config dependencies.
>>
>> Paul,
>>
>> You need to also select TRACE_CLOCK if you are going to use it.
>
> Thank you, Steve!
>
> Randy, does the following patch help?
Yes, that's good.
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> Thanx, Paul
>
> ------------------------------------------------------------------------
>
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index ce75d3b..b0fe7bd 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -1010,6 +1010,7 @@ config RCU_CPU_STALL_INFO
> config RCU_TRACE
> bool "Enable tracing for RCU"
> depends on DEBUG_KERNEL
> + select TRACE_CLOCK
> help
> This option provides tracing in RCU which presents stats
> in debugfs for debugging RCU implementation.
>
> --
--
~Randy
next prev parent reply other threads:[~2013-01-08 6:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 3:26 linux-next: Tree for Jan 7 Stephen Rothwell
2013-01-07 19:42 ` linux-next: Tree for Jan 7 (rcutorture) Randy Dunlap
2013-01-07 22:16 ` Paul E. McKenney
2013-01-07 22:59 ` Stephen Rothwell
2013-01-07 23:12 ` Steven Rostedt
2013-01-07 23:24 ` Stephen Rothwell
2013-01-07 23:31 ` Steven Rostedt
2013-01-07 23:47 ` Paul E. McKenney
2013-01-08 0:36 ` Steven Rostedt
2013-01-08 3:53 ` Paul E. McKenney
2013-01-08 6:53 ` Randy Dunlap [this message]
2013-01-14 16:45 ` Randy Dunlap
2013-01-14 17:32 ` Paul E. McKenney
2013-01-14 18:49 ` Randy Dunlap
2013-01-14 19:49 ` Paul E. McKenney
2013-01-15 3:08 ` Steven Rostedt
2013-01-15 4:05 ` Paul E. McKenney
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=50EBC259.6080702@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).