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] RFC: large system support - 128 CPUs

To: Bill Burns <bburns@xxxxxxxxxx>
Subject: Re: [Xen-devel] RFC: large system support - 128 CPUs
From: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Date: Wed, 13 Aug 2008 09:21:29 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 13 Aug 2008 01:22:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48A1D946.4040608@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>
References: <48A1D946.4040608@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.17 (2007-11-01)
At 14:41 -0400 on 12 Aug (1218552070), Bill Burns wrote:
> First 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.
> A possible fix is to tack on the following to
> the end of shadow_page_info structure:

Yep, that'll sort it out fine.  I don't think the #if is even needed
because a cpumask is always at least the size of a long.  Or you could
add a "cpumask_t _unused;" to the union with mbz in it since that's
where the sizes get out of sync.



Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, Citrix Systems (R&D) Ltd.
[Company #02300071, SL9 0DZ, UK.]

Xen-devel mailing list