From: Kevin Wolf <kwolf@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, "Markus Armbruster" <armbru@redhat.com>,
"Max Reitz" <mreitz@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v13 6/6] qom: support arbitrary non-scalar properties with -object
Date: Fri, 23 Sep 2016 13:12:22 +0200 [thread overview]
Message-ID: <20160923111222.GF5436@noname.redhat.com> (raw)
In-Reply-To: <20160923110737.GE29098@redhat.com>
Am 23.09.2016 um 13:07 hat Daniel P. Berrange geschrieben:
> On Fri, Sep 23, 2016 at 12:29:21PM +0200, Kevin Wolf wrote:
> > Am 19.09.2016 um 14:12 hat Daniel P. Berrange geschrieben:
> > > On Mon, Sep 19, 2016 at 12:58:30PM +0100, Daniel P. Berrange wrote:
> > > > Fortunately there is no existing object that implements
> > > > the UserCreatable interface that relies on the list
> > > > handling behaviour, so it is possible to swap out the
> > > > OptsVisitor for a different visitor implementation, so
> > > > -object supports non-scalar properties, thus leaving
> > > > other users of OptsVisitor unaffected.
> > >
> > > Urgh, I've just discovered that this is not in fact true.
> > >
> > > The 'memory-backend' object type uses uint16List which
> > > has the hacky list syntax
> > >
> > > -object memory-backend-ram,\
> > > id=ram-node2,size=24578621440,policy=bind,\
> > > host-nodes=1-2,host-nodes=5,host-nodes=7,
> > >
> > > So I'll need to figure out a way to preserve this syntax...
> >
> > If this turns out rather hard, would it make sense to merge just patches
> > 1 to 5 for now to enable -blockdev, which doesn't need this syntax? Then
> > you can add the magic list syntax as a follow-up together with the
> > -object work.
>
> I've got code to deal with it and will be sending a new series, probably
> on monday once i've done more testing.
Even better then. :-)
Kevin
prev parent reply other threads:[~2016-09-23 11:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 11:58 [Qemu-devel] [PATCH v13 0/6] QAPI/QOM work for non-scalar object properties Daniel P. Berrange
2016-09-19 11:58 ` [Qemu-devel] [PATCH v13 1/6] qdict: implement a qdict_crumple method for un-flattening a dict Daniel P. Berrange
2016-09-19 11:58 ` [Qemu-devel] [PATCH v13 2/6] option: make parse_option_bool/number non-static Daniel P. Berrange
2016-09-23 10:24 ` Kevin Wolf
2016-09-23 11:07 ` Daniel P. Berrange
2016-09-23 14:16 ` Eric Blake
2016-09-23 14:21 ` Daniel P. Berrange
2016-09-19 11:58 ` [Qemu-devel] [PATCH v13 3/6] qapi: rename QmpInputVisitor to QObjectInputVisitor Daniel P. Berrange
2016-09-19 11:58 ` [Qemu-devel] [PATCH v13 4/6] qapi: rename QmpOutputVisitor to QObjectOutputVisitor Daniel P. Berrange
2016-09-19 11:58 ` [Qemu-devel] [PATCH v13 5/6] qapi: add a QObjectInputVisitor that does string conversion Daniel P. Berrange
2016-09-19 11:58 ` [Qemu-devel] [PATCH v13 6/6] qom: support arbitrary non-scalar properties with -object Daniel P. Berrange
2016-09-19 12:12 ` Daniel P. Berrange
2016-09-19 12:19 ` Paolo Bonzini
2016-09-19 12:29 ` Daniel P. Berrange
2016-09-19 12:40 ` Paolo Bonzini
2016-09-23 10:29 ` Kevin Wolf
2016-09-23 11:07 ` Daniel P. Berrange
2016-09-23 11:12 ` Kevin Wolf [this message]
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=20160923111222.GF5436@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=mreitz@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).