WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] [PATCH] Fix xm vcpu-pin command

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH] Fix xm vcpu-pin command
From: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
Date: Tue, 19 Feb 2008 18:45:23 +0900
Delivery-date: Tue, 19 Feb 2008 01:46:47 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

When I tested xm vcpu-pin command, I encountered the following strange 
problem.  I encountered it on x86, but I didn't encounter it on ia64. 

On x86:
 # xm vcpu-list
 Name                                ID  VCPU   CPU State   Time(s) CPU Affinity
 Domain-0                             0     0     0   -b-      31.3 any cpu
 Domain-0                             0     1     1   r--      30.1 any cpu
 # xm vcpu-pin Domain-0 0 64
 # xm vcpu-list
 Name                                ID  VCPU   CPU State   Time(s) CPU Affinity
 Domain-0                             0     0     0   -b-      31.5 0
 Domain-0                             0     1     1   r--      31.1 any cpu
 # xm vcpu-pin Domain-0 0 65
 # xm vcpu-list
 Name                                ID  VCPU   CPU State   Time(s) CPU Affinity
 Domain-0                             0     0     1   -b-      32.0 1
 Domain-0                             0     1     0   r--      31.6 any cpu

On ia64:
 # xm vcpu-list
 Name                                ID  VCPU   CPU State   Time(s) CPU Affinity
 Domain-0                             0     0     0   r--      13.2 any cpu
 Domain-0                             0     1     1   -b-      10.8 any cpu
 # xm vcpu-pin Domain-0 0 64
 Error: Cannot pin vcpu: 0 to cpu: [64] - (22, 'Invalid argument')
 Usage: xm vcpu-pin <Domain> <VCPU|all> <CPUs|all>
 
 Set which CPUs a VCPU can use.
 # xm vcpu-list
 Name                                ID  VCPU   CPU State   Time(s) CPU Affinity
 Domain-0                             0     0     0   r--      13.5 any cpu
 Domain-0                             0     1     1   -b-      11.0 any cpu
 # xm vcpu-pin Domain-0 0 65
 Error: Cannot pin vcpu: 0 to cpu: [65] - (22, 'Invalid argument')
 Usage: xm vcpu-pin <Domain> <VCPU|all> <CPUs|all>
 
 Set which CPUs a VCPU can use.
 # xm vcpu-list
 Name                                ID  VCPU   CPU State   Time(s) CPU Affinity
 Domain-0                             0     0     0   r--      13.7 any cpu
 Domain-0                             0     1     1   -b-      11.3 any cpu


I could not understand why the problem occurs.  But I would like to 
solve the problem, so I send an ad hoc patch.  If you can solve the 
problem, I hope that the problem is solved by your patch. 

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

Best regards,
 Kan

Attachment: xm_vcpupin.patch
Description: Binary data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>