From: Stefan Hajnoczi <stefanha@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-block@nongnu.org, eblake@redhat.com, mreitz@redhat.com,
quintela@redhat.com, dgilbert@redhat.com, qemu-devel@nongnu.org,
lvivier@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/3] migration: Call blk_resume_after_migration() for postcopy
Date: Wed, 3 May 2017 14:33:24 +0100 [thread overview]
Message-ID: <20170503133324.GD14647@stefanha-x1.localdomain> (raw)
In-Reply-To: <1492614962-20946-1-git-send-email-kwolf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]
On Wed, Apr 19, 2017 at 05:15:59PM +0200, Kevin Wolf wrote:
> This fixes one of the bugs that made us disable the op blocker
> assertions for the 2.9 release.
>
> v2:
> - Filter HMP output not only for common.qemu users, but for all test
> cases that had an escape character in their reference output. This
> required matching also lines that don't begin with the (qemu) prompt
> because other messages (from stderr) are interleaved. [Eric]
> - Use bash $'\e' instead of sed \o for better portability [Eric]
> - Added driver=$IMGFMT to test 181 [Eric]
>
> Kevin Wolf (3):
> migration: Call blk_resume_after_migration() for postcopy
> qemu-iotests: Filter HMP readline escape characters
> qemu-iotests: Test postcopy migration
>
> migration/savevm.c | 8 +++
> tests/qemu-iotests/028.out | 2 +-
> tests/qemu-iotests/051 | 3 +-
> tests/qemu-iotests/051.out | 106 +++++++++++++++----------------
> tests/qemu-iotests/051.pc.out | 132 +++++++++++++++++++--------------------
> tests/qemu-iotests/068 | 4 +-
> tests/qemu-iotests/068.out | 6 +-
> tests/qemu-iotests/130.out | 4 +-
> tests/qemu-iotests/142 | 2 +-
> tests/qemu-iotests/142.out | 10 +--
> tests/qemu-iotests/145 | 3 +-
> tests/qemu-iotests/145.out | 2 +-
> tests/qemu-iotests/181 | 119 +++++++++++++++++++++++++++++++++++
> tests/qemu-iotests/181.out | 38 +++++++++++
> tests/qemu-iotests/common.filter | 7 +++
> tests/qemu-iotests/common.qemu | 4 +-
> tests/qemu-iotests/group | 1 +
> 17 files changed, 313 insertions(+), 138 deletions(-)
> create mode 100755 tests/qemu-iotests/181
> create mode 100644 tests/qemu-iotests/181.out
>
> --
> 1.8.3.1
>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2017-05-03 13:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 15:15 [Qemu-devel] [PATCH v2 0/3] migration: Call blk_resume_after_migration() for postcopy Kevin Wolf
2017-04-19 15:16 ` [Qemu-devel] [PATCH v2 1/3] " Kevin Wolf
2017-04-19 15:16 ` [Qemu-devel] [PATCH v2 2/3] qemu-iotests: Filter HMP readline escape characters Kevin Wolf
2017-04-19 15:31 ` Eric Blake
2017-04-19 15:16 ` [Qemu-devel] [PATCH v2 3/3] qemu-iotests: Test postcopy migration Kevin Wolf
2017-04-20 14:18 ` Fam Zheng
2017-04-20 14:39 ` Daniel P. Berrange
2017-05-03 13:33 ` Stefan Hajnoczi [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=20170503133324.GD14647@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=lvivier@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).