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>,
Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Cc: 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 v12 01/10] unblock backup operations in backing file
Date: Fri, 27 Nov 2015 14:14:47 +0800 [thread overview]
Message-ID: <1448604896-15378-2-git-send-email-wency@cn.fujitsu.com> (raw)
In-Reply-To: <1448604896-15378-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 bfc2be8..eaf479a 100644
--- a/block.c
+++ b/block.c
@@ -1275,6 +1275,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.5.0
next prev parent reply other threads:[~2015-11-27 6:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 6:14 [Qemu-devel] [Patch v12 00/10] Block replication for continuous checkpoints Wen Congyang
2015-11-27 6:14 ` Wen Congyang [this message]
2015-11-27 6:14 ` [Qemu-devel] [Patch v12 02/10] Store parent BDS in BdrvChild Wen Congyang
2015-11-27 6:14 ` [Qemu-devel] [Patch v12 03/10] Backup: clear all bitmap when doing block checkpoint Wen Congyang
2015-11-27 6:14 ` [Qemu-devel] [Patch v12 04/10] Allow creating backup jobs when opening BDS Wen Congyang
2015-11-27 6:14 ` [Qemu-devel] [Patch v12 05/10] docs: block replication's description Wen Congyang
2015-11-27 6:14 ` [Qemu-devel] [Patch v12 06/10] Add new block driver interfaces to control block replication Wen Congyang
2015-11-27 6:14 ` [Qemu-devel] [Patch v12 07/10] quorum: implement block driver interfaces for " Wen Congyang
2015-12-01 10:40 ` [Qemu-devel] [Patch v12 00/10] Block replication for continuous checkpoints Dr. David Alan Gilbert
2015-12-01 11:58 ` Hailiang Zhang
2015-12-02 1:03 ` Wen Congyang
2015-12-02 1:00 ` Wen Congyang
2015-12-02 6:51 ` 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=1448604896-15378-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).