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] [PATCH]Check the values of MAX_VIRT_CPUS and NR_CPUSfor

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, "Atsushi SAKAI" <sakaia@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH]Check the values of MAX_VIRT_CPUS and NR_CPUSfor SMP
From: Tristan Gingold <Tristan.Gingold@xxxxxxxx>
Date: Fri, 21 Apr 2006 09:39:54 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 21 Apr 2006 00:36:16 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <571ACEFD467F7749BC50E0A98C17CDD8094E7B66@pdsmsx403>
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>
References: <571ACEFD467F7749BC50E0A98C17CDD8094E7B66@pdsmsx403>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.5
Le Vendredi 21 Avril 2006 09:28, Tian, Kevin a écrit :
> From: Tristan Gingold [mailto:Tristan.Gingold@xxxxxxxx]
> >Sent: 2006年4月21日 15:26
> >
> >> >See how we solve this on x86 near the top of do_boot_cpu() in
> >> >arch/x86/smpboot.c. Essentially we allocate extra idle domains on
> >> >demand to give us enough idle vcpus for one per physical cpu.
> >> >
> >> >  -- Keir
> >>
> >> Yes, that's the same story on ia64 where we also allocate idle
> >> vcpu at do_boot_cpu(). That's why I'm not sure the real cause
> >> for Atsushi's issue.
> >
> >No, we don't create extra domains.  Therefore it there are more CPUs
> >than
> >VCPUs, something goes wrong...
> Yes, there's only one idle domain now. However I'm not sure
> why something will go wrong when NR_CPUS > MAX_VIRT_CPUS.
bvt has per VCPU data.  if #VCPU > #MAX_VIRT_CPUS, bvt reads/writes beyond the 


Xen-devel mailing list