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-merge] [PATCH] allow x86-64/SMP to boot

To: <xen-merge@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-merge] [PATCH] allow x86-64/SMP to boot
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Fri, 16 Dec 2005 16:24:28 +0100
Delivery-date: Fri, 16 Dec 2005 15:26:22 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-merge-request@lists.xensource.com?subject=help>
List-id: xen-merge <xen-merge.lists.xensource.com>
List-post: <mailto:xen-merge@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-merge>, <mailto:xen-merge-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-merge>, <mailto:xen-merge-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-merge-bounces@xxxxxxxxxxxxxxxxxxx
Since x86-64 general code changes were merged a little carelessly into
xen specific code, SMP kernels didn't boot anymore, because
cpu_possible_map is required to be properly filled much earlier.
Attached a patch that allowed us to get things to work again, but I'm
not certain this is entirely the right change; namely am I unsure what
set of processors the hypervisor makes available through ACPI (the
vcpu-s the domain is configured for, which would imply ACPI tables
different from the BIOSes get provided, or the raw CPUs available on the
system, in case the original ACPI tables get mirrored to the domain).


Attachment: xenlinux-x86_64-cpu-possible-map.patch
Description: Text document

Xen-merge mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-merge] [PATCH] allow x86-64/SMP to boot, Jan Beulich <=