From: Eric Blake <eblake@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, armbru@redhat.com
Subject: Re: [PATCH 2/3] qom: move user_creatable_add_opts logic to vl.c and QAPIfy it
Date: Thu, 11 Mar 2021 12:37:08 -0600 [thread overview]
Message-ID: <d99739a6-93e1-1d44-653a-d9ff8f3ae677@redhat.com> (raw)
In-Reply-To: <20210311172459.990281-3-pbonzini@redhat.com>
On 3/11/21 11:24 AM, Paolo Bonzini wrote:
> Emulators are currently using OptsVisitor (via user_creatable_add_opts)
> to parse the -object command line option. This has one extra feature,
> compared to keyval, which is automatic conversion of integers to lists
> as well as support for lists as repeated options:
>
> -object memory-backend-ram,id=pc.ram,size=1048576000,host-nodes=0,policy=bind
>
> So we cannot replace OptsVisitor with keyval right now. Still, this
> patch moves the user_creatable_add_opts logic to vl.c since it is
> not needed anywhere else, and makes it go through user_creatable_add_qapi.
>
> In order to minimize code changes, the predicate still takes a string.
> This can be changed later to use the ObjectType QAPI enum directly.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> include/qom/object_interfaces.h | 50 ++--------------------
> qom/object_interfaces.c | 57 +------------------------
> softmmu/vl.c | 73 +++++++++++++++++++++++++--------
> 3 files changed, 60 insertions(+), 120 deletions(-)
>
> @@ -1684,6 +1691,48 @@ static int machine_set_property(void *opaque,
> return object_parse_property_opt(opaque, name, value, "type", errp);
> }
>
> +static void object_option_foreach_add(bool (*type_opt_predicate)(const char *), Error **errp)
Should this return a bool...
> +{
> + ObjectOption *opt, *next;
> +
> + QTAILQ_FOREACH_SAFE(opt, &object_opts, next, next) {
> + const char *type = ObjectType_str(opt->opts->qom_type);
> + if (type_opt_predicate(type)) {
> + if (!user_creatable_add_qapi(opt->opts, errp)) {
> + return;
with return false here,
> + }
> + qapi_free_ObjectOptions(opt->opts);
> + QTAILQ_REMOVE(&object_opts, opt, next);
> + }
> + }
and true here, to make it easier for callers to detect failure without
having to inspect errp?
> +}
> +
> +static void object_option_parse(const char *optarg)
> @@ -1815,9 +1860,7 @@ static void qemu_create_early_backends(void)
> exit(1);
> }
>
> - qemu_opts_foreach(qemu_find_opts("object"),
> - user_creatable_add_opts_foreach,
> - object_create_early, &error_fatal);
> + object_option_foreach_add(object_create_early, &error_fatal);
Then again, since the only callers pass error_fatal, we never reach the
early return.
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2021-03-11 18:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 17:24 [PATCH 0/3] vl: QAPIfy -object Paolo Bonzini
2021-03-11 17:24 ` [PATCH 1/3] tests: convert check-qom-proplist to keyval Paolo Bonzini
2021-03-11 18:29 ` Eric Blake
2021-03-12 10:21 ` Kevin Wolf
2021-03-11 17:24 ` [PATCH 2/3] qom: move user_creatable_add_opts logic to vl.c and QAPIfy it Paolo Bonzini
2021-03-11 18:37 ` Eric Blake [this message]
2021-03-12 10:18 ` Kevin Wolf
2021-03-13 9:35 ` Markus Armbruster
2021-03-13 9:40 ` Paolo Bonzini
2021-03-13 12:32 ` Markus Armbruster
2021-03-13 9:57 ` Markus Armbruster
2021-03-13 10:05 ` Paolo Bonzini
2021-03-11 17:24 ` [PATCH 3/3] vl: allow passing JSON to -object Paolo Bonzini
2021-03-11 18:38 ` Eric Blake
2021-03-12 10:21 ` Kevin Wolf
2021-03-13 9:41 ` Markus Armbruster
2021-03-11 17:39 ` [PATCH 0/3] vl: QAPIfy -object no-reply
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=d99739a6-93e1-1d44-653a-d9ff8f3ae677@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--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).