From mboxrd@z Thu Jan 1 00:00:00 1970 From: "James (song wei)" Subject: Re: 32bit-pv-VM 128G memory limited Date: Mon, 2 Nov 2009 22:14:03 -0800 (PST) Message-ID: <26159985.post@talk.nabble.com> References: <4AEF29A30200002000070459@novprvlin0050.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Keir could you please say it in more detail? Thanks, James Keir Fraser-3 wrote: > > This should all already happen by default. > > -- Keir > > On 02/11/2009 07:49, "James Song" wrote: > >> Hi, >> >> >> Since 32-bit pv-domUs require memory below the 128G boundary (IIRC) >> but >> tools don't enforce this. So we need a "memory pool" for 32bit pv-domUs. >> When starting a 32-bit domU, allocate memory from this pool. If starting >> a >> 64-bit domUs or 32bit hvm dom (which don't suffer the 128G boundary >> limitation), allocate memory from above the boundary first, only >> allocating >> from the lower pool when needed. >> >> Thanks, >> James (Song Wei) >> > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > > -- View this message in context: http://old.nabble.com/32bit-pv-VM-128G-memory-limited-tp26159377p26159985.html Sent from the Xen - Dev mailing list archive at Nabble.com.