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


[Xen-devel] [PATCH] move MAX_VIRT_CPUS into arch header

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH] move MAX_VIRT_CPUS into arch header
From: Matt Chapman <matthewc@xxxxxx>
Date: Tue, 14 Jun 2005 14:51:49 -0600
Delivery-date: Tue, 14 Jun 2005 20:51:53 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
This patch moves the definition of MAX_VIRT_CPUS from xen.h into
arch-${ARCH}.h (which is included from xen.h).

The initial reason is that the current value of MAX_VIRT_CPUS overflows
the shared_info page on ia64.  Eventually we plan to move the VCPU data
onto separate pages.  However, this is an interim fix and I imagine that
the value of MAX_VIRT_CPUS may indeed be architecture-dependent - for
example, longer bitmasks on a 64-bit machine may make it easier to
support more virtual CPUs.


Signed-off-by: Matthew Chapman <matthewc@xxxxxx>

Attachment: max-virt-cpus.patch
Description: Text document

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH] move MAX_VIRT_CPUS into arch header, Matt Chapman <=