From: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH v3 0/2] Fix savevm/loadvm after postcopy migration
Date: Thu, 16 Nov 2017 20:35:25 -0200 [thread overview]
Message-ID: <20171116223527.4499-1-danielhb@linux.vnet.ibm.com> (raw)
v3:
- patch 1: added 'Reported-by' info in the commit msg. No code
changes were made.
- patch 2 *new*: a new qemu-iotest that verifies the behavior
fixed in patch1.
v2:
- added helper functions to simplify the code
Daniel Henrique Barboza (2):
migration/ram.c: do not set 'postcopy_running' in
POSTCOPY_INCOMING_END
tests/qemu-iotests: adding savevm/loadvm with postcopy flag test
migration/ram.c | 16 ++++++-
tests/qemu-iotests/198 | 110 +++++++++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/198.out | 20 +++++++++
tests/qemu-iotests/group | 1 +
4 files changed, 145 insertions(+), 2 deletions(-)
create mode 100755 tests/qemu-iotests/198
create mode 100644 tests/qemu-iotests/198.out
--
2.13.6
next reply other threads:[~2017-11-16 22:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 22:35 Daniel Henrique Barboza [this message]
2017-11-16 22:35 ` [Qemu-devel] [PATCH v3 1/2] migration/ram.c: do not set 'postcopy_running' in POSTCOPY_INCOMING_END Daniel Henrique Barboza
2017-11-16 22:35 ` [Qemu-devel] [PATCH v3 2/2] tests/qemu-iotests: adding savevm/loadvm with postcopy flag test Daniel Henrique Barboza
2017-11-17 13:24 ` Cleber Rosa
2017-11-17 13:41 ` Daniel Henrique Barboza
2017-12-01 20:13 ` Max Reitz
2017-12-03 20:13 ` Daniel Henrique Barboza
2017-12-04 14:50 ` Max Reitz
2017-12-04 15:01 ` Daniel Henrique Barboza
2017-12-04 15:06 ` Max Reitz
2017-12-04 15:15 ` Daniel Henrique Barboza
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=20171116223527.4499-1-danielhb@linux.vnet.ibm.com \
--to=danielhb@linux.vnet.ibm.com \
--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 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).