All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Bill Burns <bburns@redhat.com>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Allow Hypervisor build with more than 64 CPUs
Date: Sun, 17 Aug 2008 11:23:25 +0100	[thread overview]
Message-ID: <C4CDBAAD.1C384%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <48A5D863.6000000@redhat.com>

On 15/8/08 20:26, "Bill Burns" <bburns@redhat.com> 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

      reply	other threads:[~2008-08-17 10:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-15 19:26 [PATCH] Allow Hypervisor build with more than 64 CPUs Bill Burns
2008-08-17 10:23 ` Keir Fraser [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C4CDBAAD.1C384%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=bburns@redhat.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.