From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@gmail.com, dietmar@proxmox.com,
pbonzini@redhat.com, Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH V4 3/5] block: package committing code in qmp_transaction()
Date: Thu, 2 May 2013 10:26:44 +0800 [thread overview]
Message-ID: <1367461606-7554-4-git-send-email-xiawenc@linux.vnet.ibm.com> (raw)
In-Reply-To: <1367461606-7554-1-git-send-email-xiawenc@linux.vnet.ibm.com>
The code is simply moved into a separate function.
Signed-off-by: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
---
blockdev.c | 19 ++++++++++++-------
1 files changed, 12 insertions(+), 7 deletions(-)
diff --git a/blockdev.c b/blockdev.c
index 06100d7..26bc78e 100644
--- a/blockdev.c
+++ b/blockdev.c
@@ -871,6 +871,17 @@ static void external_snapshot_prepare(BlockdevAction *action,
}
}
+static void external_snapshot_commit(BlkTransactionStates *states)
+{
+ /* This removes our old bs from the bdrv_states, and adds the new bs */
+ bdrv_append(states->new_bs, states->old_bs);
+ /* We don't need (or want) to use the transactional
+ * bdrv_reopen_multiple() across all the entries at once, because we
+ * don't want to abort all of them if one of them fails the reopen */
+ bdrv_reopen(states->new_bs, states->new_bs->open_flags & ~BDRV_O_RDWR,
+ NULL);
+}
+
/*
* 'Atomic' group snapshots. The snapshots are taken as a set, and if any fail
* then we do not pivot any of the devices in the group, and abandon the
@@ -916,13 +927,7 @@ void qmp_transaction(BlockdevActionList *dev_list, Error **errp)
/* Now we are going to do the actual pivot. Everything up to this point
* is reversible, but we are committed at this point */
QSIMPLEQ_FOREACH(states, &snap_bdrv_states, entry) {
- /* This removes our old bs from the bdrv_states, and adds the new bs */
- bdrv_append(states->new_bs, states->old_bs);
- /* We don't need (or want) to use the transactional
- * bdrv_reopen_multiple() across all the entries at once, because we
- * don't want to abort all of them if one of them fails the reopen */
- bdrv_reopen(states->new_bs, states->new_bs->open_flags & ~BDRV_O_RDWR,
- NULL);
+ external_snapshot_commit(states);
}
/* success */
--
1.7.1
next prev parent reply other threads:[~2013-05-02 2:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 2:26 [Qemu-devel] [PATCH V4 0/5] block: make qmp_transaction extendable Wenchao Xia
2013-05-02 2:26 ` [Qemu-devel] [PATCH V4 1/5] block: package preparation code in qmp_transaction() Wenchao Xia
2013-05-03 14:18 ` Eric Blake
2013-05-02 2:26 ` [Qemu-devel] [PATCH V4 2/5] block: move input parsing " Wenchao Xia
2013-05-02 2:26 ` Wenchao Xia [this message]
2013-05-03 14:21 ` [Qemu-devel] [PATCH V4 3/5] block: package committing " Eric Blake
2013-05-02 2:26 ` [Qemu-devel] [PATCH V4 4/5] block: package rollback " Wenchao Xia
2013-05-03 14:40 ` Eric Blake
2013-05-02 2:26 ` [Qemu-devel] [PATCH V4 5/5] block: make all steps in qmp_transaction() as callback Wenchao Xia
2013-05-03 14:46 ` Eric Blake
2013-05-06 2:00 ` Wenchao Xia
2013-05-03 8:46 ` [Qemu-devel] [PATCH V4 0/5] block: make qmp_transaction extendable Kevin Wolf
2013-05-03 11:17 ` Stefan Hajnoczi
2013-05-06 15:56 ` Luiz Capitulino
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=1367461606-7554-4-git-send-email-xiawenc@linux.vnet.ibm.com \
--to=xiawenc@linux.vnet.ibm.com \
--cc=dietmar@proxmox.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).