From: Eric Blake <eblake@redhat.com>
To: Max Reitz <mreitz@redhat.com>,
qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-2.5 1/1] blockdev: Mark {insert, remove}-medium experimental
Date: Fri, 11 Dec 2015 08:30:19 -0700 [thread overview]
Message-ID: <566AEC0B.1070009@redhat.com> (raw)
In-Reply-To: <1449847385-13986-2-git-send-email-mreitz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1912 bytes --]
On 12/11/2015 08:23 AM, Max Reitz wrote:
> While in the long term we want throttling to be its own block filter
> BDS, in the short term we want it to be part of the BB instead of a BDS;
> even in the long term we may want legacy throttling to be automatically
> tied to the BB.
>
> blockdev-insert-medium and blockdev-remove-medium do not retain
> throttling information in the BB (deliberately so). Therefore, using
> them means tying this information to a BDS, which would break the model
> described above. (The same applies to other flags such as
> detect_zeroes.) We probably want to move this information to the BB or
> its own filter BDS before blockdev-{insert,remove}-medium can be
> considered completely stable.
>
> Therefore, mark these functions experimental for the time being.
>
> Suggested-by: Markus Armbruster <armbru@redhat.com>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> Acked-by: Markus Armbruster <armbru@redhat.com>
> Acked-by: Kevin Wolf <kwolf@redhat.com>
> ---
Reviewed-by: Eric Blake <eblake@redhat.com>
> +++ b/qmp-commands.hx
> @@ -4203,13 +4203,13 @@ Example:
> EQMP
>
> {
> - .name = "blockdev-remove-medium",
> + .name = "x-blockdev-remove-medium",
> .args_type = "device:s",
> - .mhandler.cmd_new = qmp_marshal_blockdev_remove_medium,
> + .mhandler.cmd_new = qmp_marshal_x_blockdev_remove_medium,
> },
>
> SQMP
> -blockdev-remove-medium
> +x-blockdev-remove-medium
> ----------------------
Formatting nit, but not worth holding this up (as it is really our last
chance to get it in 2.5 before baking in something we'd be stuck with).
>
> SQMP
> -blockdev-insert-medium
> +x-blockdev-insert-medium
> ----------------------
Ditto.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-12-11 15:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 15:23 [Qemu-devel] [PATCH for-2.5 0/1] blockdev: Mark {insert, remove}-medium experimental Max Reitz
2015-12-11 15:23 ` [Qemu-devel] [PATCH for-2.5 1/1] " Max Reitz
2015-12-11 15:30 ` Eric Blake [this message]
2015-12-11 15:40 ` Peter Maydell
2015-12-11 15:43 ` Max Reitz
2015-12-11 16:19 ` Peter Maydell
2015-12-14 13:47 ` Markus Armbruster
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=566AEC0B.1070009@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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.