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

Re: [Xen-ia64-devel] [RFC] Change .config of dom0 for

To: Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>
Subject: Re: [Xen-ia64-devel] [RFC] Change .config of dom0 for
From: Alex Williamson <alex.williamson@xxxxxx>
Date: Wed, 17 Jan 2007 17:13:54 -0700
Cc: ia64 Fedora Core Development <fedora-ia64-list@xxxxxxxxxx>, xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 17 Jan 2007 16:13:27 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <34C73A9500D158takebe_akio@xxxxxxxxxxxxxx>
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: <34C73A9500D158takebe_akio@xxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 2007-01-18 at 09:10 +0900, Akio Takebe wrote:
> Hi, Isaku and all
> 
> When I boot dom0 with dom0_mem=31G, dom0 use about 2GB memory after booting.
> I check why dom0 use 2GB, then I found the following message at the boot time.
> 
>  Aperture:     64 megabytes
>  Kernel range: 0xe0000000052b4000 - 0xe0000000092b4000
>  Address size: 30 bits
> Memory: 30649984k/32456704k available (10480k code, 1805472k reserved, 4361k 
> data, 288k init) <------- !!!reserved 1.8GB!!!
> McKinley Errata 9 workaround not needed; disabling it
...
> 
> Should we change .config of dom0?
> Or should we fix other code?
> 
> I think we should change .confing,
> I use CONFIG_DISCONTIGMEM and CONFIG_VIRTUAL_MEM_MAP,
> but we may use SPARSEMEM.
> (I'll check SPARSEMEM soon.)

   I agree, we're presenting dom0 with a memory map similar to bare
metal hardware.  The contiguous memory handlers aren't going to be able
to deal with that efficiently on many ia64 platforms.  Thanks,

        Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.


_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel

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