From: Dave Jones <davej@redhat.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: RCU_USER_QS traces.
Date: Thu, 4 Oct 2012 10:41:06 -0400 [thread overview]
Message-ID: <20121004144106.GB11191@redhat.com> (raw)
> We have CONFIG_RCU_USER_QS that is a specific case. It's an intermediate state
> before we implement a true CONFIG_NO_HZ_FULL. But the option is useless on its
> own for users. Worse, it introduces a real overhead. OTOH we want it to be upstream
> to make the development of full tickless feature more incremental.
I couldn't resist trying it.. Did these get reported yet ?
WARNING: at kernel/rcutree.c:377 rcu_eqs_enter+0x93/0xa0()
Pid: 0, comm: swapper/1 Not tainted 3.6.0+ #24
Call Trace:
[<ffffffff810678af>] warn_slowpath_common+0x7f/0xc0
[<ffffffff8106790a>] warn_slowpath_null+0x1a/0x20
[<ffffffff8111a383>] rcu_eqs_enter+0x93/0xa0
[<ffffffff8111af0b>] rcu_idle_enter+0x2b/0x70
[<ffffffff8102460f>] cpu_idle+0xbf/0x140
[<ffffffff816ad18d>] start_secondary+0x252/0x254
WARNING: at kernel/rcutree.c:352 rcu_eqs_enter_common.isra.37+0x1c6/0x1e0()
Pid: 0, comm: swapper/1 Tainted: G W 3.6.0+ #24
Call Trace:
[<ffffffff810678af>] warn_slowpath_common+0x7f/0xc0
[<ffffffff8106790a>] warn_slowpath_null+0x1a/0x20
[<ffffffff8111a2d6>] rcu_eqs_enter_common.isra.37+0x1c6/0x1e0
[<ffffffff8111a355>] rcu_eqs_enter+0x65/0xa0
[<ffffffff8111af0b>] rcu_idle_enter+0x2b/0x70
[<ffffffff8102460f>] cpu_idle+0xbf/0x140
[<ffffffff816ad18d>] start_secondary+0x252/0x254
WARNING: at kernel/rcutree.c:539 rcu_eqs_exit+0x99/0xb0()
Pid: 0, comm: swapper/1 Tainted: G W 3.6.0+ #24
Call Trace:
[<ffffffff810678af>] warn_slowpath_common+0x7f/0xc0
[<ffffffff8106790a>] warn_slowpath_null+0x1a/0x20
[<ffffffff8111a0f9>] rcu_eqs_exit+0x99/0xb0
[<ffffffff8111ae9b>] rcu_idle_exit+0x2b/0x70
[<ffffffff8102461e>] cpu_idle+0xce/0x140
[<ffffffff816ad18d>] start_secondary+0x252/0x254
WARNING: at kernel/rcutree.c:513 rcu_eqs_exit_common.isra.35+0xd4/0xe0()
Pid: 0, comm: swapper/1 Tainted: G W 3.6.0+ #24
Call Trace:
[<ffffffff810678af>] warn_slowpath_common+0x7f/0xc0
[<ffffffff8106790a>] warn_slowpath_null+0x1a/0x20
[<ffffffff8111a054>] rcu_eqs_exit_common.isra.35+0xd4/0xe0
[<ffffffff8111a0bc>] rcu_eqs_exit+0x5c/0xb0
[<ffffffff8111ae9b>] rcu_idle_exit+0x2b/0x70
[<ffffffff8102461e>] cpu_idle+0xce/0x140
[<ffffffff816ad18d>] start_secondary+0x252/0x254
Dave
next reply other threads:[~2012-10-04 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 14:41 Dave Jones [this message]
2012-10-04 15:46 ` RCU_USER_QS traces Paul E. McKenney
2012-10-05 12:36 ` Frederic Weisbecker
2012-10-05 20:00 ` Dave Jones
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=20121004144106.GB11191@redhat.com \
--to=davej@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
/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).