On 15 April 2013 23:12, Igor Mammedov imamm...@redhat.com wrote:
... to provide hotplug-able bus.
* icc-bridge will serve as a parent for icc-bus and provide
mmio mapping services to child icc-devices.
* icc-device will replace SysBusDevice as a parent of APIC
and IOAPIC devices.
Il 22/04/2013 13:39, Peter Maydell ha scritto:
... to provide hotplug-able bus.
* icc-bridge will serve as a parent for icc-bus and provide
mmio mapping services to child icc-devices.
* icc-device will replace SysBusDevice as a parent of APIC
and IOAPIC devices.
Signed-off-by:
Am 16.04.2013 00:12, schrieb Igor Mammedov:
... to provide hotplug-able bus.
* icc-bridge will serve as a parent for icc-bus and provide
mmio mapping services to child icc-devices.
* icc-device will replace SysBusDevice as a parent of APIC
and IOAPIC devices.
Signed-off-by: Igor
On Mon, 22 Apr 2013 15:22:30 +0200
Andreas Färber afaer...@suse.de wrote:
Am 16.04.2013 00:12, schrieb Igor Mammedov:
... to provide hotplug-able bus.
* icc-bridge will serve as a parent for icc-bus and provide
mmio mapping services to child icc-devices.
* icc-device will replace
... to provide hotplug-able bus.
* icc-bridge will serve as a parent for icc-bus and provide
mmio mapping services to child icc-devices.
* icc-device will replace SysBusDevice as a parent of APIC
and IOAPIC devices.
Signed-off-by: Igor Mammedov imamm...@redhat.com
---
v2:
* Rebase on top
