From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] Memory pool for paravirtual guest in memory over 128G system Date: Tue, 01 Dec 2009 13:33:25 +0000 Message-ID: References: <26570558.post@talk.nabble.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <26570558.post@talk.nabble.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "James (song wei)" , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 30/11/2009 07:43, "James (song wei)" wrote: > the main idea of this patch is: > 1) The admin sets aside some memory below 128G for 32-bit paravirtual domain > creation (via dom0_mem=- in kernel comand line). > 2) The admin also explicitly states to the tools (i..e xend) how much memory > is supposed to be left untouched by 64-bit domains > 3) If a 32-bit pv DomU gets created, no ballooning ought to be necessary > (since if it is, no guarantee can be made about the address range of the > memory ballooned out), and memory gets allocated from the reserved range. > 4) Upon 64-bit (or 32-bit HVM or HVM) DomU creation, the tools determine the > amount of memory to be ballooned out of Dom0 by adding the amount needed for > the new guest and the amount still in the reserved pool (and then of course > subtracting the total amount of memory the hypervisor has available for > guest use). > > Signed-off-by: james song (wei) The patch is corrupted (line wrapped). You need to re-send as an attachment. Please include the changeset comment and sign-off again. -- Keir