Manos Pitsidianakis <el13...@mail.ntua.gr> writes:
> Is there a specific reason this patch wasn't finished? If I'm not
> wrong using non-scalar properties with -object is still not possible,
> yet would be a very useful feature for drivers with UserCreatable
> objects.
>
> Archive link since this is an old patch:
> https://lists.gnu.org/archive/html/qemu-devel/2016-09/msg08252.html
Yes, we want non-scalar properties with -object.
This series attempts to provide them by extending QemuOpts. The trouble
is that we've already pushed QemuOpts beyond its design limits, and this
series pushes it some more. We need to stop working around the design
limits of QemuOpts and start replacing them by something that serves our
current needs, as I explained in:
Subject: Re: [PATCH v14 00/19] QAPI/QOM work for non-scalar object
properties
Message-ID: <87vawnnjpi....@dusky.pond.sub.org>
https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg04895.html
I started the replacement work (merge commit 8746709). It provides
non-scalar properties for -blockdev. I stole Dan's PATCH 07 for it,
which became commit cbd8acf. See also the design thread
Subject: Non-flat command line option argument syntax
Message-ID: <87bmukmlau....@dusky.pond.sub.org>
https://lists.gnu.org/archive/html/qemu-devel/2017-02/msg00555.html
PATCH 02-06 have been merged separately (merge commit ede0cbe).
More work is needed to apply the solution for -blockdev to -object, and
I intend to work on it. A main difficulty is backwards compatibility to
all the ill-designed / accidental QemuOpts warts. We may have to accept
some incompatibility to make progress.
