From: Eric Blake <eblake@redhat.com>
To: Vladislav Yasevich <vyasevic@redhat.com>,
qemu-devel@nongnu.org, dgilbert@redhat.com, quintela@redhat.com
Cc: germano@redhat.com, lvivier@redhat.com, mst@redhat.com,
jasowang@redhat.com, armbru@redhat.com, kashyap@redhat.com,
jdenemar@redhat.com
Subject: Re: [Qemu-devel] [PATCH 06/12] qmp: Expose qemu_announce_self as a qmp command
Date: Fri, 26 May 2017 08:16:06 -0500 [thread overview]
Message-ID: <86965f80-c0a4-4033-a194-9a9e97c27a0f@redhat.com> (raw)
In-Reply-To: <1495649128-10529-7-git-send-email-vyasevic@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]
On 05/24/2017 01:05 PM, Vladislav Yasevich wrote:
> Add a qmp command that can trigger guest announcements.
>
> Based on work of Germano Veit Michel <germano@redhat.com>
>
> Signed-off-by: Vladislav Yasevich <vyasevic@redhat.com>
> ---
> migration/savevm.c | 14 ++++++++++++++
> qapi-schema.json | 19 +++++++++++++++++++
> 2 files changed, 33 insertions(+)
>
> +void qmp_announce_self(bool has_params, AnnounceParameters *params,
> + Error **errp)
> +{
> + AnnounceParameters announce_params;
> +
> + memcpy(&announce_params, qemu_get_announce_params(),
> + sizeof(announce_params));
Shallow copies of a QAPI type happen to work when the type is all scalar
(as AnnounceParameters currently is), but it's more robust to use
QAPI_CLONE() or QAPI_CLONE_MEMBERS() so that any future non-scalar
additions to the parameters type will be correctly copied without
introducing memory leaks or double frees.
Even this might be better:
AnnounceParameters announce_params = { 0 };
qemu_set_announce_parameters(&announce_params, qemu_get_announce_params());
> +
> + if (has_params)
> + qemu_set_announce_parameters(&announce_params, params);
> +
> + qemu_announce_self(&announce_params);
> +}
The QMP changes look okay. Do you have a testsuite covering the new QMP
command somewhere in the series?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-05-26 13:16 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 18:05 [Qemu-devel] [PATCH 00/12] self-announce updates Vladislav Yasevich
2017-05-24 18:05 ` [Qemu-devel] [PATCH 01/12] migration: Introduce announce parameters Vladislav Yasevich
2017-05-26 4:03 ` Jason Wang
2017-05-26 13:06 ` Vlad Yasevich
2017-05-30 18:57 ` Dr. David Alan Gilbert
2017-06-01 7:02 ` Jason Wang
2017-06-01 13:45 ` Vlad Yasevich
2017-06-01 14:02 ` Dr. David Alan Gilbert
2017-05-26 13:08 ` Eric Blake
2017-05-26 13:17 ` Vlad Yasevich
2017-05-30 9:58 ` Juan Quintela
2017-05-30 13:45 ` Vlad Yasevich
2017-05-30 19:08 ` Dr. David Alan Gilbert
2017-05-24 18:05 ` [Qemu-devel] [PATCH 02/12] migration: Introduce announcement timer Vladislav Yasevich
2017-05-26 4:13 ` Jason Wang
2017-05-30 10:00 ` Juan Quintela
2017-05-24 18:05 ` [Qemu-devel] [PATCH 03/12] migration: Switch to using " Vladislav Yasevich
2017-05-26 4:16 ` Jason Wang
2017-05-26 13:01 ` Vlad Yasevich
2017-05-30 10:10 ` Juan Quintela
2017-05-30 13:46 ` Vlad Yasevich
2017-05-30 19:19 ` Dr. David Alan Gilbert
2017-05-30 19:34 ` Vlad Yasevich
2017-05-24 18:05 ` [Qemu-devel] [PATCH 04/12] net: Add a network device specific self-announcement ability Vladislav Yasevich
2017-05-26 4:17 ` Jason Wang
2017-05-24 18:05 ` [Qemu-devel] [PATCH 05/12] virtio-net: Allow qemu_announce_self to trigger virtio announcements Vladislav Yasevich
2017-05-26 4:21 ` Jason Wang
2017-05-24 18:05 ` [Qemu-devel] [PATCH 06/12] qmp: Expose qemu_announce_self as a qmp command Vladislav Yasevich
2017-05-26 13:16 ` Eric Blake [this message]
2017-05-26 13:19 ` Vlad Yasevich
2017-05-30 10:11 ` Juan Quintela
2017-05-30 13:49 ` Vlad Yasevich
2017-05-30 14:24 ` Juan Quintela
2017-05-30 14:43 ` Vlad Yasevich
2017-05-30 14:14 ` Daniel P. Berrange
2017-05-30 15:01 ` Vlad Yasevich
2017-05-24 18:05 ` [Qemu-devel] [PATCH 07/12] migration: Allow for a limited number of announce timers Vladislav Yasevich
2017-05-30 10:13 ` Juan Quintela
2017-05-30 19:31 ` Dr. David Alan Gilbert
2017-05-24 18:05 ` [Qemu-devel] [PATCH 08/12] announce_timer: Add ability to reset an existing Vladislav Yasevich
2017-05-30 10:15 ` Juan Quintela
2017-05-30 19:35 ` Dr. David Alan Gilbert
2017-05-30 20:01 ` Vlad Yasevich
2017-05-24 18:05 ` [Qemu-devel] [PATCH 09/12] hmp: add announce paraters info/set Vladislav Yasevich
2017-05-30 10:18 ` Juan Quintela
2017-05-30 13:57 ` Vlad Yasevich
2017-05-24 18:05 ` [Qemu-devel] [PATCH 10/12] hmp: Add hmp_announce_self Vladislav Yasevich
2017-05-31 9:47 ` Dr. David Alan Gilbert
2017-05-24 18:05 ` [Qemu-devel] [PATCH 11/12] tests/test-hmp: Add announce parameter tests Vladislav Yasevich
2017-05-31 9:53 ` Dr. David Alan Gilbert
2017-05-24 18:05 ` [Qemu-devel] [PATCH 12/12] tests: Add a test for qemu self announcments Vladislav Yasevich
2017-05-24 18:19 ` [Qemu-devel] [PATCH 00/12] self-announce updates no-reply
2017-05-24 18:38 ` no-reply
2017-05-24 18:40 ` no-reply
2017-05-31 10:29 ` Dr. David Alan Gilbert
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=86965f80-c0a4-4033-a194-9a9e97c27a0f@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=germano@redhat.com \
--cc=jasowang@redhat.com \
--cc=jdenemar@redhat.com \
--cc=kashyap@redhat.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=vyasevic@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 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).