From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: qemu-devel@nongnu.org
Cc: "Laurent Vivier" <lvivier@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Alexander Bulekov" <alxndr@bu.edu>,
"Bandan Das" <bsd@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: [PATCH v2 0/1] tests/qtest/fuzz: Avoid QTest serialization
Date: Thu, 28 May 2020 18:53:02 +0200 [thread overview]
Message-ID: <20200528165303.1877-1-f4bug@amsat.org> (raw)
Since v1:
- update virtio tests after talking with Alex & Stefan.
Alex, from here you can test the getenv("QTEST_LOG") trick.
Regards,
Phil.
Philippe Mathieu-Daudé (1):
tests/qtest/fuzz: Add faster virtio tests
tests/qtest/fuzz/virtio_net_fuzz.c | 42 ++++++++++++++++++++---
tests/qtest/fuzz/virtio_scsi_fuzz.c | 53 +++++++++++++++++++++++++----
2 files changed, 84 insertions(+), 11 deletions(-)
--
2.21.3
next reply other threads:[~2020-05-28 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 16:53 Philippe Mathieu-Daudé [this message]
2020-05-28 16:53 ` [PATCH v2 1/1] tests/qtest/fuzz: Add faster virtio tests Philippe Mathieu-Daudé
2020-05-29 5:19 ` Alexander Bulekov
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=20200528165303.1877-1-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=alxndr@bu.edu \
--cc=bsd@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@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).