On Wed, Jan 30, 2013 at 2:41 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 01/30/2013 02:29 PM, Eric W. Biederman wrote: > The bigger question is if we need a separate value from the current > E820_RESERVED_KERN. Since it is always easier to have multiple values > with the same semantics than it is to have too few, I would still prefer > we added a new E820_RESERVED_KDUMP, which would then be 2000000001. current for E820_RESERVED_KERN: during filling memblock.memory, it will be treated as E820_RAM, and also memblock.reserve already have entries for them. For E820_RESERVED_KDUMP, looks only usage is for kernel to find saved_max_pfn. So we may have to separate them.
