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] Allow Hypervisor build with more than 64 CPUs

To: Bill Burns <bburns@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Allow Hypervisor build with more than 64 CPUs
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Sun, 17 Aug 2008 11:23:25 +0100
Delivery-date: Sun, 17 Aug 2008 03:23:52 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48A5D863.6000000@xxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AckAU0gthoO/GGxGEd24dgAWy6hiGQ==
Thread-topic: [Xen-devel] [PATCH] Allow Hypervisor build with more than 64 CPUs
User-agent: Microsoft-Entourage/
On 15/8/08 20:26, "Bill Burns" <bburns@xxxxxxxxxx> wrote:

> Trying to build the Xen hypervisor with max_phys_cpus=128
> for x86_64 fails. (Note that this was on a 3.1 base, but
> unstable appears to have the same issue).
> There is a build assertion due to the size of
> the page_info structure and the shadow_page_info
> structures get out of sync due to the presence
> of cpumask_t in the page info structure (which
> grows with more than 64 CPUs).
> The proposed fix is to tack on the following to
> the end of shadow_page_info structure.

This should be fixed in c/s 18324 by relaxing the BUILD_BUG_ON().

 -- Keir

Xen-devel mailing list

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