From: Eduardo Habkost <ehabkost@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
dgilbert@redhat.com, mrezanin@redhat.com, peterx@redhat.com,
jsnow@redhat.com,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 2/3] block-jobs: Optionally unregister live block operations
Date: Wed, 30 Aug 2017 14:24:13 -0300 [thread overview]
Message-ID: <20170830172413.GA9720@localhost.localdomain> (raw)
In-Reply-To: <fc2539281a00353777c10f37dea6ccdb6aae4285.1504112256.git.jcody@redhat.com>
On Wed, Aug 30, 2017 at 01:01:41PM -0400, Jeff Cody wrote:
> From: Jeffrey Cody <jcody@redhat.com>
>
> If configured without live block operations enabled, unregister the
> live block operation commands.
>
> Signed-off-by: Jeff Cody <jcody@redhat.com>
> ---
> monitor.c | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/monitor.c b/monitor.c
> index e0f8801..de0a70e 100644
> --- a/monitor.c
> +++ b/monitor.c
> @@ -998,6 +998,22 @@ static void qmp_unregister_commands_hack(void)
> && !defined(TARGET_S390X)
> qmp_unregister_command(&qmp_commands, "query-cpu-definitions");
> #endif
> +#ifndef CONFIG_LIVE_BLOCK_OPS
> + qmp_unregister_command(&qmp_commands, "block-stream");
> + qmp_unregister_command(&qmp_commands, "block-commit");
> + qmp_unregister_command(&qmp_commands, "drive-mirror");
> + qmp_unregister_command(&qmp_commands, "blockdev-mirror");
> + qmp_unregister_command(&qmp_commands, "drive-backup");
> + qmp_unregister_command(&qmp_commands, "blockdev-backup");
> + qmp_unregister_command(&qmp_commands, "blockdev-snapshot");
> + qmp_unregister_command(&qmp_commands, "blockdev-snapshot-sync");
> + qmp_unregister_command(&qmp_commands, "block-job-set-speed");
> + qmp_unregister_command(&qmp_commands, "block-job-cancel");
> + qmp_unregister_command(&qmp_commands, "block-job-pause");
> + qmp_unregister_command(&qmp_commands, "block-job-resume");
> + qmp_unregister_command(&qmp_commands, "block-job-complete");
> + qmp_unregister_command(&qmp_commands, "query-block-jobs");
> +#endif
I suggest using the new mechanisms added by:
[PATCH 00/26] qapi: add #if pre-processor conditions to generated code
--
Eduardo
next prev parent reply other threads:[~2017-08-30 17:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 17:01 [Qemu-devel] [PATCH v2 0/3] Live block optional disable Jeff Cody
2017-08-30 17:01 ` [Qemu-devel] [PATCH v2 1/3] configure: Add option in configure to disable live block ops Jeff Cody
2017-08-30 17:01 ` [Qemu-devel] [PATCH v2 2/3] block-jobs: Optionally unregister live block operations Jeff Cody
2017-08-30 17:24 ` Eduardo Habkost [this message]
2017-08-30 19:23 ` Eric Blake
2017-08-31 6:45 ` Markus Armbruster
2017-09-06 13:00 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2017-09-06 15:02 ` Eduardo Habkost
2017-09-06 16:42 ` Eric Blake
2017-08-30 17:01 ` [Qemu-devel] [PATCH v2 3/3] hmp: Optionally disable live block operations in HMP monitor Jeff Cody
2017-09-05 14:01 ` Dr. David Alan Gilbert
2017-08-30 19:17 ` [Qemu-devel] [PATCH v2 0/3] Live block optional disable Eric Blake
2017-08-30 19:26 ` Eric Blake
2017-09-06 12:58 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
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=20170830172413.GA9720@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jcody@redhat.com \
--cc=jsnow@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mrezanin@redhat.com \
--cc=peterx@redhat.com \
--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 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).