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] numa=on broken

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] numa=on broken
From: Ryan Harper <ryanh@xxxxxxxxxx>
Date: Fri, 30 Mar 2007 12:34:32 -0500
Delivery-date: Fri, 30 Mar 2007 18:35:54 +0100
Envelope-to: Keir.Fraser@xxxxxxxxxxxx
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.5.6+20040907i
Testing the latest xen-unstable bits, booting with numa=on fails:

(XEN) Command line: /boot/xen.gz com1=115200,8n1 console=com1 conswitch=x 
(XEN) Physical RAM map:
(XEN)  0000000000000000 - 000000000009d000 (usable)
(XEN)  000000000009dc00 - 00000000000a0000 (reserved)
(XEN)  00000000000d0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000dff60000 (usable)
(XEN)  00000000dff60000 - 00000000dff72000 (ACPI data)
(XEN)  00000000dff72000 - 00000000dff80000 (ACPI NVS)
(XEN)  00000000dff80000 - 00000000e0000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec00400 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000fff80000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000200000000 (usable)
(XEN) System RAM: 7678MB (7863284kB)
(XEN) ACPI: RSDP (v002 PTLTD                                 ) @ 
(XEN) ACPI: XSDT (v001 PTLTD     XSDT   0x06040000  LTP 0x00000000) @ 
(XEN) ACPI: FADT (v003 AMD    HAMMER   0x06040000 PTEC 0x000f4240) @ 
(XEN) ACPI: SRAT (v001 AMD    HAMMER   0x06040000 AMD  0x00000001) @ 
(XEN) ACPI: MADT (v001 PTLTD     APIC   0x06040000  LTP 0x00000000) @ 
(XEN) ACPI: ASF! (v016    MBI     CETP 0x06040000 PTL  0x00000001) @ 
(XEN) ACPI: DSDT (v001 AMD-K8  AMDACPI 0x06040000 MSFT 0x0100000e) @ 
(XEN) SRAT: PXM 0 -> APIC 0 -> Node 0
(XEN) SRAT: PXM 1 -> APIC 1 -> Node 1
(XEN) SRAT: Node 0 PXM 0 0-a0000
(XEN) SRAT: Node 0 PXM 0 0-e0000000
(XEN) SRAT: Node 1 PXM 1 100000000-200000000
(XEN) NUMA: Using 32 for the hash shift.
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 2!
(XEN) Reserving non-aligned node boundary @ mfn 1048576
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 2!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 2!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 2!
(XEN) Unknown interrupt

Looking a little deeper, it looks like in end_boot_allocator() we are
attempting to dynamically allocate memory for addition arrays in avail[]
and for the heap.  This uses xmalloc() which relies on
alloc_xenheap_pages() to work.  alloc_xenheap_pages() can't function
until end_boot_allocator() completes.  Prior to end_boot_alloctor(), one
needs to use alloc_boot_pages().

Any thoughts on how to proceed here?

Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253

Xen-devel mailing list

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