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-ia64-devel] Re: [Xen-devel] Re: [PATCH] Disable auto-balloon on ia6

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: [Xen-ia64-devel] Re: [Xen-devel] Re: [PATCH] Disable auto-balloon on ia64
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 22 May 2006 10:50:31 +0100
Cc: Charles Coffing <ccoffing@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 22 May 2006 02:51:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <de6a6f8a49c55295ad1cedb0718099ef@xxxxxxxxxxxx>
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: <571ACEFD467F7749BC50E0A98C17CDD8094E7C7F@pdsmsx403> <de6a6f8a49c55295ad1cedb0718099ef@xxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 22 May 2006, at 10:37, Keir Fraser wrote:

We just need to reverse the whole change for ia64, since both domU and domVTI are insert a hole by this auto-balloon patch. Due to missing balloon support on xen/ia64 as you said, both domU and domVTI failed due to this change.

The first patch that you work around seems okay to me. That is, it seems correct that we make initial reservation exclude 'getDomainMemory headroom'. Shouldn't ia64 reserve extra memory as it needs it, as x86 does, rather than up front?

The second bit of your workaround, which applies to getDomainMemory: I'll wait and see if Charles has anything to say, but otherwise I'll remove the code that adds the extra slack entirely.

Thinking about it, that slack might have been added to give enough space for shadow page tables for live migration. Also, it shouldn't give you any problems if you weren't allocating headroom up front -- if you can fix ia64 to allocate the extra memory as needed then you shouldn't need either of your workarounds?

 -- Keir

Xen-ia64-devel mailing list