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] Regression: [IA64] Saner dom0 memory and cpudefault

To: Alex Williamson <alex.williamson@xxxxxx>
Subject: Re: [Xen-ia64-devel] Regression: [IA64] Saner dom0 memory and cpudefaults
From: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Date: Tue, 4 Sep 2007 11:18:19 +0900
Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 05 Sep 2007 08:19:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1188451986.6474.9.camel@lappy>
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: <82C666AA63DC75449C51EAD62E8B2BEC14DED9@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1188451986.6474.9.camel@lappy>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.2.1i
On Wed, Aug 29, 2007 at 10:33:06PM -0700, Alex Williamson wrote:
> On Thu, 2007-08-30 at 13:17 +0800, Duan, Ronghui wrote:
> > I make a new domain0 kernel with CONFIG_IA64_DIG .It still panic.
> 
> > (XEN) Maximum permitted dom0 size: 3973MB
> 
>    It looks like we need to reduce dom0 memory by the size of the
> contiguous region the swiotlb makes.  By default, this is 64MB, so
> booting with dom0_mem=3909M will probably work (at least that's the
> difference on my 2G system).  Unfortunately the swiotlb can be resized
> by a command line option, so statically removing 64MB isn't a very good
> solution.  Perhaps we need a more efficient create_contiguous_region()?

- When the memory exchange hypercall fails,
  kick balloon(or do something similar) and try the hypercall again.
  Although the ballooning makes the posibility higher, it doesn't gurantee.

- Start dom0 with minimal memory (e.g. 128MB) assigned and other memory
  is ballooned out when booting.
  After dom0 allocating contiguous region, populate the unassigned memory.

Any other ideas?
Given that dom0_mem is the easy work around, is it worth while
to make effort?

-- 
yamahata

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