From: Kevin Wolf <kwolf@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org, armbru@redhat.com,
eblake@redhat.com, devel@lists.libvirt.org, hreitz@redhat.com,
jsnow@redhat.com, pkrempa@redhat.com
Subject: Re: [PATCH v3 3/7] qapi: block-job-change: make copy-mode parameter optional
Date: Tue, 22 Oct 2024 14:35:12 +0200 [thread overview]
Message-ID: <ZxecANVZTYjhpeye@redhat.com> (raw)
In-Reply-To: <20241002140616.561652-4-vsementsov@yandex-team.ru>
Am 02.10.2024 um 16:06 hat Vladimir Sementsov-Ogievskiy geschrieben:
> We are going to add more parameters to change. We want to make possible
> to change only one or any subset of available options. So all the
> options should be optional.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
> Acked-by: Markus Armbruster <armbru@redhat.com>
This is different from blockdev-reopen, which requires repeating all
options (and can therefore reuse the type from blockdev-add). One of the
reasons why we made it like that is that we had some options for which
"option absent" was a meaningful value in itself, so it would have
become ambiguous if an absent option in blockdev-reopen should mean
"leave the existing value unchanged" or "unset the option".
Are we confident that this will never happen with job options? In case
of doubt, I would go for consistency with blockdev-reopen.
Either way, it would be good to document the reasoning for whatever
option we choose in the commit message.
Kevin
next prev parent reply other threads:[~2024-10-22 12:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 14:06 [PATCH v3 0/7] introduce job-change qmp command Vladimir Sementsov-Ogievskiy
2024-10-02 14:06 ` [PATCH v3 1/7] qapi: rename BlockJobChangeOptions to JobChangeOptions Vladimir Sementsov-Ogievskiy
2024-10-02 14:06 ` [PATCH v3 2/7] blockjob: block_job_change_locked(): check job type Vladimir Sementsov-Ogievskiy
2024-10-02 14:06 ` [PATCH v3 3/7] qapi: block-job-change: make copy-mode parameter optional Vladimir Sementsov-Ogievskiy
2024-10-22 12:35 ` Kevin Wolf [this message]
2024-10-29 11:32 ` Vladimir Sementsov-Ogievskiy
2024-10-02 14:06 ` [PATCH v3 4/7] blockjob: move change action implementation to job from block-job Vladimir Sementsov-Ogievskiy
2024-10-22 13:00 ` Kevin Wolf
2024-10-02 14:06 ` [PATCH v3 5/7] qapi: add job-change Vladimir Sementsov-Ogievskiy
2024-10-22 13:03 ` Kevin Wolf
2024-10-02 14:06 ` [PATCH v3 6/7] qapi/block-core: deprecate block-job-change Vladimir Sementsov-Ogievskiy
2024-11-07 7:37 ` Markus Armbruster
2024-10-02 14:06 ` [PATCH v3 7/7] iotests/mirror-change-copy-mode: switch to job-change command Vladimir Sementsov-Ogievskiy
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=ZxecANVZTYjhpeye@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=devel@lists.libvirt.org \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@yandex-team.ru \
/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).