On Thu, May 22, 2014 at 12:49:26PM +0200, Andreas Färber wrote:
> Hi,
>
> Am 22.05.2014 04:33, schrieb chen.fan.f...@cn.fujitsu.com:
> >I think if we want to use 'device/device_add' to implement CPU,
> > we must do some check before qemu_init_vcpu(). how can we to do that?
>
> We ran into suc
On Thu, 22 May 2014 02:33:45 +
"chen.fan.f...@cn.fujitsu.com" wrote:
> Hi,
>I think if we want to use 'device/device_add' to implement CPU,
> we must do some check before qemu_init_vcpu(). how can we to do that?
What check exactly would you like to perform?
For target-i38 you can look fo
Hi,
Am 22.05.2014 04:33, schrieb chen.fan.f...@cn.fujitsu.com:
>I think if we want to use 'device/device_add' to implement CPU,
> we must do some check before qemu_init_vcpu(). how can we to do that?
We ran into such problems before... If need be, we can change from the
old parent_realize sch
Hi,
I think if we want to use 'device/device_add' to implement CPU,
we must do some check before qemu_init_vcpu(). how can we to do that?
Thanks,
Chen
On Tue, 2014-05-13 at 18:08 +0800, Chen Fan wrote:
> this patches tried to make cpu hotplug with device_add,
> and made -device foo-x86_64-cp
this patches tried to make cpu hotplug with device_add,
and made -device foo-x86_64-cpu available，also we can
set apic-id property with command line, if without setting
apic-id property, we added first unoccupied apic id as the
default new apic id. and hotplug cpu with device_add, we
must make che
