From: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, vsementsov@virtuozzo.com, mreitz@redhat.com,
andrey.shinkevich@virtuozzo.com, den@openvz.org,
jsnow@redhat.com
Subject: [Qemu-devel] [PATCH v6 0/6] Allow Valgrind checking all QEMU processes
Date: Mon, 26 Aug 2019 18:50:22 +0300 [thread overview]
Message-ID: <1566834628-485525-1-git-send-email-andrey.shinkevich@virtuozzo.com> (raw)
In the current implementation of the QEMU bash iotests, only qemu-io
processes may be run under the Valgrind, which is a useful tool for
finding memory usage issues. Let's allow the common.rc bash script
runing all the QEMU processes, such as qemu-kvm, qemu-img, qemu-ndb
and qemu-vxhs, under the Valgrind tool.
v6:
01: The possibility was added for a user to exclude particular processes
from running under the Valgrind to speed up the test run (suggested
by John).
02: The shim function _NO_VALGRIND() was introduced as a workaround for
the Valgrind bug that hangs QEMU killed process (suggested by John).
03: The comments were amended in the commit messages and common.rc file.
Discussed in the email threads with the message IDs:
<1563553816-148827-1-git-send-email-andrey.shinkevich@virtuozzo.com>
<1560276131-683243-1-git-send-email-andrey.shinkevich@virtuozzo.com>
Andrey Shinkevich (6):
iotests: allow Valgrind checking all QEMU processes
iotests: exclude killed processes from running under Valgrind
iotests: Add casenotrun report to bash tests
iotests: Valgrind fails with nonexistent directory
iotests: extended timeout under Valgrind
iotests: extend sleeping time under Valgrind
tests/qemu-iotests/028 | 6 ++-
tests/qemu-iotests/039 | 5 ++
tests/qemu-iotests/039.out | 30 ++---------
tests/qemu-iotests/051 | 4 ++
tests/qemu-iotests/061 | 2 +
tests/qemu-iotests/061.out | 12 +----
tests/qemu-iotests/137 | 1 +
tests/qemu-iotests/137.out | 6 +--
tests/qemu-iotests/183 | 9 +++-
tests/qemu-iotests/192 | 6 ++-
tests/qemu-iotests/247 | 6 ++-
tests/qemu-iotests/common.rc | 124 ++++++++++++++++++++++++++++++++++++-------
12 files changed, 149 insertions(+), 62 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-08-26 15:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 15:50 Andrey Shinkevich [this message]
2019-08-26 15:50 ` [Qemu-devel] [PATCH v6 1/6] iotests: allow Valgrind checking all QEMU processes Andrey Shinkevich
2019-08-28 22:58 ` John Snow
2019-08-29 0:30 ` Eric Blake
2019-08-29 10:50 ` Andrey Shinkevich
2019-08-29 17:33 ` John Snow
2019-08-26 15:50 ` [Qemu-devel] [PATCH v6 2/6] iotests: exclude killed processes from running under Valgrind Andrey Shinkevich
2019-08-28 23:00 ` John Snow
2019-08-26 15:50 ` [Qemu-devel] [PATCH v6 3/6] iotests: Add casenotrun report to bash tests Andrey Shinkevich
2019-08-26 15:50 ` [Qemu-devel] [PATCH v6 4/6] iotests: Valgrind fails with nonexistent directory Andrey Shinkevich
2019-08-26 15:50 ` [Qemu-devel] [PATCH v6 5/6] iotests: extended timeout under Valgrind Andrey Shinkevich
2019-08-26 15:50 ` [Qemu-devel] [PATCH v6 6/6] iotests: extend sleeping time " Andrey Shinkevich
2019-08-28 23:02 ` John Snow
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=1566834628-485525-1-git-send-email-andrey.shinkevich@virtuozzo.com \
--to=andrey.shinkevich@virtuozzo.com \
--cc=den@openvz.org \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).