From: "Andreas Färber" <afaerber@suse.de>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 3/7] qom: create objects in two phases
Date: Fri, 08 May 2015 16:37:21 +0200 [thread overview]
Message-ID: <554CCA21.8000100@suse.de> (raw)
In-Reply-To: <1430476206-26034-4-git-send-email-berrange@redhat.com>
Hi,
Can we *please* find a better subject for this? To me, creating QOM
objects in two phases is about instance_init vs. realize, and thus I was
pretty upset that Paolo dared to apply this without asking me first.
Am 01.05.2015 um 12:30 schrieb Daniel P. Berrange:
> Some types of object must be created before chardevs, other types of
> object must be created after chardevs. As such there is no option but
> to create objects in two phases.
>
> This takes the decision to create as many object types as possible
> in the first phase, and only delay those which have a dependency on
> the chardevs. Hopefully the set which need delaying will remain
> small.
>
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
> vl.c | 40 +++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 39 insertions(+), 1 deletion(-)
>
> diff --git a/vl.c b/vl.c
> index 74c2681..ee2f70a 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -2591,6 +2591,33 @@ static int machine_set_property(const char *name, const char *value,
> return 0;
> }
>
> +
> +/**
Accidental documentation comment?
> + * Initial object creation happens before all other
> + * QEMU data types are created. The majority of objects
> + * can be created at this point. The rng-egd object
> + * cannot be created here, as it depends on the chardev
> + * already existing.
> + */
> +static bool object_create_initial(const char *type)
> +{
> + if (g_str_equal(type, "rng-egd")) {
> + return false;
> + }
> + return true;
> +}
> +
> +
> +/**
Ditto?
> + * The remainder of object creation happens after the
> + * creation of chardev, fsdev and device data types.
> + */
> +static bool object_create_delayed(const char *type)
> +{
> + return !object_create_initial(type);
> +}
> +
> +
> static int object_create(QemuOpts *opts, void *opaque)
> {
> Error *err = NULL;
> @@ -2599,6 +2626,7 @@ static int object_create(QemuOpts *opts, void *opaque)
> void *dummy = NULL;
> OptsVisitor *ov;
> QDict *pdict;
> + bool (*type_predicate)(const char *) = opaque;
>
> ov = opts_visitor_new(opts);
> pdict = qemu_opts_to_qdict(opts, NULL);
> @@ -2613,6 +2641,9 @@ static int object_create(QemuOpts *opts, void *opaque)
> if (err) {
> goto out;
> }
> + if (!type_predicate(type)) {
> + goto out;
> + }
>
> qdict_del(pdict, "id");
> visit_type_str(opts_get_visitor(ov), &id, "id", &err);
> @@ -4008,6 +4039,12 @@ int main(int argc, char **argv, char **envp)
>
> socket_init();
>
> + if (qemu_opts_foreach(qemu_find_opts("object"),
> + object_create,
> + object_create_initial, 0) != 0) {
> + exit(1);
> + }
> +
> if (qemu_opts_foreach(qemu_find_opts("chardev"), chardev_init_func, NULL, 1) != 0)
> exit(1);
> #ifdef CONFIG_VIRTFS
> @@ -4027,7 +4064,8 @@ int main(int argc, char **argv, char **envp)
> }
>
> if (qemu_opts_foreach(qemu_find_opts("object"),
> - object_create, NULL, 0) != 0) {
> + object_create,
> + object_create_delayed, 0) != 0) {
> exit(1);
> }
>
Otherwise looks okay and there's a pattern emerging of "not qom:".
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-05-08 14:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 10:29 [Qemu-devel] [PATCH v3 0/7] qom: misc fixes & enhancements to support TLS work Daniel P. Berrange
2015-05-01 10:30 ` [Qemu-devel] [PATCH v3 1/7] qom: fix typename of 'policy' enum property in hostmem obj Daniel P. Berrange
2015-05-08 14:28 ` Andreas Färber
2015-05-01 10:30 ` [Qemu-devel] [PATCH v3 2/7] qom: document user creatable object types in help text Daniel P. Berrange
2015-05-08 14:31 ` Andreas Färber
2015-05-01 10:30 ` [Qemu-devel] [PATCH v3 3/7] qom: create objects in two phases Daniel P. Berrange
2015-05-08 14:37 ` Andreas Färber [this message]
2015-05-08 14:40 ` Paolo Bonzini
2015-05-12 16:55 ` Daniel P. Berrange
2015-05-01 10:30 ` [Qemu-devel] [PATCH v3 4/7] qom: add object_new_propv / object_new_proplist constructors Daniel P. Berrange
2015-05-08 17:10 ` Andreas Färber
2015-05-08 17:18 ` Paolo Bonzini
2015-05-08 17:22 ` Andreas Färber
2015-05-08 20:16 ` Eric Blake
2015-05-12 16:49 ` Daniel P. Berrange
2015-05-01 10:30 ` [Qemu-devel] [PATCH v3 5/7] qom: make enum string tables const-correct Daniel P. Berrange
2015-05-08 17:19 ` Andreas Färber
2015-05-01 10:30 ` [Qemu-devel] [PATCH v3 6/7] qom: add a object_property_add_enum helper method Daniel P. Berrange
2015-05-08 17:45 ` Andreas Färber
2015-05-12 16:53 ` Daniel P. Berrange
2015-05-01 10:30 ` [Qemu-devel] [PATCH v3 7/7] qom: don't pass string table to object_get_enum method Daniel P. Berrange
2015-05-08 17:54 ` Andreas Färber
2015-05-12 16:54 ` Daniel P. Berrange
2015-05-05 10:33 ` [Qemu-devel] [PATCH v3 0/7] qom: misc fixes & enhancements to support TLS work Paolo Bonzini
2015-05-05 15:37 ` Andreas Färber
2015-05-08 12:31 ` Paolo Bonzini
2015-05-08 12:34 ` Andreas Färber
2015-05-08 14:20 ` Paolo Bonzini
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=554CCA21.8000100@suse.de \
--to=afaerber@suse.de \
--cc=berrange@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).