All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: Charles Coffing <ccoffing@novell.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	xen-ia64-devel <xen-ia64-devel@lists.xensource.com>
Subject: RE: Re: [PATCH] Disable auto-balloon on ia64
Date: Mon, 22 May 2006 08:25:45 -0600	[thread overview]
Message-ID: <1148307945.13851.118.camel@localhost> (raw)
In-Reply-To: <571ACEFD467F7749BC50E0A98C17CDD8094E7C82@pdsmsx403>

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

  reply	other threads:[~2006-05-22 14:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-22 13:33 [Xen-devel] Re: [PATCH] Disable auto-balloon on ia64 Tian, Kevin
2006-05-22 14:25 ` Alex Williamson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-22  9:06 Tian, Kevin
2006-05-22  9:37 ` Keir Fraser
2006-05-22  9:50   ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1148307945.13851.118.camel@localhost \
    --to=alex.williamson@hp.com \
    --cc=ccoffing@novell.com \
    --cc=kevin.tian@intel.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-ia64-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.