From: Max Reitz <mreitz@redhat.com>
To: John Snow <jsnow@redhat.com>, qemu-block@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, qemu-devel@nongnu.org,
armbru@redhat.com, vsementsov@parallels.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH 06/11] qmp: Add an implementation wrapper for qmp_drive_backup
Date: Tue, 17 Mar 2015 15:33:40 -0400 [thread overview]
Message-ID: <55088194.3030304@redhat.com> (raw)
In-Reply-To: <55087D91.1040809@redhat.com>
On 2015-03-17 at 15:16, John Snow wrote:
>
>
> On 03/17/2015 02:51 PM, Max Reitz wrote:
>> On 2015-03-04 at 23:15, John Snow wrote:
>>> We'd like to be able to specify the callback given to backup_start
>>> manually in the case of transactions, so split apart qmp_drive_backup
>>> into an implementation and a wrapper.
>>>
>>> Switch drive_backup_prepare to use the new wrapper, but don't overload
>>> the callback and closure yet.
>>>
>>> This is kind of gross, but we need to forward-declare the wrapper for
>>> the drive_backup transaction to be able to use. I could try moving
>>> the transaction blocks lower instead, but I wanted (for v1, at least)
>>> to minimize code movement so that the core changes were easiest to see.
>>>
>>> If anyone has suggestions on organization, please suggest them.
>>>
>>> Signed-off-by: John Snow <jsnow@redhat.com>
>>> ---
>>> blockdev.c | 77
>>> ++++++++++++++++++++++++++++++++++++++++++++++----------------
>>> 1 file changed, 58 insertions(+), 19 deletions(-)
>>>
>>> diff --git a/blockdev.c b/blockdev.c
>>> index 3153ee7..9e3b9e9 100644
>>> --- a/blockdev.c
>>> +++ b/blockdev.c
>>> @@ -1449,6 +1449,19 @@ void
>>> undo_transaction_wrapper(BlkTransactionState *common)
>>> blk_put_transaction_state(common);
>>> }
>>> +static void _drive_backup(const char *device, const char *target,
>>
>> Please don't use leading underscores. (Please.)
>>
>> Just call it do_drive_backup() or something.
>>
>> Other than that, I'm okay with a forward-declaration; if you want to
>> move it, but I'd be fine with moving the code, too.
>>
>> With _drive_backup() being called do_drive_backup():
>>
>> Reviewed-by: Max Reitz <mreitz@redhat.com>
>>
>
> Moving the code around might be better, it just makes for a much
> noisier patch. I made my decisions for v1 to keep code disturbed the
> least.
>
> Once more critiques roll in I will decide what to do.
>
> I'll replace with "do_drive_backup" unless you can think of a nice
> three-letter word to replace "do" so that I don't even have to perturb
> the alignment context ;)
Well, you're still prepending "static", so I think you won't get around
perturbing the context :-)
Max
>>> + bool has_format, const char *format,
>>> + enum MirrorSyncMode sync,
>>> + bool has_mode, enum NewImageMode mode,
>>> + bool has_speed, int64_t speed,
>>> + bool has_bitmap, const char *bitmap,
>>> + bool has_on_source_error,
>>> + BlockdevOnError on_source_error,
>>> + bool has_on_target_error,
>>> + BlockdevOnError on_target_error,
>>> + BlockCompletionFunc *cb, void *opaque,
>>> + Error **errp);
>>> +
>>> /* internal snapshot private data */
>>> typedef struct InternalSnapshotState {
>>> BlkTransactionState common;
>>> @@ -1768,15 +1781,16 @@ static void
>>> drive_backup_prepare(BlkTransactionState *common, Error **errp)
>>> state->aio_context = bdrv_get_aio_context(bs);
>>> aio_context_acquire(state->aio_context);
>>> - qmp_drive_backup(backup->device, backup->target,
>>> - backup->has_format, backup->format,
>>> - backup->sync,
>>> - backup->has_mode, backup->mode,
>>> - backup->has_speed, backup->speed,
>>> - backup->has_bitmap, backup->bitmap,
>>> - backup->has_on_source_error,
>>> backup->on_source_error,
>>> - backup->has_on_target_error,
>>> backup->on_target_error,
>>> - &local_err);
>>> + _drive_backup(backup->device, backup->target,
>>> + backup->has_format, backup->format,
>>> + backup->sync,
>>> + backup->has_mode, backup->mode,
>>> + backup->has_speed, backup->speed,
>>> + backup->has_bitmap, backup->bitmap,
>>> + backup->has_on_source_error,
>>> backup->on_source_error,
>>> + backup->has_on_target_error,
>>> backup->on_target_error,
>>> + NULL, NULL,
>>> + &local_err);
>>> if (local_err) {
>>> error_propagate(errp, local_err);
>>> return;
>>> @@ -2717,15 +2731,18 @@ out:
>>> aio_context_release(aio_context);
>>> }
>>> -void qmp_drive_backup(const char *device, const char *target,
>>> - bool has_format, const char *format,
>>> - enum MirrorSyncMode sync,
>>> - bool has_mode, enum NewImageMode mode,
>>> - bool has_speed, int64_t speed,
>>> - bool has_bitmap, const char *bitmap,
>>> - bool has_on_source_error, BlockdevOnError
>>> on_source_error,
>>> - bool has_on_target_error, BlockdevOnError
>>> on_target_error,
>>> - Error **errp)
>>> +static void _drive_backup(const char *device, const char *target,
>>> + bool has_format, const char *format,
>>> + enum MirrorSyncMode sync,
>>> + bool has_mode, enum NewImageMode mode,
>>> + bool has_speed, int64_t speed,
>>> + bool has_bitmap, const char *bitmap,
>>> + bool has_on_source_error,
>>> + BlockdevOnError on_source_error,
>>> + bool has_on_target_error,
>>> + BlockdevOnError on_target_error,
>>> + BlockCompletionFunc *cb, void *opaque,
>>> + Error **errp)
>>> {
>>> BlockDriverState *bs;
>>> BlockDriverState *target_bs;
>>> @@ -2837,9 +2854,15 @@ void qmp_drive_backup(const char *device, const
>>> char *target,
>>> }
>>> }
>>> + if (cb == NULL) {
>>> + cb = block_job_cb;
>>> + }
>>> + if (opaque == NULL) {
>>> + opaque = bs;
>>> + }
>>> backup_start(bs, target_bs, speed, sync, bmap,
>>> on_source_error, on_target_error,
>>> - block_job_cb, bs, &local_err);
>>> + cb, opaque, &local_err);
>>> if (local_err != NULL) {
>>> bdrv_unref(target_bs);
>>> error_propagate(errp, local_err);
>>> @@ -2850,6 +2873,22 @@ out:
>>> aio_context_release(aio_context);
>>> }
>>> +void qmp_drive_backup(const char *device, const char *target,
>>> + bool has_format, const char *format,
>>> + enum MirrorSyncMode sync,
>>> + bool has_mode, enum NewImageMode mode,
>>> + bool has_speed, int64_t speed,
>>> + bool has_bitmap, const char *bitmap,
>>> + bool has_on_source_error, BlockdevOnError
>>> on_source_error,
>>> + bool has_on_target_error, BlockdevOnError
>>> on_target_error,
>>> + Error **errp)
>>> +{
>>> + _drive_backup(device, target, has_format, format, sync, has_mode,
>>> mode,
>>> + has_speed, speed, has_bitmap, bitmap,
>>> has_on_source_error,
>>> + on_source_error, has_on_target_error,
>>> on_target_error,
>>> + NULL, NULL, errp);
>>> +}
>>> +
>>> BlockDeviceInfoList *qmp_query_named_block_nodes(Error **errp)
>>> {
>>> return bdrv_named_nodes_list();
>>
>
next prev parent reply other threads:[~2015-03-17 19:33 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 4:15 [Qemu-devel] [PATCH 00/11] block: incremental backup transactions John Snow
2015-03-05 4:15 ` [Qemu-devel] [PATCH 01/11] qapi: Add transaction support to block-dirty-bitmap operations John Snow
2015-03-17 15:14 ` Max Reitz
2015-03-05 4:15 ` [Qemu-devel] [PATCH 02/11] iotests: add transactional incremental backup test John Snow
2015-03-11 12:11 ` Kashyap Chamarthy
2015-03-11 14:25 ` John Snow
2015-03-11 16:18 ` Kashyap Chamarthy
2015-03-05 4:15 ` [Qemu-devel] [PATCH 03/11] block: add transactional callbacks feature John Snow
2015-03-17 17:47 ` Max Reitz
2015-03-17 18:04 ` John Snow
2015-03-17 18:18 ` Eric Blake
2015-03-17 18:23 ` John Snow
2015-03-17 18:19 ` Max Reitz
2015-03-05 4:15 ` [Qemu-devel] [PATCH 04/11] block: add refcount to Job object John Snow
2015-03-17 17:54 ` Max Reitz
2015-03-05 4:15 ` [Qemu-devel] [PATCH 05/11] block: add delayed bitmap successor cleanup John Snow
2015-03-17 18:44 ` Max Reitz
2015-03-17 19:12 ` John Snow
2015-03-17 22:46 ` John Snow
2015-03-18 13:03 ` Max Reitz
2015-03-05 4:15 ` [Qemu-devel] [PATCH 06/11] qmp: Add an implementation wrapper for qmp_drive_backup John Snow
2015-03-17 18:51 ` Max Reitz
2015-03-17 19:16 ` John Snow
2015-03-17 19:33 ` Max Reitz [this message]
2015-03-17 20:15 ` Eric Blake
2015-03-05 4:15 ` [Qemu-devel] [PATCH 07/11] block: drive_backup transaction callback support John Snow
2015-03-17 19:49 ` Max Reitz
2015-03-17 23:27 ` John Snow
2015-03-18 13:41 ` Max Reitz
2015-03-18 19:51 ` John Snow
2015-03-18 20:20 ` Max Reitz
2015-03-05 4:15 ` [Qemu-devel] [PATCH 08/11] iotests: add QMP event waiting queue John Snow
2015-03-17 20:04 ` Max Reitz
2015-03-05 4:15 ` [Qemu-devel] [PATCH 09/11] iotests: test 124 - drive object refactoring John Snow
2015-03-17 20:44 ` Max Reitz
2015-03-17 23:40 ` John Snow
2015-03-18 13:44 ` Max Reitz
2015-03-05 4:15 ` [Qemu-devel] [PATCH 10/11] iotests: 124 - backup_prepare refactoring John Snow
2015-03-17 20:50 ` Max Reitz
2015-03-17 23:44 ` John Snow
2015-03-05 4:15 ` [Qemu-devel] [PATCH 11/11] iotests: 124 - transactional failure test John Snow
2015-03-17 20:59 ` Max Reitz
2015-03-17 21:04 ` John Snow
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=55088194.3030304@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@parallels.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).