All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Charles Coffing" <ccoffing@novell.com>
To: Yunhong Jiang <yunhong.jiang@intel.com>, xen-devel@lists.xensource.com
Subject: RE: [PATCH]  Fix auto-ballooning of dom0 for HVM domains
Date: Fri, 19 May 2006 13:59:09 -0600	[thread overview]
Message-ID: <446DCFE0.D169.003C.0@novell.com> (raw)
In-Reply-To: <A8F9FF3706D1A5479EF62192B976DB441C0594@pdsmsx401.ccr.corp.intel.com>

> On Thu, May 18, 2006 at 10:23 PM, in message
<A8F9FF3706D1A5479EF62192B976DB441C0594@pdsmsx401.ccr.corp.intel.com>,
"Jiang, Yunhong" <yunhong.jiang@intel.com> wrote: 
> Hi, Charles
> 	Just one suggestion, for  xen- hvm- auto- balloon.diff, how
about
> change 
>              xc.domain_setmaxmem(self.domid, m)
>  
> to 
>              xc.domain_setmaxmem(self.domid, self.info['memory'] *
1024)

Ideally, yes, I would agree.  But later, in qemu, another
increase_reservation() is called.  If I make the suggested change, I
suspect that qemu will fail to get its memory.

Or is this upper limit not checked when increase_reservation() is
called from dom0?

  parent reply	other threads:[~2006-05-19 19:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19  4:23 [PATCH] Fix auto-ballooning of dom0 for HVM domains Jiang, Yunhong
2006-05-19 15:15 ` Ewan Mellor
2006-05-19 19:59 ` Charles Coffing [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-22  9:09 Tian, Kevin
2006-05-22  8:51 Tian, Kevin
2006-05-22  9:06 ` Keir Fraser
2006-05-22 14:51 ` Charles Coffing
2006-05-22 15:03   ` Keir Fraser
2006-05-22 15:15     ` Charles Coffing
2006-05-19 16:29 Jiang, Yunhong
2006-05-18 17:04 Charles Coffing
2006-05-18 18:11 ` Charles Coffing

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=446DCFE0.D169.003C.0@novell.com \
    --to=ccoffing@novell.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yunhong.jiang@intel.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.