How does kdump deal with trampoline allocation?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"H. Peter Anvin" <hpa at zytor.com> writes:

> 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.

What motivates your trampoline rewrite?

Eric



[Index of Archives]     [LM Sensors]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux