WARNING - OLD ARCHIVES

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/
   
 
 
Xen 		  
Home Products Support Community News
 
   
 

xen-ia64-devel

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [Xen-ia64-devel] [PATCH][RFC]discontig memory support

from [Kouya SHIMURA] [Permanent Link][Original]
To: Alex Williamson <alex.williamson@xxxxxx>
Subject: Re: [Xen-ia64-devel] [PATCH][RFC]discontig memory support
From: Kouya SHIMURA <kouya@xxxxxxxxxxxxxx>
Date: Tue, 4 Apr 2006 11:32:15 +0900
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 03 Apr 2006 19:32:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1144079139.5331.29.camel@localhost>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <200604031231.k33CVki30168@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <1144079139.5331.29.camel@localhost>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx 
Hi Alex,

 > [TODO]
 >   * mpt_table (defined in xen/arch/ia64/xen/xenmem.c) implies the same
 >     problem. We have to fix it.

Maybe you hit the abobe issue. 
0-260GB address space requres contiguous 130MB area for mpt_table.
mpt_table is still allocated from xen heap(up to 64MB) and
the area doesn't suffice at all. 

I will fix soon.

Kouya

Alex Williamson writes:
 > On Mon, 2006-04-03 at 21:31 +0900, Kouya SHIMURA wrote:
 > > Hi xen/ia64 developers.
 > > 
 > > The attached patch supports discontiguous memory. 
 > > It also makes over 4GB memory available.
 > > Please comment and review.
 > 
 > Hi Kouya,
 > 
 >    Nice work.  I agree with Kevin, let's start with the easier solution
 > and work towards SPARSEMEM if we determine it's better.  I see it's on
 > your todo list, but documenting the performance difference will also be
 > important for evaluating future changes.
 > 
 >    I tried this patch on a zx1 system.  Unfortunately I'm still not able
 > to use all of the memory.  The system has 10GB of memory with the
 > following memory address space: 0-1GB, 4-10GB, 257-260GB.  On current
 > xen-ia64-unstable tip, I'm able to use the memory in the first two
 > address spaces by passing xen the option max_addr=10G (of course I only
 > get 7GB of usable memory).  If I apply this patch and remove the
 > max_addr option, I get the boot log below.  This system has a fairly
 > sparse layout, but newer and bigger systems have even larger and more
 > sparse layouts.  Thanks,
 > 
 >      Alex
 > 
 > -- 
 > Alex Williamson                             HP Linux & Open Source Lab
 > 
 > (XEN) Console output is synchronous.
 > (XEN) xen image pstart: 0x4000000, xenheap pend: 0x8000000
 > (XEN) efi.trim_top: ignoring 4KB of memory at 0x0 due to granule hole at 0x0
 > (XEN) efi.trim_top: ignoring 636KB of memory at 0x1000 due to granule hole 
 > at 0x0
 > (XEN) efi.trim_bottom: ignoring 15360KB of memory at 0x100000 due to granule 
 > hole at 0x0
 > (XEN) ready to move Dom0 to 0x8000000 with len e20168...ready to move initrd 
 > to 0x8e24000 with len 0...Done
 > (XEN) find_memory: efi_memmap_walk returns max_page=103fff0
 > (XEN) find_memory: last granule reserved for dom0; xen max_page=103f800
 > (XEN) Before heap_start: f000000004102370
 > (XEN) After heap_start: f00000000430c000
 > (XEN) Init boot pages: 0x1000000 -> 0x4000000.
 > (XEN) Init boot pages: 0x8000000 -> 0x3f5e4000.
 > (XEN) Init boot pages: 0x3fb00000 -> 0x3fb2c000.
 > (XEN) Init boot pages: 0x100000000 -> 0x27fffc000.
 > (XEN) Init boot pages: 0x4040000000 -> 0x40fdf7c008.
 > (XEN) Init boot pages: 0x40fdf7c068 -> 0x40fdf7ff9e.
 > (XEN) Init boot pages: 0x40fdf7ffd2 -> 0x40fef9a008.
 > (XEN) Init boot pages: 0x40fef9a7e8 -> 0x40ffd68000.
 > (XEN) Init boot pages: 0x40ffda8000 -> 0x40ffe10000.
 > (XEN) Init boot pages: 0x40ffe80000 -> 0x40fffc0000.
 > (XEN) System RAM: 10213MB (10458224kB)
 > (XEN) size of virtual frame_table: 25616kB
 > (XEN) alloc_dom0: starting (initializing 512 MB...)
 > (XEN) alloc_dom0: dom0_start=0x8000000
 > (XEN) Xen heap: 60MB (62416kB)
 > (XEN) About to call scheduler_init()
 > (XEN) Using scheduler: Simple EDF Scheduler (sedf)
 > (XEN) ACPI: RSDP (v002     HP                                ) @ 
 > 0x000000003fb2e000
 > (XEN) ACPI: XSDT (v001     HP   zx6000 0x00000000 HP 0x00000000) @ 
 > 0x000000003fb2e02c
 > (XEN) ACPI: FADT (v003     HP   zx6000 0x00000000 HP 0x00000000) @ 
 > 0x000000003fb369e0
 > (XEN) ACPI: SPCR (v001     HP   zx6000 0x00000000 HP 0x00000000) @ 
 > 0x000000003fb36b18
 > (XEN) ACPI: DBGP (v001     HP   zx6000 0x00000000 HP 0x00000000) @ 
 > 0x000000003fb36b68
 > (XEN) ACPI: MADT (v001     HP   zx6000 0x00000000 HP 0x00000000) @ 
 > 0x000000003fb36c28
 > (XEN) ACPI: SPMI (v004     HP   zx6000 0x00000000 HP 0x00000000) @ 
 > 0x000000003fb36ba0
 > (XEN) ACPI: CPEP (v001     HP   zx6000 0x00000000 HP 0x00000000) @ 
 > 0x000000003fb36bf0
 > (XEN) ACPI: SSDT (v001     HP   zx6000 0x00000006 INTL 0x02012044) @ 
 > 0x000000003fb33870
 > (XEN) ACPI: SSDT (v001     HP   zx6000 0x00000006 INTL 0x02012044) @ 
 > 0x000000003fb33a50
 > (XEN) ACPI: SSDT (v001     HP   zx6000 0x00000006 INTL 0x02012044) @ 
 > 0x000000003fb33da0
 > (XEN) ACPI: SSDT (v001     HP   zx6000 0x00000006 INTL 0x02012044) @ 
 > 0x000000003fb347c0
 > (XEN) ACPI: SSDT (v001     HP   zx6000 0x00000006 INTL 0x02012044) @ 
 > 0x000000003fb351e0
 > (XEN) ACPI: SSDT (v001     HP   zx6000 0x00000006 INTL 0x02012044) @ 
 > 0x000000003fb35c00
 > (XEN) ACPI: SSDT (v001     HP   zx6000 0x00000006 INTL 0x02012044) @ 
 > 0x000000003fb36620
 > (XEN) ACPI: SSDT (v001     HP   zx6000 0x00000006 INTL 0x02012044) @ 
 > 0x000000003fb36800
 > (XEN) ACPI: SSDT (v001     HP   zx6000 0x00000006 INTL 0x02012044) @ 
 > 0x000000003fb368f0
 > (XEN) ACPI: DSDT (v001     HP   zx6000 0x00000007 INTL 0x02012044) @ 
 > 0x0000000000000000
 > (XEN) SAL 3.1: HP version 2.31
 > (XEN) SAL Platform features: None
 > (XEN) SAL: AP wakeup using external interrupt vector 0xff
 > (XEN) No logical to physical processor mapping available
 > (XEN) avail:0x1180c60000000000, 
 > status:0x60000000000,control:0x1180c00000000000, vm?0x0
 > (XEN) No VT feature supported.
 > (XEN) cpu_init: current=f0000000040b4000, 
 > current->domain->arch.mm=0000000000000000
 > (XEN) vhpt_init: vhpt size=0x1000000, align=0x1000000
 > (XEN) vhpt_init: vhpt paddr=0x27e000000, end=0x27effffff
 > (XEN) ACPI: Local APIC address e8000000fee00000
 > (XEN) ACPI: LAPIC_ADDR_OVR (address[00000000fee00000])
 > (XEN) ACPI: LSAPIC (acpi_id[0x00] lsapic_id[0x00] lsapic_eid[0x00] enabled)
 > (XEN) CPU 0 (0x0000) enabled (BSP)
 > (XEN) ACPI: LSAPIC (acpi_id[0x01] lsapic_id[0x01] lsapic_eid[0x00] enabled)
 > (XEN) CPU 1 (0x0100) enabled
 > (XEN) ACPI: IOSAPIC (id[0x0] address[00000000fed20800] gsi_base[16])
 > (XEN) ACPI: IOSAPIC (id[0x1] address[00000000fed22800] gsi_base[27])
 > (XEN) ACPI: IOSAPIC (id[0x2] address[00000000fed24800] gsi_base[38])
 > (XEN) ACPI: IOSAPIC (id[0x3] address[00000000fed26800] gsi_base[49])
 > (XEN) ACPI: [APIC:0x06] ignored 3 entries of 7 found
 > (XEN) 2 CPUs available, 2 CPUs total
 > (XEN) ia64_mca_init() skipped (Machine check abort handling)
 > (XEN) Cannot handle page request order 14!
 > (XEN) 
 > (XEN) ****************************************
 > (XEN) Panic on CPU 0:
 > (XEN) Not enough memory to bootstrap Xen.
 > (XEN) ****************************************
 > (XEN) 
 > (XEN) Reboot in five seconds...
 > (XEN) machine_restart called: spinning....
 > 
 > 


_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  RE: [Xen-ia64-devel] [PATCH][RFC]discontig memory support, Kouya SHIMURA
Next by Date:  RE: [Xen-ia64-devel] [PATCH][RFC]discontig memory support, Tian, Kevin
Previous by Thread:  Re: [Xen-ia64-devel] [PATCH][RFC]discontig memory support, Alex Williamson
Next by Thread:  [Xen-ia64-devel] [PATCH] discontig memory support, Kouya SHIMURA
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy