From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: peterz@infradead.org, mingo@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] locktorture: Torture rwlocks
Date: Tue, 30 Sep 2014 00:57:00 -0700 [thread overview]
Message-ID: <20140930075700.GQ5015@linux.vnet.ibm.com> (raw)
In-Reply-To: <1411996466-11488-1-git-send-email-dave@stgolabs.net>
On Mon, Sep 29, 2014 at 06:14:22AM -0700, Davidlohr Bueso wrote:
> We are still missing the ability to torture rwlocks, particularly the
> new queued variant (patch 1). The rest of the patches are miscellaneous
> updates.
>
> Hopefully the set is straightforward enough that it can still be
> considered for v3.18.
Queued, thank you!
Running a quick set of tests, if these pass, will send a pull request along.
Thanx, Paul
> Davidlohr Bueso (4):
> locktorture: Support rwlocks
> locktorture: Fix __acquire annotation for spinlock irq
> locktorture: Cannot hold read and write lock
> locktorture: Cleanup header usage
>
> Documentation/locking/locktorture.txt | 5 +
> kernel/locking/locktorture.c | 141 ++++++++++++++++++---
> .../selftests/rcutorture/configs/lock/CFLIST | 1 +
> .../selftests/rcutorture/configs/lock/LOCK04 | 6 +
> .../selftests/rcutorture/configs/lock/LOCK04.boot | 1 +
> 5 files changed, 137 insertions(+), 17 deletions(-)
> create mode 100644 tools/testing/selftests/rcutorture/configs/lock/LOCK04
> create mode 100644 tools/testing/selftests/rcutorture/configs/lock/LOCK04.boot
>
> --
> 1.8.4.5
>
prev parent reply other threads:[~2014-09-30 7:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 13:14 [PATCH 0/4] locktorture: Torture rwlocks Davidlohr Bueso
2014-09-29 13:14 ` [PATCH 1/4] locktorture: Support rwlocks Davidlohr Bueso
2014-09-29 13:14 ` [PATCH 2/4] locktorture: Fix __acquire annotation for spinlock irq Davidlohr Bueso
2014-09-29 13:14 ` [PATCH 3/4] locktorture: Cannot hold read and write lock Davidlohr Bueso
2014-09-29 13:14 ` [PATCH 4/4] locktorture: Cleanup header usage Davidlohr Bueso
2014-09-30 7:57 ` Paul E. McKenney [this message]
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=20140930075700.GQ5015@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=dave@stgolabs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox