From: Markus Armbruster <armbru@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
qemu-devel@nongnu.org, "Markus Armbruster" <armbru@redhat.com>,
"William Tsai" <williamtsai1111@gmail.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Eduardo Habkost" <eduardo@habkost.net>
Subject: Re: [PATCH 0/1] qom: fix setting of qdev array properties
Date: Thu, 07 Sep 2023 11:33:24 +0200 [thread overview]
Message-ID: <87edja9vkr.fsf@pond.sub.org> (raw)
In-Reply-To: <ZPbt0io6He9mE2SB@redhat.com> (Kevin Wolf's message of "Tue, 5 Sep 2023 10:58:58 +0200")
Kevin Wolf <kwolf@redhat.com> writes:
> Am 04.09.2023 um 18:25 hat Daniel P. Berrangé geschrieben:
>> By the time of the 8.2.0 release, it will have been 2 years and 6
>> releases since we accidentally broke setting of array properties
>> for user creatable devices:
>>
>> https://gitlab.com/qemu-project/qemu/-/issues/1090
>
> Oh, nice!
Nice? *Awesome*!
> Well, maybe that sounds a bit wrong, but the syntax that was broken was
> problematic and more of a hack,
A monstrosity, in my opinion. I tried to strangle it in the crib, but
its guardians wouldn't let me. Can dig up references for the morbidly
curious.
> and after two years there is clearly no
> need to bring the exact same syntax back now.
Exactly.
> So I'd suggest we bring the funcionality back, but with proper QAPI
> lists instead of len-foo/foo[*].
>
> If we ever want to continue with command line QAPIfication, this change
> would already solve one of the compatibility concerns we've had in the
> past.
>
>> I still think for user creatable devices we'd be better off just
>> mandating the use of JSON syntax for -device and thus leveraging
>> the native JSON array type. This patch was the quick fix for the
>> existing array property syntax though.
>
> I agree, let's not apply this one. It puts another ugly hack in the
> common QOM code path just to bring back the old ugly hack in qdev.
Since -device supports both JSON and dotted keys, we'd still offer a
(differently ugly) solution for users averse to JSON.
next prev parent reply other threads:[~2023-09-07 9:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 16:25 [PATCH 0/1] qom: fix setting of qdev array properties Daniel P. Berrangé
2023-09-04 16:25 ` [PATCH 1/1] qom: fix setting of " Daniel P. Berrangé
2023-09-05 8:58 ` [PATCH 0/1] qom: fix setting of qdev " Kevin Wolf
2023-09-05 9:35 ` Peter Maydell
2023-09-07 9:33 ` Markus Armbruster [this message]
2023-09-07 9:35 ` Peter Maydell
2023-09-07 10:06 ` Daniel P. Berrangé
2023-09-08 9:25 ` Kevin Wolf
2023-09-08 9:27 ` Daniel P. Berrangé
2023-09-08 12:16 ` Kevin Wolf
2023-09-08 12:19 ` Daniel P. Berrangé
2023-09-08 9:53 ` Peter Maydell
2023-09-08 12:22 ` Kevin Wolf
2023-09-08 12:52 ` Peter Maydell
2023-09-07 12:59 ` Kevin Wolf
2023-09-07 14:16 ` Markus Armbruster
2023-09-07 9:45 ` Markus Armbruster
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=87edja9vkr.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eduardo@habkost.net \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=williamtsai1111@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.