qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, den@openvz.org, vsementsov@virtuozzo.com,
	rkagan@virtuozzo.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/7] iotests: allow Valgrind checking all QEMU processes
Date: Mon, 10 Jun 2019 09:24:03 -0500	[thread overview]
Message-ID: <96a6fd48-9e84-1285-1932-3ce1736cd08c@redhat.com> (raw)
In-Reply-To: <1560105348-459129-2-git-send-email-andrey.shinkevich@virtuozzo.com>


[-- Attachment #1.1: Type: text/plain, Size: 1019 bytes --]

On 6/9/19 1:35 PM, Andrey Shinkevich wrote:
> With the '-valgrind' option, let all the QEMU processes be run under
> the Valgrind tool. The Valgrind own parameters may be set with its
> environment variable VALGRIND_OPTS, e.g.
> VALGRIND_OPTS="--leak-check=yes" ./check -qcow2 -valgrind <test#>

Let's spell this --valgrind; long options should prefer the use of --
(as in getopt_long), whether or not we also have a reason to support
-valgrind (as in getopt_long_only). Yes, qemu is an oddball in this
regards, but no need to make it worse.

> 
> Signed-off-by: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
> ---
>  tests/qemu-iotests/common.rc | 65 ++++++++++++++++++++++++++++++++------------
>  1 file changed, 48 insertions(+), 17 deletions(-)
> 
> diff --git a/tests/qemu-iotests/common.rc b/tests/qemu-iotests/common.rc
> index 93f8738..3caaca4 100644


-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-06-10 14:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-09 18:35 [Qemu-devel] [PATCH 0/7] Allow Valgrind checking all QEMU processes Andrey Shinkevich
2019-06-09 18:35 ` [Qemu-devel] [PATCH 1/7] iotests: allow " Andrey Shinkevich
2019-06-10 14:24   ` Eric Blake [this message]
2019-06-10 15:02     ` Andrey Shinkevich
2019-06-10 15:36       ` Eric Blake
2019-06-09 18:35 ` [Qemu-devel] [PATCH 2/7] iotests: amendment for benchmark output of 039 061 137 Andrey Shinkevich
2019-06-10  9:10   ` Daniel P. Berrangé
2019-06-10  9:31     ` Andrey Shinkevich
2019-06-09 18:35 ` [Qemu-devel] [PATCH 3/7] iotests: exclude killed processes from running under Valgrind Andrey Shinkevich
2019-06-09 18:35 ` [Qemu-devel] [PATCH 4/7] iotests: Valgrind fails to work with nonexistent directory Andrey Shinkevich
2019-06-09 18:35 ` [Qemu-devel] [PATCH 5/7] iotests: extended timeout under Valgrind Andrey Shinkevich
2019-06-09 18:35 ` [Qemu-devel] [PATCH 6/7] iotests: extend sleeping time " Andrey Shinkevich
2019-06-09 18:35 ` [Qemu-devel] [PATCH 7/7] iotests: amend QEMU NBD process synchronization 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=96a6fd48-9e84-1285-1932-3ce1736cd08c@redhat.com \
    --to=eblake@redhat.com \
    --cc=andrey.shinkevich@virtuozzo.com \
    --cc=den@openvz.org \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rkagan@virtuozzo.com \
    --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).