[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 14/30] target-i386: ICC bus: replace BusState.al
From: |
Igor Mammedov |
Subject: |
Re: [Qemu-devel] [PATCH 14/30] target-i386: ICC bus: replace BusState.allow_hotplug with hotplug_handler |
Date: |
Wed, 24 Sep 2014 17:30:49 +0200 |
On Wed, 24 Sep 2014 16:50:17 +0200
Paolo Bonzini <address@hidden> wrote:
> Il 24/09/2014 16:37, Igor Mammedov ha scritto:
> >> > If you do this, aren't you enabling CPU hot-unplug? Should
> >> > hotplug_handler_plug and/or hotplug_handler_unplug return an error if
> >> > there is no callback?
> > hotplug/unplug of x86 CPU is not usable with device_add/del yet, so
> > it's not used for CPUs yet.
> > x86 CPU nor APIC don't have DeviceClass.unplug callback so for old
> > behavior any attempt to call device_del would cause abort.
> > With this path attempt would become NOP.
>
> Can you make it an error instead? I guess that's related to the other
> question---whether hotplug_handler_plug and/or hotplug_handler_unplug
> should return an error if there is no callback.
For example that would make us in addition to above add fake plug/unplug
handlers without errors for APIC so it could be realized without error
when it's created by CPU. (applies to all composite devices).
Anyway question is moot if we are to drop hotplug assert from bus_add_child().
>
> Paolo
- Re: [Qemu-devel] [PATCH 10/30] qdev: HotplugHandler: rename unplug callback to unplug_request, (continued)
[Qemu-devel] [PATCH 15/30] virtio-pci: replace BusState.allow_hotplug with hotplug_handler, Igor Mammedov, 2014/09/24
[Qemu-devel] [PATCH 17/30] virtio-mmio: drop useless bus->allow_hotplug = 0, Igor Mammedov, 2014/09/24
[Qemu-devel] [PATCH 18/30] s390x: drop not used allow_hotplug in event-facility, Igor Mammedov, 2014/09/24
[Qemu-devel] [PATCH 19/30] s390x: convert s390-virtio to hotplug handler API, Igor Mammedov, 2014/09/24