From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Cc: armbru@redhat.com, berrange@redhat.com, peter.maydell@linaro.org,
pbonzini@redhat.com
Subject: Re: [PATCH v3 10/11] qdev: Make netdev properties work as list elements
Date: Thu, 9 Nov 2023 20:13:45 +0100 [thread overview]
Message-ID: <0b711283-d06c-4146-9920-62f1896aea89@linaro.org> (raw)
In-Reply-To: <20231109174240.72376-11-kwolf@redhat.com>
On 9/11/23 18:42, Kevin Wolf wrote:
> The 'name' parameter of QOM setters is primarily used to specify the name
> of the currently parsed input element in the visitor interface. For
> top-level qdev properties, this is always set and matches 'prop->name'.
>
> However, for list elements it is NULL, because each element of a list
> doesn't have a separate name. Passing a non-NULL value runs into
> assertion failures in the visitor code.
>
> Therefore, using 'name' in error messages is not right for property
> types that are used in lists, because "(null)" (or even a segfault)
> isn't very helpful to identify what QEMU is complaining about.
>
> Change netdev properties to use 'prop->name' instead, which will contain
> the name of the array property after switching array properties to lists
> in the external interface. (This is still not perfect, as it doesn't
> identify which element in the list caused the error, but strictly better
> than before.)
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> hw/core/qdev-properties-system.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2023-11-09 19:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 17:42 [PATCH v3 00/11] qdev: Make array properties user accessible again Kevin Wolf
2023-11-09 17:42 ` [PATCH v3 01/11] hw/i386/pc: Use qdev_prop_set_array() Kevin Wolf
2023-11-09 19:11 ` Philippe Mathieu-Daudé
2023-11-09 17:42 ` [PATCH v3 02/11] hw/arm/mps2-tz: " Kevin Wolf
2023-11-09 17:42 ` [PATCH v3 03/11] hw/arm/mps2: " Kevin Wolf
2023-11-09 17:42 ` [PATCH v3 04/11] hw/arm/sbsa-ref: " Kevin Wolf
2023-11-09 17:42 ` [PATCH v3 05/11] hw/arm/vexpress: " Kevin Wolf
2023-11-09 17:42 ` [PATCH v3 06/11] hw/arm/virt: " Kevin Wolf
2023-11-09 17:42 ` [PATCH v3 07/11] hw/arm/xlnx-versal: " Kevin Wolf
2023-11-09 17:42 ` [PATCH v3 08/11] hw/rx/rx62n: " Kevin Wolf
2023-11-09 17:42 ` [PATCH v3 09/11] qom: Add object_property_set_default_list() Kevin Wolf
2023-11-09 19:12 ` Philippe Mathieu-Daudé
2023-11-09 17:42 ` [PATCH v3 10/11] qdev: Make netdev properties work as list elements Kevin Wolf
2023-11-09 19:13 ` Philippe Mathieu-Daudé [this message]
2023-11-09 17:42 ` [PATCH v3 11/11] qdev: Rework array properties based on list visitor Kevin Wolf
2023-11-09 19:14 ` [PATCH v3 00/11] qdev: Make array properties user accessible again Philippe Mathieu-Daudé
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=0b711283-d06c-4146-9920-62f1896aea89@linaro.org \
--to=philmd@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).