From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, ehabkost@redhat.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH] qdev: Make -device FOO, help help again when FOO is not pluggable
Date: Mon, 16 Mar 2015 18:37:00 +0100 [thread overview]
Message-ID: <550714BC.3090101@redhat.com> (raw)
In-Reply-To: <1426527232-15044-1-git-send-email-armbru@redhat.com>
On 16/03/2015 18:33, Markus Armbruster wrote:
> Doesn't work since commit 31bed55 changed qdev_device_help() to reject
> abstract devices and devices that have
> cannot_instantiate_with_device_add_yet set.
>
> The former makes sense: abstract devices are purely internal, and the
> implementation of the help feature can't cope with them.
>
> The latter makes less sense: the implementation works fine, and even
> though you can't -device such a device, the help may still be useful
> elsewhere, for instance with -global.
>
> Revert the latter by moving the cannot_instantiate_with_device_add_yet
> check back to the other caller of qdev_get_device_class(),
> qdev_device_add().
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
Cc: qemu-stable@nongnu.org
I'm picking this patch up. It will miss -rc0, but I'll send my next
pull request before -rc1.
Paolo
> ---
> qdev-monitor.c | 22 ++++++++++++----------
> 1 file changed, 12 insertions(+), 10 deletions(-)
>
> diff --git a/qdev-monitor.c b/qdev-monitor.c
> index 5d30ac5..b0b8cf1 100644
> --- a/qdev-monitor.c
> +++ b/qdev-monitor.c
> @@ -180,10 +180,14 @@ static const char *find_typename_by_alias(const char *alias)
> return NULL;
> }
>
> +
> +/**
> + * Return DeviceClass for concrete device type @driver.
> + * On error, store an error through @errp if non-null, and return %NULL.
> + */
> static DeviceClass *qdev_get_device_class(const char **driver, Error **errp)
> {
> ObjectClass *oc;
> - DeviceClass *dc;
>
> oc = object_class_by_name(*driver);
> if (!oc) {
> @@ -206,15 +210,7 @@ static DeviceClass *qdev_get_device_class(const char **driver, Error **errp)
> return NULL;
> }
>
> - dc = DEVICE_CLASS(oc);
> - if (dc->cannot_instantiate_with_device_add_yet ||
> - (qdev_hotplug && !dc->hotpluggable)) {
> - error_set(errp, QERR_INVALID_PARAMETER_VALUE, "driver",
> - "pluggable device type");
> - return NULL;
> - }
> -
> - return dc;
> + return DEVICE_CLASS(oc);
> }
>
>
> @@ -512,6 +508,12 @@ DeviceState *qdev_device_add(QemuOpts *opts)
> error_free(err);
> return NULL;
> }
> + if (dc->cannot_instantiate_with_device_add_yet ||
> + (qdev_hotplug && !dc->hotpluggable)) {
> + qerror_report(QERR_INVALID_PARAMETER_VALUE, "driver",
> + "pluggable device type");
> + return NULL;
> + }
>
> /* find bus */
> path = qemu_opt_get(opts, "bus");
>
next prev parent reply other threads:[~2015-03-16 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 17:33 [Qemu-devel] [PATCH] qdev: Make -device FOO, help help again when FOO is not pluggable Markus Armbruster
2015-03-16 17:37 ` Paolo Bonzini [this message]
2015-03-16 18:13 ` Eduardo Habkost
2015-03-17 7:15 ` Markus Armbruster
2015-03-17 14:57 ` Eduardo Habkost
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=550714BC.3090101@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).