All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, qemu-block@nongnu.org, mst@redhat.com,
	jcody@redhat.com, quintela@redhat.com, armbru@redhat.com,
	groug@kaod.org, aneesh.kumar@linux.vnet.ibm.com,
	ashijeetacharya@gmail.com, pbonzini@redhat.com,
	amit.shah@redhat.com, marcandre.lureau@redhat.com,
	dgilbert@redhat.com, John Snow <jsnow@redhat.com>
Subject: [Qemu-devel] [PATCH v3 0/1] migration: disallow migrate_add_blocker during migration
Date: Fri,  9 Dec 2016 12:25:46 -0500	[thread overview]
Message-ID: <20161209172547.31550-1-jsnow@redhat.com> (raw)

As discussed on-list, this may be a necessary building block for
a run-time flag that prevents us from getting into any situations
where we configure a non-migratable QEMU.

I'd like extra attention to be paid to the virtio-gpu, vhost, and
ivshmem changes as I am not perfectly confident in those.

Sorry for the wide CC distributions.

V3: Rebased from a version I sent about a year ago.
    Changed the migration function names a bit,
    Changed new calls to migrate_add_blocker.

John Snow (1):
  migration: disallow migrate_add_blocker during migration

 block/qcow.c                  |  6 +++++-
 block/vdi.c                   |  6 +++++-
 block/vhdx.c                  | 24 ++++++++++++++----------
 block/vmdk.c                  |  7 ++++++-
 block/vpc.c                   | 10 +++++++---
 block/vvfat.c                 | 20 ++++++++++++--------
 hw/9pfs/9p.c                  | 16 ++++++++++++----
 hw/display/virtio-gpu.c       | 29 ++++++++++++++++-------------
 hw/misc/ivshmem.c             | 11 +++++++----
 hw/scsi/vhost-scsi.c          | 25 +++++++++++++++++++------
 hw/virtio/vhost.c             |  8 +++++++-
 include/migration/migration.h |  6 +++++-
 migration/migration.c         | 35 +++++++++++++++++++++++++++++++++--
 stubs/migr-blocker.c          |  3 ++-
 target-i386/kvm.c             | 16 +++++++++++++---
 15 files changed, 163 insertions(+), 59 deletions(-)

-- 
2.9.3

             reply	other threads:[~2016-12-09 17:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-09 17:25 John Snow [this message]
2016-12-09 17:25 ` [Qemu-devel] [PATCH v3 1/1] migration: disallow migrate_add_blocker during migration John Snow
2016-12-09 17:39   ` Dr. David Alan Gilbert
2016-12-09 21:10     ` John Snow
2016-12-12 10:52   ` Greg Kurz
2016-12-12 11:02     ` Dr. David Alan Gilbert
2016-12-12 14:56       ` Greg Kurz
2016-12-09 17:50 ` [Qemu-devel] [PATCH v3 0/1] " no-reply

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=20161209172547.31550-1-jsnow@redhat.com \
    --to=jsnow@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=armbru@redhat.com \
    --cc=ashijeetacharya@gmail.com \
    --cc=dgilbert@redhat.com \
    --cc=groug@kaod.org \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@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 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.