From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: dgilbert@redhat.com, lvivier@redhat.com, peterx@redhat.com,
eblake@redhat.com, armbru@redhat.com
Subject: [Qemu-devel] [PATCH v4 0/5] Remove old MigrationParams
Date: Tue, 16 May 2017 13:11:18 +0200 [thread overview]
Message-ID: <20170516111123.17692-1-quintela@redhat.com> (raw)
changes from v3
- patch 1 included again. We have a 'block' capability and a
'block_incremental' parameter
Make Dave happy: rename shared into incremental
Make Eric and Markus happy:
block: off -> no block migration, we don't care about
block_incremental value
block: on block_incremental: off -> no incremental block migration
block: on block_incremental: on -> incremental block migration
- Use visitors.
You ask if there is not a better way than hand coding a boolean parser.
QAPI people (a.k.a. Markus) answer to use a visitor.
Once there, I used it also for integers, not only booleans.
- Use -b/-i parameters. OK, I bit the bullet: You can't use
capabilities/parameters and -b/-i: it gives you one error If you use
-b/-i, capability parameter is cleanup after the migration ends (Who
would have guessed that there are cases where we call
migration_fd_error(), but not migration_fd_cleanup()
I think this should make Peter and Markus and Dave happy.
- Integrate migrate block compile time disabling
Well, it conflicted left and right, so I fixed it
Once there, I disable setting/getting block capability if it is disabled.
Please review.
[v3]
- Patch 1 included in pull request
- disable block_shared when we disable block_enable
- enable block_enabled when we enable block_shared
Please, review.
[v2]
- make migrate_block_set_* take a boolean
- disable block migration in colo to maintain semantics.
[v1]
Upon a time there were MigrationParms (only used for block migration)
and then MigrationParams used for everything else. This series:
- create migration capabilities for block parameters
- make the migrate command line parameters to use capabilities
- remove MigrationParams completely
Dr. David Alan Gilbert (1):
block migration: Allow compile time disable
Juan Quintela (4):
hmp: Use visitor api for hmp_migrate_set_parameter()
migration: Create block capability
migration: Remove use of old MigrationParams
migration: Remove old MigrationParams
configure | 11 +++++
hmp.c | 23 +++++++--
include/migration/block.h | 24 +++++++++
include/migration/migration.h | 18 +++----
include/migration/vmstate.h | 1 -
include/qemu/typedefs.h | 1 -
include/sysemu/sysemu.h | 3 +-
migration/Makefile.objs | 2 +-
migration/block.c | 17 +------
migration/colo.c | 6 +--
migration/migration.c | 112 +++++++++++++++++++++++++++++++++++++++---
migration/savevm.c | 24 ++++-----
qapi-schema.json | 14 ++++--
13 files changed, 194 insertions(+), 62 deletions(-)
--
2.9.3
next reply other threads:[~2017-05-16 11:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 11:11 Juan Quintela [this message]
2017-05-16 11:11 ` [Qemu-devel] [PATCH 1/5] hmp: Use visitor api for hmp_migrate_set_parameter() Juan Quintela
2017-05-16 12:29 ` Markus Armbruster
2017-05-16 11:11 ` [Qemu-devel] [PATCH 2/5] migration: Create block capability Juan Quintela
2017-05-16 14:20 ` Markus Armbruster
2017-05-16 14:34 ` Juan Quintela
2017-05-16 16:00 ` Markus Armbruster
2017-05-16 16:08 ` Eric Blake
2017-05-16 16:42 ` Markus Armbruster
2017-05-16 16:48 ` Eric Blake
2017-05-16 17:07 ` Markus Armbruster
2017-05-16 17:37 ` Juan Quintela
2017-05-16 11:11 ` [Qemu-devel] [PATCH 3/5] migration: Remove use of old MigrationParams Juan Quintela
2017-05-16 14:22 ` Markus Armbruster
2017-05-16 14:36 ` Juan Quintela
2017-05-16 15:35 ` Markus Armbruster
2017-05-16 11:11 ` [Qemu-devel] [PATCH 4/5] migration: Remove " Juan Quintela
2017-05-16 11:11 ` [Qemu-devel] [PATCH 5/5] block migration: Allow compile time disable Juan Quintela
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=20170516111123.17692-1-quintela@redhat.com \
--to=quintela@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=lvivier@redhat.com \
--cc=peterx@redhat.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).