From: Max Reitz <mreitz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/3] iotests: Test migration with all kinds of filter nodes
Date: Thu, 1 Aug 2019 20:50:23 +0200 [thread overview]
Message-ID: <c38a8d8d-2c86-dd77-be4e-543542ae41ae@redhat.com> (raw)
In-Reply-To: <20190801151744.798-4-kwolf@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 802 bytes --]
On 01.08.19 17:17, Kevin Wolf wrote:
> This test case is motivated by commit 2b23f28639 ('block/copy-on-read:
> Fix permissions for inactive node'). Instead of just testing
> copy-on-read on migration, let's stack all sorts of filter nodes on top
> of each other and try if the resulting VM can still migrate
> successfully. For good measure, put everything into an iothread, because
> why not?
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> tests/qemu-iotests/262 | 84 ++++++++++++++++++++++++++++++++++++++
> tests/qemu-iotests/262.out | 17 ++++++++
> tests/qemu-iotests/group | 1 +
> 3 files changed, 102 insertions(+)
> create mode 100755 tests/qemu-iotests/262
> create mode 100644 tests/qemu-iotests/262.out
Reviewed-by: Max Reitz <mreitz@redhat.com>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-08-01 18:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 15:17 [Qemu-devel] [PATCH 0/3] iotests: Test migration with filter nodes Kevin Wolf
2019-08-01 15:17 ` [Qemu-devel] [PATCH 1/3] iotests: Move migration helpers to iotests.py Kevin Wolf
2019-08-01 17:44 ` Max Reitz
2019-08-01 15:17 ` [Qemu-devel] [PATCH 2/3] iotests: Enable -d for Python non-unittest tests Kevin Wolf
2019-08-01 17:57 ` Max Reitz
2019-08-02 14:07 ` Kevin Wolf
2019-08-05 22:19 ` John Snow
2019-08-06 9:51 ` Kevin Wolf
2019-08-06 13:09 ` John Snow
2019-08-01 15:17 ` [Qemu-devel] [PATCH 3/3] iotests: Test migration with all kinds of filter nodes Kevin Wolf
2019-08-01 18:50 ` Max Reitz [this message]
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=c38a8d8d-2c86-dd77-be4e-543542ae41ae@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.