From: "Andreas Färber" <afaerber@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org,
Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Subject: Re: [Qemu-devel] [PATCH] qdev: Fix qdev_try_create() for bus-less devices
Date: Wed, 05 Feb 2014 18:20:55 +0100 [thread overview]
Message-ID: <52F272F7.1080309@suse.de> (raw)
In-Reply-To: <52F26AEB.9040100@suse.de>
Am 05.02.2014 17:46, schrieb Andreas Färber:
> Am 05.02.2014 17:38, schrieb Paolo Bonzini:
>> Il 05/02/2014 15:09, Andreas Färber ha scritto:
>>> diff --git a/hw/core/qdev.c b/hw/core/qdev.c
>>> index 82a9123..14c8765 100644
>>> --- a/hw/core/qdev.c
>>> +++ b/hw/core/qdev.c
>>> @@ -131,21 +131,27 @@ DeviceState *qdev_create(BusState *bus, const
>>> char *name)
>>> DeviceState *qdev_try_create(BusState *bus, const char *type)
>>> {
>>> DeviceState *dev;
>>> + ObjectClass *oc;
>>> + DeviceClass *dc;
>>>
>>> - if (object_class_by_name(type) == NULL) {
>>> + oc = object_class_by_name(type);
>>> + if (oc == NULL) {
>>> return NULL;
>>> }
>>> + dc = DEVICE_CLASS(oc);
>>> dev = DEVICE(object_new(type));
>>> if (!dev) {
>>> return NULL;
>>> }
>>>
>>> - if (!bus) {
>>> + if (!bus && dc->bus_type && strcmp(dc->bus_type, "System") == 0) {
>>
>> Should you check instead if dev is-a TYPE_SYSBUS_DEVICE?
>
> Hmm, that would catch TYPE_SYS_BUS_DEVICE-derived types as well, which
> might in theory override bus_type.
>
> The ugly thing here is the cyclic dependency betwen qdev and sysbus,
> therefore no TYPE_SYSTEM_BUS.
BTW this patch became optional due to the one-line nand fix (which also
does not show the device in legacy info qtree), but I am still in favor
of merging this or a variation thereof to avoid future troubles.
Andreas
>
>> Does this also leave the nand device out of info qtree, or is it still
>> dumped?
>
> As I pointed out several times already, devices that are not on a bus
> are generally *not* printed by info qtree. It depends on the old qbus
> concept. Therefore info qtree is not of much use anymore and should be
> dropped in favor of the qom-list and qom-get operations, which get us
> all devices and all properties. I had once attached a qom-tree for that
> and need to put that into a proper patch. Best before the next question
> pops up. :)
>
> Andreas
>
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-02-05 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 14:09 [Qemu-devel] [PATCH] qdev: Fix qdev_try_create() for bus-less devices Andreas Färber
2014-02-05 16:38 ` Paolo Bonzini
2014-02-05 16:46 ` Andreas Färber
2014-02-05 17:20 ` Andreas Färber [this message]
2014-02-05 23:16 ` Peter Crosthwaite
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=52F272F7.1080309@suse.de \
--to=afaerber@suse.de \
--cc=pbonzini@redhat.com \
--cc=peter.crosthwaite@xilinx.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).