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/
Home Products Support Community News


RE: [Xen-devel] million cycle interrupt

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] million cycle interrupt
From: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
Date: Mon, 13 Apr 2009 17:14:48 -0500
Accept-language: en-US
Acceptlanguage: en-US
Delivery-date: Mon, 13 Apr 2009 15:15:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <80803855-cac6-4b43-bb0e-fae8d85062f9@default>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <F08FB3AE1C57B54DAE921605F219DFC21E6B1C8FB8@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <80803855-cac6-4b43-bb0e-fae8d85062f9@default>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acm8dctR69FFyt9CRUGLBuuNOre8ZwADznSQ
Thread-topic: [Xen-devel] million cycle interrupt
I have only tried increasing the max_phys_cpus from 32 to 64, 96 etc. I would 
think that decreasing it to 4 means that only the first 4 LCPUS were booted. 
The rest should have been ignored.

-----Original Message-----
From: Dan Magenheimer [mailto:dan.magenheimer@xxxxxxxxxx]
Sent: Monday, April 13, 2009 4:24 PM
To: Puthiyaparambil, Aravindh; Xen-Devel (E-mail)
Subject: RE: [Xen-devel] million cycle interrupt

Thanks Aravindh!

Hmmm... I'm suspicious of this.  When compiled with
max_phys_cpus=4, xm info shows nr_cpus=4, nr_nodes=1,
cores_per_socket=1 and threads_per_core=1.  Without
this compile option, cores_per_socket=4 and
threads_per_core=2... so I would expect only one
of these to change.  Hopefully the compile option
is simply changing the data reported by xm info.
It appears the guest still is using 4 physical processors.

> -----Original Message-----
> From: Puthiyaparambil, Aravindh
> [mailto:aravindh.puthiyaparambil@xxxxxxxxxx]
> Sent: Monday, April 13, 2009 9:31 AM
> To: Dan Magenheimer; Xen-Devel (E-mail)
> Subject: RE: [Xen-devel] million cycle interrupt
> >>Is there a way to cap the number of physical cpus seen by Xen
> >>(other than nosmp to cap at one)?
> There is a compile time option (max_phys_cpus) where you can
> specify the number of LCPUs.
> Aravindh Puthiyaparambil
> Virtualization Engineer
> Virtual Systems Development
> Unisys, Tredyffrin PA

Xen-devel mailing list

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