From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Alleged fix for writer stall on -rcu branch dev
Date: Mon, 15 Apr 2019 15:26:52 -0700 [thread overview]
Message-ID: <20190415222652.GB14111@linux.ibm.com> (raw)
In-Reply-To: <20190415110403.4yivka4cofckgxwb@linutronix.de>
On Mon, Apr 15, 2019 at 01:04:03PM +0200, Sebastian Andrzej Siewior wrote:
> On 2019-04-15 03:56:45 [-0700], Paul E. McKenney wrote:
> > This is new in rcutorture as well. It is complaining that we just got
> > done with a stutter interval (in which torturing temporarily stops)
> > but not everything has progressed through the callback chain to be freed.
> > And in this case it is happening during rcutorture shutdown, so I need
> > to check the callback -- I might need end-of-run checks in that WARN_ON().
And I did need end-of-run checks, which are now in -rcu on branch dev.
> good so nothing important so far. I hope the box gets to TREE08 soon.
> Do you want to me retrigger the run with your newer dev branch once it
> is done?
I feel a bit guilty monopolizing your system...
I have accumulated a collection of forward-progress ideas, so one approach
would be for me to get those written, then running well on my systems, and
then ask for some testing on your systems. Would that be a reasonable
approach?
Might make anyone else wanting to use that system in the near term more
happy as well. ;-)
Thanx, Paul
next prev parent reply other threads:[~2019-04-15 22:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190409221426.GA11212@linux.ibm.com>
[not found] ` <20190410181538.3ocva5lmh7ghrisr@linutronix.de>
[not found] ` <20190410184105.GR14111@linux.ibm.com>
[not found] ` <20190410191918.g2yqnsmuqukmzdfe@linutronix.de>
[not found] ` <20190410203302.GT14111@linux.ibm.com>
2019-04-11 0:06 ` Alleged fix for writer stall on -rcu branch dev Paul E. McKenney
2019-04-13 14:21 ` Paul E. McKenney
2019-04-13 18:17 ` Paul E. McKenney
2019-04-15 10:41 ` Sebastian Andrzej Siewior
2019-04-15 10:40 ` Sebastian Andrzej Siewior
2019-04-15 10:56 ` Paul E. McKenney
2019-04-15 11:04 ` Sebastian Andrzej Siewior
2019-04-15 22:26 ` Paul E. McKenney [this message]
2019-04-16 8:03 ` Sebastian Andrzej Siewior
2019-04-23 15:25 ` Sebastian Andrzej Siewior
2019-04-24 5:33 ` 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=20190415222652.GB14111@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.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).