qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ian Main <imain@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, rjones@redhat.com,
	Ian Main <imain@redhat.com>,
	stefanha@redhat.com, pbonzini@redhat.com
Subject: [Qemu-devel] [PATCH V6 0/3] Implement sync modes for drive-backup.
Date: Mon, 22 Jul 2013 15:09:17 -0700	[thread overview]
Message-ID: <1374530960-22031-1-git-send-email-imain@redhat.com> (raw)

This patch adds sync modes on top of the work that Stefan Hajnoczi has done.

These patches apply on kevin/block.

Hopefully all is in order as this is my first QEMU patch.  Many thanks to
Stephan and Fam Zheng for their help.

V2:

- No longer poll, instead use qemu_coroutine_yield().
- Use bdrv_co_is_allocated().
- Much better SYNC_MODE_NONE test.

V3:

- A few style fixes.
- Better commit message explaining how TOP and NONE operate.
- Verified using checkpatch.pl.

V4:

- Add patch to use the source as a backing hd during backup.
- Add patch to default sync mode none to qcow2.

V5:

- Fix qcow2 patch.  Forgot to git add final version.

V6:

- Default to requiring 'format' when mode is absolute-paths.
- Removed one bad hunk that was misapplying.
- Fixed docs, examples and tests to match changes.
- Added tests for format bad/missing.
- Added bdrv_set_in_use() to target.
- Default to qcow2 patch not required.

Ian Main (3):
  Implement sync modes for drive-backup.
  Add tests for sync modes 'TOP' and 'NONE'
  Add backing drive while performing backup.

 block/backup.c                | 107 +++++++++++++++++++++++++++++------------
 blockdev.c                    |  36 +++++++++-----
 include/block/block_int.h     |   4 +-
 qapi-schema.json              |   4 +-
 qmp-commands.hx               |   2 +
 tests/qemu-iotests/055        | 108 +++++++++++++++++++++++++++++++++++++-----
 tests/qemu-iotests/055.out    |   4 +-
 tests/qemu-iotests/group      |   2 +-
 tests/qemu-iotests/iotests.py |   5 ++
 9 files changed, 211 insertions(+), 61 deletions(-)

-- 
1.8.1.4

             reply	other threads:[~2013-07-22 22:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22 22:09 Ian Main [this message]
2013-07-22 22:09 ` [Qemu-devel] [PATCH V6 1/3] Implement sync modes for drive-backup Ian Main
2013-07-24 10:55   ` Kevin Wolf
2013-07-24 17:57     ` Ian Main
2013-07-24 20:32     ` Eric Blake
2013-07-24 22:01       ` Ian Main
2013-07-25 11:23         ` Kevin Wolf
2013-07-25 14:36       ` Paolo Bonzini
2013-07-25 16:57         ` Eric Blake
2013-07-25 16:59           ` Paolo Bonzini
2013-07-22 22:09 ` [Qemu-devel] [PATCH V6 2/3] Add tests for sync modes 'TOP' and 'NONE' Ian Main
2013-07-24 11:19   ` Kevin Wolf
2013-07-24 18:02     ` Ian Main
2013-07-22 22:09 ` [Qemu-devel] [PATCH V6 3/3] Add backing drive while performing backup Ian Main
2013-07-24 11:28   ` Kevin Wolf
2013-07-23 11:53 ` [Qemu-devel] [PATCH V6 0/3] Implement sync modes for drive-backup Stefan Hajnoczi
2013-07-23 19:55   ` Ian Main
2013-07-24  0:55     ` Fam Zheng

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=1374530960-22031-1-git-send-email-imain@redhat.com \
    --to=imain@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.com \
    --cc=stefanha@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).