From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: imammedo@redhat.com, vsementsov@virtuozzo.com,
berrange@redhat.com, ehabkost@redhat.com
Subject: Re: [PATCH] monitor: Tidy up find_device_state()
Date: Mon, 11 Oct 2021 08:39:36 +0200 [thread overview]
Message-ID: <cc3e1c8e-2472-1ba8-3a27-c220877b0756@redhat.com> (raw)
In-Reply-To: <20210916111707.84999-1-armbru@redhat.com>
On 16/09/21 13:17, Markus Armbruster wrote:
> Commit 6287d827d4 "monitor: allow device_del to accept QOM paths"
> extended find_device_state() to accept QOM paths in addition to qdev
> IDs. This added a checked conversion to TYPE_DEVICE at the end, which
> duplicates the check done for the qdev ID case earlier, except it sets
> a *different* error: GenericError "ID is not a hotpluggable device"
> when passed a QOM path, and DeviceNotFound "Device 'ID' not found"
> when passed a qdev ID. Fortunately, the latter won't happen as long
> as we add only devices to /machine/peripheral/.
>
> Earlier, commit b6cc36abb2 "qdev: device_del: Search for to be
> unplugged device in 'peripheral' container" rewrote the lookup by qdev
> ID to use QOM instead of qdev_find_recursive(), so it can handle
> buss-less devices. It does so by constructing an absolute QOM path.
> Works, but object_resolve_path_component() is easier. Switching to it
> also gets rid of the unclean duplication described above.
>
> While there, avoid converting to TYPE_DEVICE twice, first to check
> whether it's possible, and then for real.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> softmmu/qdev-monitor.c | 13 +++++--------
> 1 file changed, 5 insertions(+), 8 deletions(-)
Queued, thanks.
Paolo
> diff --git a/softmmu/qdev-monitor.c b/softmmu/qdev-monitor.c
> index a304754ab9..d1ab3c25fb 100644
> --- a/softmmu/qdev-monitor.c
> +++ b/softmmu/qdev-monitor.c
> @@ -831,16 +831,12 @@ void qmp_device_add(QDict *qdict, QObject **ret_data, Error **errp)
> static DeviceState *find_device_state(const char *id, Error **errp)
> {
> Object *obj;
> + DeviceState *dev;
>
> if (id[0] == '/') {
> obj = object_resolve_path(id, NULL);
> } else {
> - char *root_path = object_get_canonical_path(qdev_get_peripheral());
> - char *path = g_strdup_printf("%s/%s", root_path, id);
> -
> - g_free(root_path);
> - obj = object_resolve_path_type(path, TYPE_DEVICE, NULL);
> - g_free(path);
> + obj = object_resolve_path_component(qdev_get_peripheral(), id);
> }
>
> if (!obj) {
> @@ -849,12 +845,13 @@ static DeviceState *find_device_state(const char *id, Error **errp)
> return NULL;
> }
>
> - if (!object_dynamic_cast(obj, TYPE_DEVICE)) {
> + dev = (DeviceState *)object_dynamic_cast(obj, TYPE_DEVICE);
> + if (!dev) {
> error_setg(errp, "%s is not a hotpluggable device", id);
> return NULL;
> }
>
> - return DEVICE(obj);
> + return dev;
> }
>
> void qdev_unplug(DeviceState *dev, Error **errp)
>
prev parent reply other threads:[~2021-10-11 6:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 11:17 [PATCH] monitor: Tidy up find_device_state() Markus Armbruster
2021-09-16 11:26 ` Daniel P. Berrangé
2021-10-02 5:36 ` Markus Armbruster
2021-10-05 13:19 ` Damien Hedde
2021-10-11 6:39 ` Paolo Bonzini [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=cc3e1c8e-2472-1ba8-3a27-c220877b0756@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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 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).