From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Williamson Subject: RE: Re: [PATCH] Disable auto-balloon on ia64 Date: Mon, 22 May 2006 08:25:45 -0600 Message-ID: <1148307945.13851.118.camel@localhost> References: <571ACEFD467F7749BC50E0A98C17CDD8094E7C82@pdsmsx403> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <571ACEFD467F7749BC50E0A98C17CDD8094E7C82@pdsmsx403> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Tian, Kevin" Cc: Charles Coffing , xen-devel , xen-ia64-devel List-Id: xen-devel@lists.xenproject.org On Mon, 2006-05-22 at 21:33 +0800, Tian, Kevin wrote: > OK, the question by far is that ia64 describes the memory hierarchy > presented to domain by d->max_pages. Before balloon is ready, we at > least need to ensure all frames covered by d->max_pages allocated for > target domain. Then there're two alternatives: > - Keep the first piece of change on increase_reservation, which > ensures all pages including extra spaces allocated immediately. > - Pass the extra memory size to xen at arch_set_info_guest, and > then change xen/ia64 to only tell domain maximum pfns as > d->max_pages-extra_size > > Both need to be changed again later if balloon is ready. So I prefer to > option I which is simpler and can help Alex to do sync quickly. How do > you think? I agree, I think we can get by with only the ia64 changes in the increase_reservation call. The other option seems more fragile. Keir, would you include the first chunk of Kevin's patch as a temporary solution until we have better ballooning support on xen/ia64 (should be soon)? Thanks, Alex -- Alex Williamson HP Linux & Open Source Lab