From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: marcandre.lureau@redhat.com, tgolembi@redhat.com,
philmd@redhat.com, mdroth@linux.vnet.ibm.com
Subject: [PATCH 4/4] qga: Flatten simple union GuestDeviceId
Date: Wed, 21 Oct 2020 09:15:20 +0200 [thread overview]
Message-ID: <20201021071520.2168877-5-armbru@redhat.com> (raw)
In-Reply-To: <20201021071520.2168877-1-armbru@redhat.com>
Simple unions are simpler than flat unions in the schema, but more
complicated in C and on the QMP wire: there's extra indirection in C
and extra nesting on the wire, both pointless. They should be avoided
in new code.
GuestDeviceId was recently added for guest-get-devices. Convert it to
a flat union.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
---
qga/qapi-schema.json | 8 ++++++++
qga/commands-win32.c | 9 ++++-----
2 files changed, 12 insertions(+), 5 deletions(-)
diff --git a/qga/qapi-schema.json b/qga/qapi-schema.json
index c7bfb8bf6a..fe10631e4c 100644
--- a/qga/qapi-schema.json
+++ b/qga/qapi-schema.json
@@ -1256,6 +1256,12 @@
{ 'command': 'guest-get-osinfo',
'returns': 'GuestOSInfo' }
+##
+# @GuestDeviceType:
+##
+{ 'enum': 'GuestDeviceType',
+ 'data': [ 'pci' ] }
+
##
# @GuestDeviceIdPCI:
#
@@ -1276,6 +1282,8 @@
# Since: 5.2
##
{ 'union': 'GuestDeviceId',
+ 'base': { 'type': 'GuestDeviceType' },
+ 'discriminator': 'type',
'data': { 'pci': 'GuestDeviceIdPCI' } }
##
diff --git a/qga/commands-win32.c b/qga/commands-win32.c
index 1efe3ba076..0c33d48aaa 100644
--- a/qga/commands-win32.c
+++ b/qga/commands-win32.c
@@ -2400,16 +2400,15 @@ GuestDeviceInfoList *qmp_guest_get_devices(Error **errp)
}
skip = false;
- id = g_new0(GuestDeviceIdPCI, 1);
vendor_id = g_match_info_fetch(match_info, 1);
device_id = g_match_info_fetch(match_info, 2);
- id->vendor_id = g_ascii_strtoull(vendor_id, NULL, 16);
- id->device_id = g_ascii_strtoull(device_id, NULL, 16);
device->id = g_new0(GuestDeviceId, 1);
device->has_id = true;
- device->id->type = GUEST_DEVICE_ID_KIND_PCI;
- device->id->u.pci.data = id;
+ device->id->type = GUEST_DEVICE_TYPE_PCI;
+ id = &device->id->u.pci;
+ id->vendor_id = g_ascii_strtoull(vendor_id, NULL, 16);
+ id->device_id = g_ascii_strtoull(device_id, NULL, 16);
g_match_info_free(match_info);
break;
--
2.26.2
next prev parent reply other threads:[~2020-10-21 7:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 7:15 [PATCH 0/4] qga: Fix several guest-get-devices issues Markus Armbruster
2020-10-21 7:15 ` [PATCH 1/4] qga: Rename guest-get-devices return member 'address' to 'id' Markus Armbruster
2020-10-21 7:34 ` Philippe Mathieu-Daudé
2020-10-21 8:08 ` Markus Armbruster
2020-10-21 7:46 ` Marc-André Lureau
2020-10-21 7:15 ` [PATCH 2/4] qga: Use common time encoding for guest-get-devices 'driver-date' Markus Armbruster
2020-10-21 7:42 ` Marc-André Lureau
2020-10-21 7:15 ` [PATCH 3/4] qga-win: Fix guest-get-devices error API violations Markus Armbruster
2020-10-21 7:37 ` Marc-André Lureau
2020-10-21 7:39 ` Philippe Mathieu-Daudé
2020-10-21 7:15 ` Markus Armbruster [this message]
2020-10-21 7:35 ` [PATCH 4/4] qga: Flatten simple union GuestDeviceId Philippe Mathieu-Daudé
2020-10-21 7:36 ` Marc-André Lureau
2020-10-27 6:35 ` [PATCH 0/4] qga: Fix several guest-get-devices issues 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=20201021071520.2168877-5-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tgolembi@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).