RE: [Xen-devel] dom0 vcpu set problem

["Liu, Jinsong" <jinsong.liu@xxxxxxxxx>]

Yes, acpi hotplug is for hvm vcpu hotplug.

To get more xenstore refer, you can access
http://wiki.xensource.com/xenwiki/XenStore?highlight=%28xenstore%29
http://wiki.xensource.com/xenwiki/XenStoreReference?highlight=%28xenstore%29

Attached is the tool to dump xenstore, with it, you can get info for dom0 vcpu 
add/remove, like:
xm vcpu-set 0 1
/local/domain/0/cpu/1/availability=offline
/local/domain/0/cpu/0/availability=online

xm vcpu-set 0 2
/local/domain/0/cpu/1/availability=online
/local/domain/0/cpu/0/availability=online

pv vcpu hotplug code is as what Jan said.

Thanks,
Jinsong

Jan Beulich wrote:
>>>> Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx> 11.05.10 08:19 >>>
>> Can anybody point me where in the code the acpi cpu hotplug gets
>> triggered to add the vcpu again to the dom0 kernel after setting the
>> xenstore! 
> 
> No, ACPI hotplug code is not involved in pv domains' vCPU adding or
> removal. Instead, the pv kernels create a xenstore watch on their
> domain's "cpu" node, reading cpu/<id>/availability when the watch
> fires. See drivers/xen/core/cpu_hotplug.c (for the forward ported
> kernels) or drivers/xen/cpu_hotplug.c (for the pv-ops ones).
> 
> Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

dumpxenstore.sh
Description: dumpxenstore.sh

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel