From: John Snow <jsnow@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-block@nongnu.org
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH 3/3] block: prohibit migration during transactions
Date: Fri, 2 Oct 2015 14:20:00 -0400 [thread overview]
Message-ID: <560ECAD0.8020005@redhat.com> (raw)
In-Reply-To: <560D7500.1000705@redhat.com>
On 10/01/2015 02:01 PM, Paolo Bonzini wrote:
>
>
> On 01/10/2015 18:34, John Snow wrote:
>> +
>> + error_setg(&blocker, "Block device(s) are in use by a Block Transaction");
>
> s/Block Transaction/transaction command/
>
> But how can migration start during a transaction?
>
Well, it definitely can't now ! :)
This is actually more for the other case: The migration starts, and we
want to prohibit snapshots and transactions during that period. Together
with the patch this depends on, we accomplish that.
The workflow of snapshot/transaction-before-migration isn't currently
possible.
>> + ret = migrate_add_blocker(blocker, errp);
>> + if (ret < 0) {
>> + goto cleanup_mig;
>> + }
>>
>> QSIMPLEQ_HEAD(snap_bdrv_states, BlkTransactionState) snap_bdrv_states;
>> QSIMPLEQ_INIT(&snap_bdrv_states);
>> @@ -1814,6 +1823,9 @@ exit:
>> }
>> g_free(state);
>> }
>> + cleanup_mig:
>> + migrate_del_blocker(blocker);
>> + error_free(blocker);
>
prev parent reply other threads:[~2015-10-02 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 16:34 [Qemu-devel] [PATCH 0/3] block: prohibit migrations during tasks John Snow
2015-10-01 16:34 ` [Qemu-devel] [PATCH 1/3] block: prohibit migration during BlockJobs John Snow
2015-10-01 18:03 ` Paolo Bonzini
2015-10-02 18:17 ` John Snow
2015-10-05 8:13 ` Kevin Wolf
2015-10-05 14:55 ` Paolo Bonzini
2015-10-01 16:34 ` [Qemu-devel] [PATCH 2/3] block/mirror: allow migration after sync John Snow
2015-10-01 16:34 ` [Qemu-devel] [PATCH 3/3] block: prohibit migration during transactions John Snow
2015-10-01 18:01 ` Paolo Bonzini
2015-10-02 18:20 ` John Snow [this message]
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=560ECAD0.8020005@redhat.com \
--to=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.