From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Markus Armbruster" <armbru@redhat.com>,
"Claudio Fontana" <cfontana@suse.de>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [RFC PATCH] qom: Extract object_try_new() from qdev_new()
Date: Mon, 9 Jan 2023 12:25:47 +0100 [thread overview]
Message-ID: <0917600b-f7e8-de00-8ee7-51051c16538a@linaro.org> (raw)
In-Reply-To: <20230109112056.94385-1-philmd@linaro.org>
On 9/1/23 12:20, Philippe Mathieu-Daudé wrote:
> The module resolving in qdev_new() is specific to QOM, not to
> QDev. Extract the code as a new QOM object_try_new() helper so
> it can be reused by non-QDev code.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> RFC because I'm wonder if we can't find a better name...
>
> Also, should we refactor object_initialize() similarly,
> having object_try_initialize(..., Error *)?
> ---
> hw/core/qdev.c | 23 ++---------------------
> include/qom/object.h | 12 ++++++++++++
> qom/object.c | 23 +++++++++++++++++++++++
> 3 files changed, 37 insertions(+), 21 deletions(-)
>
> diff --git a/hw/core/qdev.c b/hw/core/qdev.c
> index d759c4602c..3a076dcc7f 100644
> --- a/hw/core/qdev.c
> +++ b/hw/core/qdev.c
> @@ -147,31 +147,12 @@ bool qdev_set_parent_bus(DeviceState *dev, BusState *bus, Error **errp)
>
> DeviceState *qdev_new(const char *name)
> {
> - ObjectClass *oc = object_class_by_name(name);
> -#ifdef CONFIG_MODULES
> - if (!oc) {
> - int rv = module_load_qom(name, &error_fatal);
> - if (rv > 0) {
> - oc = object_class_by_name(name);
> - } else {
> - error_report("could not find a module for type '%s'", name);
> - exit(1);
Wrong patch, sorry, v2 coming.
next prev parent reply other threads:[~2023-01-09 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 11:20 [RFC PATCH] qom: Extract object_try_new() from qdev_new() Philippe Mathieu-Daudé
2023-01-09 11:25 ` Philippe Mathieu-Daudé [this message]
2023-01-09 12:39 ` Daniel P. Berrangé
2023-01-09 13:17 ` Claudio Fontana
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=0917600b-f7e8-de00-8ee7-51051c16538a@linaro.org \
--to=philmd@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=cfontana@suse.de \
--cc=eduardo@habkost.net \
--cc=kraxel@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).