Re: [Xen-devel] 32bit-pv-VM 128G memory limited

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" <jsong@xxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
> 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.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

[Xen-devel] [PATCH] Disable vPMU feature by default, Shan, Haitao

Next by Date:

Re: [Xen-devel] Need help in debugging partially blocked hypervisor, Dietmar Hahn

Previous by Thread:

Re: [Xen-devel] 32bit-pv-VM 128G memory limited, Keir Fraser

Next by Thread:

Re: [Xen-devel] 32bit-pv-VM 128G memory limited, Keir Fraser

Indexes:

[Date] [Thread] [Top] [All Lists]