Chris Wright wrote:
> * Zachary Amsden (zach@vmware.com) wrote:
>   
>> Create a configurable hole in the linear address space at the top
>> of memory.  A more advanced interface is needed to negotiate how
>> much space the hypervisor is allowed to steal, but in the end, it
>> seems most likely that a fixed constant size will be chosen for
>> the compiled kernel, potentially propagated to an information
>> page used by paravirtual initialization to determine interface
>> compatibility.
>>
>> Signed-off-by: Zachary Amsden <zach@vmware.com>
>>
>> Index: linux-2.6.16-rc3/arch/i386/Kconfig
>> ===================================================================
>> --- linux-2.6.16-rc3.orig/arch/i386/Kconfig	2006-02-22 16:09:04.000000000 -0800
>> +++ linux-2.6.16-rc3/arch/i386/Kconfig	2006-02-22 16:33:27.000000000 -0800
>> @@ -201,6 +201,15 @@ config VMI_DEBUG
>>  
>>  endmenu
>>  
>> +config MEMORY_HOLE
>> +	int "Create hole at top of memory (0-256 MB)"
>> +	range 0 256
>> +	default "64" if X86_VMI
>> +	default "0" if !X86_VMI
>>     
>
> Deja-vu ;-)  And still works in context of Xen, but we've just let the
> subarch define the __FIXADDR_TOP.  Having it be dynamic could be
> interesting.
>   

Here's dynamic.  I hope it still applies.