On Fri, Apr 12, 2013 at 01:00:57PM +0200, Igor Mammedov wrote:
> On Thu, 11 Apr 2013 15:46:47 -0300
> Eduardo Habkost wrote:
>
> > On Thu, Apr 11, 2013 at 04:51:45PM +0200, Igor Mammedov wrote:
> > > hot-added CPU will be distributed to acpi_piix4, rtc_cmos and icc_bridge
> > >
> > > Signed-off-
On Thu, 11 Apr 2013 15:46:47 -0300
Eduardo Habkost wrote:
> On Thu, Apr 11, 2013 at 04:51:45PM +0200, Igor Mammedov wrote:
> > hot-added CPU will be distributed to acpi_piix4, rtc_cmos and icc_bridge
> >
> > Signed-off-by: Igor Mammedov
> > Reviewed-by: Paolo Bonzini
>
> Have you considered m
On Thu, Apr 11, 2013 at 04:51:45PM +0200, Igor Mammedov wrote:
> hot-added CPU will be distributed to acpi_piix4, rtc_cmos and icc_bridge
>
> Signed-off-by: Igor Mammedov
> Reviewed-by: Paolo Bonzini
Have you considered making a generic device creation/realization
notification mechanism, that c
hot-added CPU will be distributed to acpi_piix4, rtc_cmos and icc_bridge
Signed-off-by: Igor Mammedov
Reviewed-by: Paolo Bonzini
---
v2:
* move notifier to qom/cpu.c and call it from CPUClass.realize() on hotplug
* remove get_firmware_id() since it belong to other patch
---
include/sysemu/s
