From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Huth <thuth@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: [PATCH v3 0/5] Fix multifd + cancel + multifd
Date: Thu, 16 Jan 2020 16:46:11 +0100 [thread overview]
Message-ID: <20200116154616.11569-1-quintela@redhat.com> (raw)
Hi
In the v3 series:
- Add back the ->shutdown fix
Dave found the problem, we need to setup an error if we do shutdown.
- Make iotests to work back (we need to setup ->active for savevm)
- So postcopy/recovery is fixed again.
Please review, if there are not outstanding issues, I plan to push it.
Thanks, Juan
In the v2 series:
- get the multifd test patch
- drop the ->shutdown fix
it break postcopy recovery test. Still trying to determine if the
problem is inside the recover test or the recover code.
- upgrade the migrate_cancel test
Please review.
[v1]
This series:
- create a test that does:
launch multifd on target
migrate to target
cancel on source
create another target
migrate again
- And fixes the cases that made it fail:
* Make sure that we don't try ever IO after shutdown/error
Please, review.
Juan Quintela (5):
multifd: Make sure that we don't do any IO after an error
migration: Create MigrationState active field
migration: Don't wait in semaphore for thread we know has finished
qemu-file: Don't do IO after shutdown
migration-test: Make sure that multifd and cancel works
migration/migration.c | 5 ++
migration/migration.h | 5 ++
migration/qemu-file.c | 22 ++++++-
migration/ram.c | 28 ++++++---
migration/savevm.c | 2 +
tests/qtest/migration-test.c | 112 ++++++++++++++++++++++++++++++++++-
6 files changed, 163 insertions(+), 11 deletions(-)
--
2.24.1
next reply other threads:[~2020-01-16 15:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 15:46 Juan Quintela [this message]
2020-01-16 15:46 ` [PATCH v3 1/5] multifd: Make sure that we don't do any IO after an error Juan Quintela
2020-01-16 18:20 ` Dr. David Alan Gilbert
2020-01-16 15:46 ` [PATCH v3 2/5] migration: Create MigrationState active field Juan Quintela
2020-01-17 16:26 ` Dr. David Alan Gilbert
2020-01-17 18:35 ` Juan Quintela
2020-01-21 11:08 ` Juan Quintela
2020-01-16 15:46 ` [PATCH v3 3/5] migration: Don't wait in semaphore for thread we know has finished Juan Quintela
2020-01-17 16:45 ` Dr. David Alan Gilbert
2020-01-21 11:10 ` Juan Quintela
2020-01-16 15:46 ` [PATCH v3 4/5] qemu-file: Don't do IO after shutdown Juan Quintela
2020-01-16 15:46 ` [PATCH v3 5/5] migration-test: Make sure that multifd and cancel works Juan Quintela
2020-01-16 15:59 ` Thomas Huth
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=20200116154616.11569-1-quintela@redhat.com \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).