From: paulmck@linux.vnet.ibm.com (Paul E. McKenney)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] drivers: psci: PSCI checker module
Date: Wed, 26 Oct 2016 11:11:48 -0700 [thread overview]
Message-ID: <20161026181148.GW3716@linux.vnet.ibm.com> (raw)
In-Reply-To: <20161026173534.GC16248@red-moon>
On Wed, Oct 26, 2016 at 06:35:34PM +0100, Lorenzo Pieralisi wrote:
> On Wed, Oct 26, 2016 at 10:22:52AM -0700, Paul E. McKenney wrote:
> > On Wed, Oct 26, 2016 at 06:10:06PM +0100, Lorenzo Pieralisi wrote:
[ . . . ]
> > > Thanks a lot for your feedback, thoughts appreciated.
> >
> > Let me ask the question more directly.
> >
> > Why on earth are we trying to run these tests concurrently?
>
> We must prevent that, no question about that, that's why I started
> this discussion. It is not fine to enable this checker and the
> RCU/LOCK torture hotplug tests at the same time.
>
> > After all, if we just run one at a time in isolation, there is no
> > problem.
>
> Fine by me, it was to understand if the current assumptions we made
> are correct and they are definitely not. If we enable the PSCI checker
> we must disable the torture rcu/lock hotplug tests either statically or
> dynamically.
What rcutorture, locktorture, and rcuperf do is to invoke
torture_init_begin(), which returns false if one of these tests
is already running.
Perhaps we should extract this torture-test-exclusion and require
than conflicting torture tests invoke it?
Thanx, Paul
next prev parent reply other threads:[~2016-10-26 18:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 14:51 [PATCH v3] drivers: psci: PSCI checker module Kevin Brodsky
2016-10-25 15:45 ` Lorenzo Pieralisi
2016-10-25 18:34 ` Paul E. McKenney
2016-10-26 13:17 ` Lorenzo Pieralisi
2016-10-26 15:18 ` Paul E. McKenney
2016-10-26 17:10 ` Lorenzo Pieralisi
2016-10-26 17:22 ` Paul E. McKenney
2016-10-26 17:35 ` Lorenzo Pieralisi
2016-10-26 18:11 ` Paul E. McKenney [this message]
2016-10-27 9:13 ` Lorenzo Pieralisi
2016-10-27 12:51 ` Kevin Brodsky
2016-10-27 14:54 ` Paul E. McKenney
2016-10-27 16:06 ` Kevin Brodsky
2016-10-27 16:32 ` Lorenzo Pieralisi
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=20161026181148.GW3716@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.