How does kdump deal with trampoline allocation?

[H. Peter Anvin]

On 12/27/2010 11:40 PM, Eric W. Biederman wrote:
>>
>> OK, that's straightforward.  That presumably means that the low 640K is
>> marked unused in the memory map that memblock sees during early startup.
>>  That fits very cleanly with the patches I'm doing.
> 
> Additionally we typically start with maxcpus=1 so we don't strictly
> need the trampoline to start other cpus.
> 

Well, the trampoline is optional only on 32 bits, and with my changes,
it would be unconditional.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.