On Tue, Jun 18, 2019 at 01:43:00AM +, Lendacky, Thomas wrote:
> Yes and no... it doesn't say how it is done, namely through the use of
> memblock_reserve() calls and when and where those occur.
Ah ok, so you found that out and documented it now. Good.
:-)
--
Regards/Gruss,
Boris.
Good
On 6/17/19 5:47 AM, Borislav Petkov wrote:
> On Fri, Jun 14, 2019 at 09:15:18PM +, Lendacky, Thomas wrote:
>> The memory occupied by the kernel is reserved using memblock_reserve()
>> in setup_arch(). Currently, the area is from symbols _text to __bss_stop.
>> Everything after __bss_stop must
On Fri, Jun 14, 2019 at 09:15:18PM +, Lendacky, Thomas wrote:
> The memory occupied by the kernel is reserved using memblock_reserve()
> in setup_arch(). Currently, the area is from symbols _text to __bss_stop.
> Everything after __bss_stop must be specifically reserved otherwise it
> is discar
On 06/14/19 at 09:15pm, Lendacky, Thomas wrote:
> The memory occupied by the kernel is reserved using memblock_reserve()
> in setup_arch(). Currently, the area is from symbols _text to __bss_stop.
> Everything after __bss_stop must be specifically reserved otherwise it
> is discarded. This is not c
After applied the patch series(v2), the kexec-d kernel and the kdump kernel can
successfully boot.
Thanks.
Tested-by: Lianbo Jiang
在 2019年06月15日 05:15, Lendacky, Thomas 写道:
> The memory occupied by the kernel is reserved using memblock_reserve()
> in setup_arch(). Currently, the area is from sy
On 6/14/19 2:15 PM, Lendacky, Thomas wrote:
> + /*
> + * The memory occupied from _text to here, __end_of_kernel_reserve, is
> + * automatically reserved in setup_arch(). Anything after here must be
> + * explicitly reserved using memblock_reserve() or it will be discarded
> +
6 matches
Mail list logo
