qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, mreitz@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/9] block/qcow2: Migration handoff fixes and cleanups
Date: Wed, 13 Jan 2016 17:37:07 +0100	[thread overview]
Message-ID: <1452703036-17999-1-git-send-email-kwolf@redhat.com> (raw)

This is the non-controversal part of the qcow2 locking series, which just makes
the state of images with respect to live migration clearer and fixes a few bugs
we have in the handoff procedure and with writing the qcow2 feature table.

Kevin Wolf (9):
  qcow2: Write feature table only for v3 images
  qcow2: Write full header on image creation
  block: Assert no write requests under BDRV_O_INCOMING
  block: Fix error path in bdrv_invalidate_cache()
  block: Rename BDRV_O_INCOMING to BDRV_O_INACTIVE
  block: Inactivate BDS when migration completes
  qcow2: Implement .bdrv_inactivate
  qcow2: Fix BDRV_O_INACTIVE handling in qcow2_invalidate_cache()
  qcow2: Make image inaccessible after failed qcow2_invalidate_cache()

 block.c                    |  42 +++++++++++++++--
 block/io.c                 |   2 +
 block/qcow2.c              | 110 +++++++++++++++++++++++++++------------------
 block/qed.c                |   4 +-
 include/block/block.h      |   3 +-
 include/block/block_int.h  |   1 +
 migration/migration.c      |   7 +++
 nbd.c                      |   2 +-
 qmp.c                      |  12 +++++
 tests/qemu-iotests/031.out |  17 +++----
 tests/qemu-iotests/036     |   2 +
 tests/qemu-iotests/036.out |   5 +++
 tests/qemu-iotests/061.out |  35 ++++++++-------
 13 files changed, 166 insertions(+), 76 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2016-01-13 16:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13 16:37 Kevin Wolf [this message]
2016-01-13 16:37 ` [Qemu-devel] [PATCH v2 1/9] qcow2: Write feature table only for v3 images Kevin Wolf
2016-01-13 16:37 ` [Qemu-devel] [PATCH v2 2/9] qcow2: Write full header on image creation Kevin Wolf
2016-01-13 16:37 ` [Qemu-devel] [PATCH v2 3/9] block: Assert no write requests under BDRV_O_INCOMING Kevin Wolf
2016-01-13 16:37 ` [Qemu-devel] [PATCH v2 4/9] block: Fix error path in bdrv_invalidate_cache() Kevin Wolf
2016-01-13 16:37 ` [Qemu-devel] [PATCH v2 5/9] block: Rename BDRV_O_INCOMING to BDRV_O_INACTIVE Kevin Wolf
2016-01-13 16:49   ` Eric Blake
2016-01-13 16:37 ` [Qemu-devel] [PATCH v2 6/9] block: Inactivate BDS when migration completes Kevin Wolf
2016-01-13 16:37 ` [Qemu-devel] [PATCH v2 7/9] qcow2: Implement .bdrv_inactivate Kevin Wolf
2016-01-13 16:37 ` [Qemu-devel] [PATCH v2 8/9] qcow2: Fix BDRV_O_INACTIVE handling in qcow2_invalidate_cache() Kevin Wolf
2016-01-13 16:37 ` [Qemu-devel] [PATCH v2 9/9] qcow2: Make image inaccessible after failed qcow2_invalidate_cache() Kevin Wolf
2016-01-19 16:55 ` [Qemu-devel] [PATCH v2 0/9] block/qcow2: Migration handoff fixes and cleanups Kevin Wolf

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=1452703036-17999-1-git-send-email-kwolf@redhat.com \
    --to=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).