From: Kevin Wolf <kwolf@redhat.com>
To: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
Cc: vsementsov@virtuozzo.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org, mreitz@redhat.com, den@openvz.org,
jsnow@redhat.com
Subject: Re: [Qemu-devel] [PATCH v7 0/6] Allow Valgrind checking all QEMU processes
Date: Tue, 3 Sep 2019 12:02:29 +0200 [thread overview]
Message-ID: <20190903100229.GD4582@localhost.localdomain> (raw)
In-Reply-To: <1567338786-586124-1-git-send-email-andrey.shinkevich@virtuozzo.com>
Am 01.09.2019 um 13:53 hat Andrey Shinkevich geschrieben:
> In the current implementation of the QEMU bash iotests, only qemu-io
> processes may be run under the Valgrind with the switch '-valgrind'.
> Let's allow the common.rc bash script running all other QEMU processes,
> such as qemu-kvm, qemu-img, qemu-ndb and qemu-vxhs, under the Valgrind.
Thanks, applied to the block branch.
Kevin
next prev parent reply other threads:[~2019-09-03 10:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-01 11:53 [Qemu-devel] [PATCH v7 0/6] Allow Valgrind checking all QEMU processes Andrey Shinkevich
2019-09-01 11:53 ` [Qemu-devel] [PATCH v7 1/6] iotests: allow " Andrey Shinkevich
2019-09-01 11:53 ` [Qemu-devel] [PATCH v7 2/6] iotests: exclude killed processes from running under Valgrind Andrey Shinkevich
2019-09-01 11:53 ` [Qemu-devel] [PATCH v7 3/6] iotests: Add casenotrun report to bash tests Andrey Shinkevich
2019-09-01 11:53 ` [Qemu-devel] [PATCH v7 4/6] iotests: Valgrind fails with nonexistent directory Andrey Shinkevich
2019-09-01 11:53 ` [Qemu-devel] [PATCH v7 5/6] iotests: extended timeout under Valgrind Andrey Shinkevich
2019-09-01 11:53 ` [Qemu-devel] [PATCH v7 6/6] iotests: extend sleeping time " Andrey Shinkevich
2019-09-03 10:02 ` Kevin Wolf [this message]
2019-09-03 10:38 ` [Qemu-devel] [PATCH v7 0/6] Allow Valgrind checking all QEMU processes Andrey Shinkevich
2019-09-03 14:22 ` Andrey Shinkevich
2019-09-03 14:28 ` Kevin Wolf
2019-09-03 16:36 ` Andrey Shinkevich
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=20190903100229.GD4582@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=andrey.shinkevich@virtuozzo.com \
--cc=den@openvz.org \
--cc=jsnow@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).