From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: sedat.dilek@gmail.com
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for April 14 (Call-traces: RCU/ACPI/WQ related?)
Date: Thu, 21 Apr 2011 17:50:46 -0700 [thread overview]
Message-ID: <20110422005046.GQ2235@linux.vnet.ibm.com> (raw)
In-Reply-To: <BANLkTineNYTXffcNT59STsk5nkLhi=o-kA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1826 bytes --]
On Thu, Apr 21, 2011 at 04:47:31PM +0200, Sedat Dilek wrote:
> On Thu, Apr 21, 2011 at 4:28 PM, Paul E. McKenney
> <paulmck@linux.vnet.ibm.com> wrote:
> > On Thu, Apr 21, 2011 at 02:49:37PM +0200, Sedat Dilek wrote:
> >> On Thu, Apr 21, 2011 at 12:24 PM, Sedat Dilek
> >> <sedat.dilek@googlemail.com> wrote:
[ . . . ]
> >> Here the results from the 2nd-run (PREEMPT_RCU enabled).
> >
> > OK, and the grace periods clearly stopped advancing early on.
> >
> > Beyond that point, the per-CPU kthread is blocked, but RCU has some
> > work for it to do. So someone has called invoke_rcu_cpu_kthread(),
> > but rcu_cpu_kthread() is still blocked. I don't see a bug right
> > off-hand, but it is early in the morning for me, so I might easily
> > be missing something.
> >
> > Hmmm...
> >
> > The synchronization between these two assumes that the per-CPU
> > kthread is always bound to the respective CPU, so if was somehow
> > being migrated off, that might explain these results.
> >
> > I will add some more diagnostics, test them locally, then push
> > out an update. Seem reasonable?
> >
> > And thank you again for the testing!!!
>
> Ping me when you have new stuff for testing.
> Tomorrow (friday), here is public holiday and monday, too.
> So a looong weekend.
;-)
OK, I have a new sedat.2011.04.21a branch in the -rcu git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git
This is against 2.6.39-rc3, as before. (Yes, I do need to rebase to
2.6.39-rc4, but didn't want to change any more than I had to.)
I also have an updated script, which is attached. The output is similar
to the earlier one, and it operated is pretty much the same way.
Have a great weekend, and I look forward to seeing what shows up on
this round. I confess to still being quite puzzled!
Thanx, Paul
[-- Attachment #2: collectdebugfs.sh --]
[-- Type: application/x-sh, Size: 1679 bytes --]
next prev parent reply other threads:[~2011-04-22 0:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 8:59 linux-next: Tree for April 14 (Call-traces: RCU/ACPI/WQ related?) Sedat Dilek
2011-04-14 9:16 ` Sedat Dilek
2011-04-14 10:19 ` Sedat Dilek
2011-04-14 22:19 ` Sedat Dilek
2011-04-14 22:44 ` Paul E. McKenney
2011-04-21 5:08 ` Paul E. McKenney
2011-04-21 9:07 ` Sedat Dilek
2011-04-21 10:24 ` Sedat Dilek
2011-04-21 12:49 ` Sedat Dilek
2011-04-21 14:28 ` Paul E. McKenney
2011-04-21 14:47 ` Sedat Dilek
2011-04-22 0:50 ` Paul E. McKenney [this message]
2011-04-22 9:40 ` Sedat Dilek
2011-04-22 15:02 ` Paul E. McKenney
2011-04-22 17:36 ` Sedat Dilek
2011-04-23 21:05 ` Paul E. McKenney
2011-04-23 21:16 ` Sedat Dilek
2011-04-23 23:04 ` Sedat Dilek
2011-04-23 23:08 ` Sedat Dilek
2011-04-24 6:27 ` Paul E. McKenney
2011-04-24 9:36 ` Sedat Dilek
2011-04-24 16:43 ` Paul E. McKenney
2011-04-26 5:06 ` Paul E. McKenney
2011-04-26 11:45 ` Sedat Dilek
2011-04-26 12:42 ` Paul E. McKenney
2011-04-26 12:50 ` Sedat Dilek
2011-04-26 15:42 ` Paul E. McKenney
2011-04-26 10:06 ` Peter Zijlstra
2011-04-26 11:31 ` Paul E. McKenney
2011-04-26 19:44 ` 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=20110422005046.GQ2235@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--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).