From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mukesh Rathor <mukesh.rathor@oracle.com>
Subject: Re: max vcpus in dom0
Date: Tue, 27 Apr 2010 19:34:22 -0700
Message-ID: <20100427193422.36ac956e@mantra.us.oracle.com>
References: <4BD6AD07020000780005CF3B@vpn.id2.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4BD6AD07020000780005CF3B@vpn.id2.novell.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Jan Beulich <jbeulich@novell.com>
Cc: Xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On Tue, 27 Apr 2010 09:23:19 +0100
"Jan Beulich" <jbeulich@novell.com> 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