From: John Snow <jsnow@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: "kwolf >> Kevin Wolf" <kwolf@redhat.com>,
"mrei >> Max Reitz" <mreitz@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
stefan Hajnoczi <stefanha@redhat.com>,
"arm >> Markus Armbruster" <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 3/4] block: Add blockdev-backup to transaction
Date: Wed, 17 Dec 2014 16:20:07 -0500 [thread overview]
Message-ID: <5491F387.3030708@redhat.com> (raw)
In-Reply-To: <1418820703-17179-4-git-send-email-famz@redhat.com>
On 12/17/2014 07:51 AM, Fam Zheng wrote:
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> blockdev.c | 79 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> qapi-schema.json | 2 ++
> 2 files changed, 81 insertions(+)
>
> diff --git a/blockdev.c b/blockdev.c
> index dbbab1d..9f9ae88 100644
> --- a/blockdev.c
> +++ b/blockdev.c
> @@ -1559,6 +1559,79 @@ static void drive_backup_clean(BlkTransactionState *common)
> }
> }
>
> +typedef struct BlockdevBackupState {
> + BlkTransactionState common;
> + BlockDriverState *bs;
> + BlockJob *job;
> + AioContext *aio_context;
> +} BlockdevBackupState;
> +
> +static void blockdev_backup_prepare(BlkTransactionState *common, Error **errp)
> +{
> + BlockdevBackupState *state = DO_UPCAST(BlockdevBackupState, common, common);
> + BlockdevBackup *backup;
> + BlockDriverState *bs, *target;
> + Error *local_err = NULL;
> +
> + assert(common->action->kind == TRANSACTION_ACTION_KIND_BLOCKDEV_BACKUP);
> + backup = common->action->blockdev_backup;
> +
> + bs = bdrv_find(backup->device);
> + if (!bs) {
> + error_set(errp, QERR_DEVICE_NOT_FOUND, backup->device);
> + return;
> + }
> +
> + target = bdrv_find(backup->target);
> + if (!target) {
> + error_set(errp, QERR_DEVICE_NOT_FOUND, backup->target);
> + return;
> + }
> +
> + /* AioContext is released in .clean() */
> + state->aio_context = bdrv_get_aio_context(bs);
> + if (state->aio_context != bdrv_get_aio_context(target)) {
> + state->aio_context = NULL;
> + error_setg(errp, "Backup between two IO threads is not implemented");
> + return;
> + }
> + aio_context_acquire(state->aio_context);
> +
> + qmp_blockdev_backup(backup->device, backup->target,
> + backup->sync,
> + backup->has_speed, backup->speed,
> + backup->has_on_source_error, backup->on_source_error,
> + backup->has_on_target_error, backup->on_target_error,
> + &local_err);
> + if (local_err) {
> + error_propagate(errp, local_err);
> + return;
> + }
> +
> + state->bs = bdrv_find(backup->device);
Just some questions:
why not use 'bs' instead of calling the function again? Granted, it
should work a second time if it worked once.
> + state->job = state->bs->job;
Why stash both bs and bs->job? Can the BDS change what its job member
points to between .prepare() and .abort() ?
> +}
> +
> +static void blockdev_backup_abort(BlkTransactionState *common)
> +{
> + BlockdevBackupState *state = DO_UPCAST(BlockdevBackupState, common, common);
> + BlockDriverState *bs = state->bs;
> +
> + /* Only cancel if it's the job we started */
> + if (bs && bs->job && bs->job == state->job) {
> + block_job_cancel_sync(bs->job);
> + }
> +}
> +
> +static void blockdev_backup_clean(BlkTransactionState *common)
> +{
> + BlockdevBackupState *state = DO_UPCAST(BlockdevBackupState, common, common);
> +
> + if (state->aio_context) {
> + aio_context_release(state->aio_context);
> + }
> +}
> +
> static void abort_prepare(BlkTransactionState *common, Error **errp)
> {
> error_setg(errp, "Transaction aborted using Abort action");
> @@ -1582,6 +1655,12 @@ static const BdrvActionOps actions[] = {
> .abort = drive_backup_abort,
> .clean = drive_backup_clean,
> },
> + [TRANSACTION_ACTION_KIND_BLOCKDEV_BACKUP] = {
> + .instance_size = sizeof(BlockdevBackupState),
> + .prepare = blockdev_backup_prepare,
> + .abort = blockdev_backup_abort,
> + .clean = blockdev_backup_clean,
> + },
> [TRANSACTION_ACTION_KIND_ABORT] = {
> .instance_size = sizeof(BlkTransactionState),
> .prepare = abort_prepare,
> diff --git a/qapi-schema.json b/qapi-schema.json
> index 47d99cf..fbfc52f 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -1260,11 +1260,13 @@
> # drive-backup since 1.6
> # abort since 1.6
> # blockdev-snapshot-internal-sync since 1.7
> +# blockdev-backup since 2.3
> ##
> { 'union': 'TransactionAction',
> 'data': {
> 'blockdev-snapshot-sync': 'BlockdevSnapshot',
> 'drive-backup': 'DriveBackup',
> + 'blockdev-backup': 'BlockdevBackup',
> 'abort': 'Abort',
> 'blockdev-snapshot-internal-sync': 'BlockdevSnapshotInternal'
> } }
>
At any rate, regardless of the answers to my questions:
Reviewed-by: John Snow <jsnow@redhat.com>
next prev parent reply other threads:[~2014-12-17 21:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 12:51 [Qemu-devel] [PATCH v5 0/4] qmp: Add "blockdev-backup" Fam Zheng
2014-12-17 12:51 ` [Qemu-devel] [PATCH v5 1/4] qapi: Comment version info in TransactionAction Fam Zheng
2014-12-17 21:18 ` Eric Blake
2014-12-17 12:51 ` [Qemu-devel] [PATCH v5 2/4] qmp: Add command 'blockdev-backup' Fam Zheng
2014-12-17 20:53 ` John Snow
2014-12-18 10:22 ` Fam Zheng
2014-12-17 12:51 ` [Qemu-devel] [PATCH v5 3/4] block: Add blockdev-backup to transaction Fam Zheng
2014-12-17 21:20 ` John Snow [this message]
2014-12-18 10:31 ` Fam Zheng
2014-12-17 12:51 ` [Qemu-devel] [PATCH v5 4/4] qemu-iotests: Test blockdev-backup in 055 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=5491F387.3030708@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--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.