From: Steffen Persvold <sp@numascale.com>
To: paulmck@linux.vnet.ibm.com
Cc: Daniel J Blueman <daniel@numascale-asia.com>,
Dipankar Sarma <dipankar@in.ibm.com>,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: RCU qsmask !=0 warnings on large-SMP...
Date: Wed, 25 Jan 2012 23:51:08 +0100 [thread overview]
Message-ID: <4F20875C.3000207@numascale.com> (raw)
In-Reply-To: <20120125215121.GK2849@linux.vnet.ibm.com>
On 1/25/2012 22:51, Paul E. McKenney wrote:
> On Wed, Jan 25, 2012 at 09:35:15PM +0100, Steffen Persvold wrote:
[]
>>
>> Yes, 3.2.1 is our debug target right now.
>
> OK, good! Could you please add an "ftrace_dump(DUMP_ALL)" before you
> print the first set of error messages? (Preferably set up so that
> you only dump once!)
>
> Then before you start testing, could you please enable the
> rcu_grace_period and rcu_grace_period_init trace events? This should
> get a good picture of the sequence of grace-period-related events leading
> up to the failure.
>
> You will need to build the kernel with CONFIG_RCU_TRACE=y.
>
> The usual commands suffice to enable tracing:
>
> echo 1> /sys/kernel/debug/tracing/events/rcu_grace_period/enable
> echo 1> /sys/kernel/debug/tracing/events/rcu_grace_period_init/enable
>
> This should give some history that might help understand why the previous
> grace period ended before the CPUs had all checked in. Maybe even why
> the rcu_node structures got advance notice of the new grace period...
>
[]
>>
>> Are you talking about the data from /sys/kernel/debug/rcu/ ? I have
>> CONFIG_RCU_TRACE (and consequently CONFIG_TREE_RCU_TRACE) set, is
>> this enough to get the event data you want ?
>
> Yep, if you have CONFIG_RCU_TRACE=y, then the two tracepoints should
> be available.
>
It seems that I don't have the /sys/kernel/debug/tracing/events
interface on the kernel I'm running now. Perhaps I need to enable the
CONFIG_FTRACE feature also ? If so what FTRACE interfaces do I need ?
Cheers,
--
Steffen Persvold, Chief Architect NumaChip
Numascale AS - www.numascale.com
Tel: +47 92 49 25 54 Skype: spersvold
next prev parent reply other threads:[~2012-01-25 22:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 9:44 RCU qsmask !=0 warnings on large-SMP Daniel J Blueman
2012-01-25 14:00 ` Paul E. McKenney
2012-01-25 14:18 ` Steffen Persvold
2012-01-25 18:14 ` Paul E. McKenney
2012-01-25 20:35 ` Steffen Persvold
2012-01-25 21:51 ` Paul E. McKenney
2012-01-25 22:51 ` Steffen Persvold [this message]
2012-01-26 1:57 ` Paul E. McKenney
2012-01-25 21:14 ` Steffen Persvold
2012-01-25 21:34 ` Paul E. McKenney
2012-01-25 22:48 ` Steffen Persvold
2012-01-26 1:58 ` Paul E. McKenney
2012-01-26 15:04 ` Steffen Persvold
2012-01-26 19:26 ` Paul E. McKenney
2012-01-27 11:09 ` Steffen Persvold
2012-01-29 6:09 ` Paul E. McKenney
2012-01-30 16:15 ` Paul E. McKenney
2012-01-31 17:33 ` Steffen Persvold
2012-01-31 17:38 ` 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=4F20875C.3000207@numascale.com \
--to=sp@numascale.com \
--cc=daniel@numascale-asia.com \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).