qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] RFC: -object vs -chardev creation order
Date: Wed, 18 Mar 2015 08:32:05 +0100	[thread overview]
Message-ID: <550929F5.5020500@redhat.com> (raw)
In-Reply-To: <20150317190836.GP6540@redhat.com>



On 17/03/2015 20:08, Daniel P. Berrange wrote:
> A third option is to not process -object args in one go, instead process
> each type of object at a time. eg we'd first create all the
> -object tls-credential instances, then create the -chardev instances,
> then create the -object rng-egd instances. This is probably the least
> amount of work in short term, but not all that scalable, unless we do
> a catch-all default case, so we only need code up hacks for a few
> particular object types.
> 
> Thus my gut feeling is to do option 3, but I'd like other opinions before
> embarking on this....

Yes, for now it is the best.

Another idea is to build objects lazily.  This requires adding a
"missing property" interface and making /objects implement it.  We can
think about it later.

Paolo

  reply	other threads:[~2015-03-18  7:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 19:08 [Qemu-devel] RFC: -object vs -chardev creation order Daniel P. Berrange
2015-03-18  7:32 ` Paolo Bonzini [this message]
2015-03-18  9:43 ` Markus Armbruster
2015-03-18  9:59   ` Daniel P. Berrange

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=550929F5.5020500@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=berrange@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).