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-ia64-devel

[Xen-ia64-devel] dom0-smp issue.

To: <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-ia64-devel] dom0-smp issue.
From: "yo.fujita" <yo.fujita@xxxxxxxxxxxxxxxx>
Date: Thu, 27 Jul 2006 19:23:14 +0900
Delivery-date: Thu, 27 Jul 2006 03:20:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcaxZqsOouj7XwJ0R9y1fXugzQ696A==
Hi

I will report a new issue, which was found by Yongkang at first.

As already reported by Yongkang, we also met the same dom0-smp issue.
Our test environment is as below.

cset          :10700
physical CPUs :3 (2 cores)
HyperThred    :enable

We tried 3 patterns of tests.
The first testing was done with the following parameters in elilo.conf.

append="dom0_max_vcpus=4 com2=115200,8n1 console=com2 sched=bvt
tbuf_size=128 -- nomca console=tty0 console=ttyS1,115200,8n1 rhgb
root=/dev/sda2"

System can boot up. But I can see only 3 CPUs in /proc/cpuinfo.
And "xm vcpu-list" result is below.
[root@tiger158 ~]# xm vcpu-list
Name                              ID  VCPU  CPU  State  Time(s)  CPU
Affinity
Domain-0                           0     0    0   r--     351.5  0
Domain-0                           0     1    1   r--     351.2  any cpu
Domain-0                           0     2    2   r--     350.9  any cpu
Domain-0                           0     3    -   --p       0.0  any cpu

In addition, I tried other test with parameter 8 and 0 of "dom0_max_vcpus=".
Each the results are as below.
#case param 8
[root@tiger158 ~]# xm vcpu-l
Name                              ID  VCPU  CPU  State  Time(s)  CPU
Affinity
Domain-0                           0     0    0   r--     643.4  0
Domain-0                           0     1    1   r--     643.1  any cpu
Domain-0                           0     2    2   r--     642.9  any cpu
Domain-0                           0     3    -   --p       0.0  any cpu
Domain-0                           0     4    -   --p       0.0  any cpu
Domain-0                           0     5    -   --p       0.0  any cpu
Domain-0                           0     6    -   --p       0.0  any cpu
Domain-0                           0     7    -   --p       0.0  any cpu

#case param 0
[root@tiger158 ~]# xm vcpu-l
Name                              ID  VCPU  CPU  State  Time(s)  CPU
Affinity
Domain-0                           0     0    0   r--     176.4  0
Domain-0                           0     1    1   r--     176.1  any cpu
Domain-0                           0     2    2   r--     175.9  any cpu
Domain-0                           0     3    -   --p       0.0  any cpu
Domain-0                           0     4    -   --p       0.0  any cpu
Domain-0                           0     5    -   --p       0.0  any cpu
Domain-0                           0     6    -   --p       0.0  any cpu
Domain-0                           0     7    -   --p       0.0  any cpu
Domain-0                           0     8    -   --p       0.0  any cpu
Domain-0                           0     9    -   --p       0.0  any cpu
Domain-0                           0    10    -   --p       0.0  any cpu
Domain-0                           0    11    -   --p       0.0  any cpu

Through all the tests, active VCPUs are only 3 and others are "p". 
I think xen0 can only recognize the 1st CPU of each physical CPU.

Thanks,
Fujita



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

<Prev in Thread] Current Thread [Next in Thread>