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] Re: max vcpus in dom0

To: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Subject: [Xen-devel] Re: max vcpus in dom0
From: Mukesh Rathor <mukesh.rathor@xxxxxxxxxx>
Date: Tue, 27 Apr 2010 19:34:22 -0700
Cc: Xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 27 Apr 2010 19:36:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BD6AD07020000780005CF3B@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/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: <4BD6AD07020000780005CF3B@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, 27 Apr 2010 09:23:19 +0100
"Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> >>> Mukesh Rathor  04/27/10 4:20 AM >>>
> >Looking at a bug where dom0 is crashing coming up with more than 32
> >vcpus, the problem happens trying to initialize 32nd vcpu. I see
> >the shared info is limited to 32vcpus, implying we'd have a hard
> >limit of 32 vcpus in dom0, correct? 
> 
> That's the legacy limit, yes. Any attempt to go beyond 32 CPUs
> requires the kernel to use the per-vCPU-info-placement hypercall
> prior to bringing up those vCPU-s.
> 
> Jan

Hi Jan,

Yes, I found your patch searching xen-devel implementing
VCPUOP_register_vcpu_info after I posted my msg. However, I don't find
any kernel using this other than pv-ops kernel. So I assume this is
work in progress. If you already have a patch for 2.6.18-xxx, please let
me know, if not, I'll work on it.


thanks,
Mukesh

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

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