[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC 4/8] qdev: link based hotplug
From: |
Igor Mammedov |
Subject: |
Re: [Qemu-devel] [RFC 4/8] qdev: link based hotplug |
Date: |
Thu, 20 Mar 2014 17:20:32 +0100 |
On Thu, 20 Mar 2014 17:12:17 +0100
Paolo Bonzini <address@hidden> wrote:
> Il 20/03/2014 16:01, Igor Mammedov ha scritto:
> > + /*
> > + * Returns path to link<> that should be set/unset on dev hotplug.
> > + * Used for link based bussless devices hotplug.
> > + */
> > + char* (*hotplug_path)(DeviceState *dev);
> > +
>
> What about just looking up on the QOM tree until you find a
> HotplugHandler, if the device doesn't have a bus or the bus doesn't have
> a hotplug handler link itself? This is similar to how FWPathProvider works.
it does so "hotplug_handler_get_from_path()",
above just provides option to specify lookup path. See 6/8 where PC board
allocates links and sets its own board specific path for generic DimmDevice.
>
> Paolo
[Qemu-devel] [RFC 5/8] dimm: implement dimm device abstraction, Igor Mammedov, 2014/03/20
[Qemu-devel] [RFC 4/8] qdev: link based hotplug, Igor Mammedov, 2014/03/20
[Qemu-devel] [RFC 6/8] pc: preallocate hotplug links for DIMMDevices, Igor Mammedov, 2014/03/20
[Qemu-devel] [RFC 7/8] pc: initialize memory hotplug address space, Igor Mammedov, 2014/03/20
[Qemu-devel] [RFC 8/8] pc: make PC_MACHINE memory hotplug controller, Igor Mammedov, 2014/03/20