From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Lu Gao <Lu.Gao@verisilicon.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Jianxian Wen <Jianxian.Wen@verisilicon.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Eduardo Habkost <eduardo@habkost.net>
Subject: Re: [PATCH] qom/object_interfaces: Handle `len-` property first
Date: Tue, 24 Oct 2023 10:20:37 +0100 [thread overview]
Message-ID: <ZTeMZbluC1EHa3rh@redhat.com> (raw)
In-Reply-To: <34781C803212B140A51E6B66D9092E5D02BEDA7B26@SHASXM06.verisilicon.com>
On Tue, Oct 24, 2023 at 08:53:31AM +0000, Lu Gao wrote:
> ping
>
> https://patchew.org/QEMU/20230921141634.26233-1-lu.gao@verisilicon.com/
>
> Could you please help review the patch?
>
> Thanks.
> B.R.
>
> -----Original Message-----
> From: Lu Gao
> Sent: Thursday, September 21, 2023 10:17 PM
> To: qemu-devel@nongnu.org
> Cc: Lu Gao; Jianxian Wen; Paolo Bonzini; Daniel P. Berrangé; Eduardo Habkost
> Subject: [PATCH] qom/object_interfaces: Handle `len-` property first
>
> From: "Gao, Lu" <lu.gao@verisilicon.com>
>
> Array property needs corresponding `len-` property set first to add
> actual array properties. Then we need to make sure `len-` property is
> set first before array property.
>
> But when the model is used with like
> `-device driver[,prop[=value][,...]]`
> in QEMU command line options, this is not guaranteed in current
> property set from qdict. Array property might be
> handled before 'len-' property, then leads to an error.
>
> Signed-off-by: Lu Gao <lu.gao@verisilicon.com>
> Signed-off-by: Jianxian Wen <jianxian.wen@verisilicon.com>
> ---
> qom/object_interfaces.c | 19 +++++++++++++++++--
> 1 file changed, 17 insertions(+), 2 deletions(-)
This approach has already been rejected in favour of a new impl
strategy for array properties shown in this series:
https://lists.nongnu.org/archive/html/qemu-devel/2023-09/msg01832.html
NB the syntax will change on the CLI
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2023-10-24 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 14:16 [PATCH] qom/object_interfaces: Handle `len-` property first Lu Gao
2023-10-24 8:53 ` Lu Gao via
2023-10-24 8:53 ` Lu Gao
2023-10-24 9:20 ` Daniel P. Berrangé [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=ZTeMZbluC1EHa3rh@redhat.com \
--to=berrange@redhat.com \
--cc=Jianxian.Wen@verisilicon.com \
--cc=Lu.Gao@verisilicon.com \
--cc=eduardo@habkost.net \
--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 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.