[Xen-devel] [PATCH] Fix xm vcpu-pin for inactive managed domains

[Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>]

Hi,

We cannot currently change cpu affinity definitions of inactive managed 
domains by xm vcpu-pin command. 

# xm vcpu-list vm1
Name                                ID  VCPU   CPU State   Time(s) CPU Affinity
vm1                                        0                   0.0 any cpu
vm1                                        1                   0.0 any cpu
# xm vcpu-pin vm1 all 2,3
Error: Cannot pin vcpu: 0 to cpu: [2, 3] - an integer is required
Usage: xm vcpu-pin <Domain> <VCPU|all> <CPUs|all>

Set which CPUs a VCPU can use.


This patch enables changing cpu affinity definitions of inactive managed 
domains. 
However, we cannot change cpu affinity definitions to each vcpu because 
we cannot currently define cpu affinity definitions to each vcpu to domain 
configuration definitions.  Therefore, we need to specify 'all' to VCPU 
argument of xm vcpu-pin command. 

# xm vcpu-list vm1
Name                                ID  VCPU   CPU State   Time(s) CPU Affinity
vm1                                        0                   0.0 any cpu
vm1                                        1                   0.0 any cpu
# xm vcpu-pin vm1 all 0,1
# xm vcpu-list vm1
Name                                ID  VCPU   CPU State   Time(s) CPU Affinity
vm1                                        0                   0.0 0-1
vm1                                        1                   0.0 0-1
# xm vcpu-pin vm1 all 2,3
# xm vcpu-list vm1
Name                                ID  VCPU   CPU State   Time(s) CPU Affinity
vm1                                        0                   0.0 2-3
vm1                                        1                   0.0 2-3
# xm vcpu-pin vm1 0 0,1
Error: Must specify 'all' to VCPU for inactive managed domains
Usage: xm vcpu-pin <Domain> <VCPU|all> <CPUs|all>

Set which CPUs a VCPU can use.


Signed-off-by: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>

Best regards,
 Kan

xm_vcpupin.patch
Description: Binary data

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