qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Wen Congyang <wency@cn.fujitsu.com>
To: qemu devel <qemu-devel@nongnu.org>, Fam Zheng <famz@redhat.com>,
	Max Reitz <mreitz@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu block <qemu-block@nongnu.org>,
	Jiang Yunhong <yunhong.jiang@intel.com>,
	Dong Eddie <eddie.dong@intel.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	"Michael R. Hines" <mrhines@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH v11 01/12] unblock backup operations in backing file
Date: Tue, 3 Nov 2015 18:58:38 +0800	[thread overview]
Message-ID: <1446548329-17475-2-git-send-email-wency@cn.fujitsu.com> (raw)
In-Reply-To: <1446548329-17475-1-git-send-email-wency@cn.fujitsu.com>

Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
---
 block.c | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/block.c b/block.c
index 9a2ab68..1d6c115 100644
--- a/block.c
+++ b/block.c
@@ -1161,6 +1161,24 @@ void bdrv_set_backing_hd(BlockDriverState *bs, BlockDriverState *backing_hd)
     /* Otherwise we won't be able to commit due to check in bdrv_commit */
     bdrv_op_unblock(backing_hd, BLOCK_OP_TYPE_COMMIT_TARGET,
                     bs->backing_blocker);
+    /*
+     * We do backup in 3 ways:
+     * 1. drive backup
+     *    The target bs is new opened, and the source is top BDS
+     * 2. blockdev backup
+     *    Both the source and the target are top BDSes.
+     * 3. internal backup(used for block replication)
+     *    Both the source and the target are backing file
+     *
+     * In case 1, and 2, the backing file is neither the source nor
+     * the target.
+     * In case 3, we will block the top BDS, so there is only one block
+     * job for the top BDS and its backing chain.
+     */
+    bdrv_op_unblock(backing_hd, BLOCK_OP_TYPE_BACKUP_SOURCE,
+                    bs->backing_blocker);
+    bdrv_op_unblock(backing_hd, BLOCK_OP_TYPE_BACKUP_TARGET,
+                    bs->backing_blocker);
 out:
     bdrv_refresh_limits(bs, NULL);
 }
-- 
2.4.3

  reply	other threads:[~2015-11-03 11:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 10:58 [Qemu-devel] [PATCH v11 00/12] Block replication is a very important feature which is used for Wen Congyang
2015-11-03 10:58 ` Wen Congyang [this message]
2015-11-03 10:58 ` [Qemu-devel] [PATCH v11 02/12] Store parent BDS in BdrvChild Wen Congyang
2015-11-03 10:58 ` [Qemu-devel] [PATCH v11 03/12] allow writing to the backing file Wen Congyang
2015-11-03 10:58 ` [Qemu-devel] [PATCH v11 04/12] Backup: clear all bitmap when doing block checkpoint Wen Congyang
2015-11-03 10:58 ` [Qemu-devel] [PATCH v11 05/12] Allow creating backup jobs when opening BDS Wen Congyang
2015-11-03 10:58 ` [Qemu-devel] [PATCH v11 06/12] block: make bdrv_put_ref_bh_schedule() as a public API Wen Congyang
2015-11-03 10:58 ` [Qemu-devel] [PATCH v11 07/12] docs: block replication's description Wen Congyang
2015-11-03 10:58 ` [Qemu-devel] [PATCH v11 08/12] Add new block driver interfaces to control block replication Wen Congyang
2015-11-03 10:58 ` [Qemu-devel] [PATCH v11 09/12] quorum: implement block driver interfaces for " Wen Congyang
2015-11-03 10:58 ` [Qemu-devel] [PATCH v11 10/12] Implement new driver " Wen Congyang
2015-11-03 10:58 ` [Qemu-devel] [PATCH v11 11/12] support replication driver in blockdev-add Wen Congyang
2015-11-03 10:58 ` [Qemu-devel] [PATCH v11 12/12] Add a new API to start/stop replication, do checkpoint to all BDSes Wen Congyang
2015-11-12  9:03 ` [Qemu-devel] [PATCH v11 00/12] Block replication for continuous checkpoints Wen Congyang

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=1446548329-17475-2-git-send-email-wency@cn.fujitsu.com \
    --to=wency@cn.fujitsu.com \
    --cc=dgilbert@redhat.com \
    --cc=eddie.dong@intel.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=mrhines@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=yunhong.jiang@intel.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).