From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: fam@euphon.net, berrange@redhat.com, stefanb@linux.vnet.ibm.com,
"Alex Bennée" <alex.bennee@linaro.org>,
richard.henderson@linaro.org, f4bug@amsat.org, cota@braap.org,
stefanha@redhat.com, marcandre.lureau@redhat.com,
pbonzini@redhat.com, aurelien@aurel32.net
Subject: [PATCH v1 0/5] testing/next (rcutorture and misc tweaks)
Date: Fri, 7 Feb 2020 11:39:34 +0000 [thread overview]
Message-ID: <20200207113939.9247-1-alex.bennee@linaro.org> (raw)
Hi,
The current state of testing/next is mostly a rubber duck exercise as
I tried to figure out what might cause the rcutorture test to fail.
The only real practical change is asserting we are never about to
reset and existing active RCU structure. So far I haven't seen the
rcutorture crash occur since (although git stability seems to be a
current problem for Travis).
Alex Bennée (4):
tests/tcg: include a skip runner for pauth3 with plugins
tests/rcutorture: update usage hint
tests/rcutorture: better document locking of stats
tests/rcutorture: mild documenting refactor of update thread
Thomas Huth (1):
travis.yml: Test the s390-ccw build, too
tests/rcutorture.c | 55 +++++++++++++++++------
.travis.yml | 10 +++++
tests/tcg/aarch64/Makefile.softmmu-target | 2 +
3 files changed, 53 insertions(+), 14 deletions(-)
--
2.20.1
next reply other threads:[~2020-02-07 11:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 11:39 Alex Bennée [this message]
2020-02-07 11:39 ` [PATCH v1 1/5] tests/tcg: include a skip runner for pauth3 with plugins Alex Bennée
2020-02-07 11:39 ` [PATCH v1 2/5] tests/rcutorture: update usage hint Alex Bennée
2020-02-12 20:46 ` Philippe Mathieu-Daudé
2020-02-07 11:39 ` [PATCH v1 3/5] tests/rcutorture: better document locking of stats Alex Bennée
2020-02-12 20:47 ` Philippe Mathieu-Daudé
2020-02-07 11:39 ` [PATCH v1 4/5] tests/rcutorture: mild documenting refactor of update thread Alex Bennée
2020-02-07 11:39 ` [PATCH v1 5/5] travis.yml: Test the s390-ccw build, too Alex Bennée
2020-02-12 20:48 ` Philippe Mathieu-Daudé
2020-02-13 8:34 ` Cornelia Huck
2020-02-12 19:42 ` [PATCH v1 0/5] testing/next (rcutorture and misc tweaks) Alex Bennée
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=20200207113939.9247-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=cota@braap.org \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanb@linux.vnet.ibm.com \
--cc=stefanha@redhat.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).