qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qdev: Fix bus dependency of DeviceState::hotpluggable getter
Date: Sun, 09 Mar 2014 17:48:57 +0100	[thread overview]
Message-ID: <531C9B79.70905@suse.de> (raw)
In-Reply-To: <20140309164018.GB8717@redhat.com>

Am 09.03.2014 17:40, schrieb Michael S. Tsirkin:
> On Fri, Mar 07, 2014 at 07:13:18PM +0100, Andreas Färber wrote:
>> Commit 1a37eca107cece3ed454bae29eef0bd1fac4a244 (qdev: add
>> "hotpluggable" property to Device) added a property "hotpluggable" to
>> each device, with its getter accessing parent_bus->allow_hotplug.
>>
>> Add a NULL check.
>>
>> Cc: Igor Mammedov <imammedo@redhat.com>
>> Signed-off-by: Andreas Färber <afaerber@suse.de>
> 
> Fair enough but I'm guessing we should
> assume devices without a parent are not
> hotpluggable, should we not?
> 
> Without a bus what handles hotplug?

The device has to, in its realize function.

>> ---
>>  hw/core/qdev.c | 3 ++-
>>  1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/hw/core/qdev.c b/hw/core/qdev.c
>> index 749c83a..cb07863 100644
>> --- a/hw/core/qdev.c
>> +++ b/hw/core/qdev.c
>> @@ -735,7 +735,8 @@ static bool device_get_hotpluggable(Object *obj, Error **err)
>>      DeviceClass *dc = DEVICE_GET_CLASS(obj);
>>      DeviceState *dev = DEVICE(obj);
>>  
>> -    return dc->hotpluggable && dev->parent_bus->allow_hotplug;
>> +    return dc->hotpluggable && (dev->parent_bus == NULL ||
>> +                                dev->parent_bus->allow_hotplug);
> 
> So maybe this should be:
>>     return dc->hotpluggable && dev->parent_bus &&
>>                                dev->parent_bus->allow_hotplug;
> 
> ?

Hmm... that would render non-x86 CPUs non-hotpluggable. I guess we need
to check dc->bus_type for a NULL value and if non-NULL use your variant
and otherwise mine. I'll give it some more thought.

Thanks,
Andreas

> 
>>  }
>>  
>>  static void device_initfn(Object *obj)
>> -- 
>> 1.8.4.5

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2014-03-09 16:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07 18:13 [Qemu-devel] [PATCH] qdev: Fix bus dependency of DeviceState::hotpluggable getter Andreas Färber
2014-03-09 16:40 ` Michael S. Tsirkin
2014-03-09 16:48   ` Andreas Färber [this message]
2014-03-09 16:55     ` Michael S. Tsirkin
2014-03-10 11:37       ` Igor Mammedov

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=531C9B79.70905@suse.de \
    --to=afaerber@suse.de \
    --cc=imammedo@redhat.com \
    --cc=mst@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).