Hari Bathini writes:
> On 15/07/20 8:09 am, Thiago Jung Bauermann wrote:
>>
>> Hari Bathini writes:
>>
>
>
>
>>> +/**
>>> + * __locate_mem_hole_top_down - Looks top down for a large enough memory
>>> hole
>>> + * in the memory regions between buf_min &
>>> b
On 15/07/20 8:09 am, Thiago Jung Bauermann wrote:
>
> Hari Bathini writes:
>
>> +/**
>> + * __locate_mem_hole_top_down - Looks top down for a large enough memory
>> hole
>> + * in the memory regions between buf_min &
>> buf_max
>> + *
Thiago Jung Bauermann writes:
> Hari Bathini writes:
>
>> diff --git a/arch/powerpc/include/asm/crashdump-ppc64.h
>> b/arch/powerpc/include/asm/crashdump-ppc64.h
>> new file mode 100644
>> index 000..90deb46
>> --- /dev/null
>> +++ b/arch/powerpc/include/asm/crashdump-ppc64.h
>> @@ -0,0 +
Hari Bathini writes:
> diff --git a/arch/powerpc/include/asm/crashdump-ppc64.h
> b/arch/powerpc/include/asm/crashdump-ppc64.h
> new file mode 100644
> index 000..90deb46
> --- /dev/null
> +++ b/arch/powerpc/include/asm/crashdump-ppc64.h
> @@ -0,0 +1,10 @@
> +/* SPDX-License-Identifier: GPL
crashkernel region could have an overlap with special memory regions
like opal, rtas, tce-table & such. These regions are referred to as
exclude memory ranges. Setup this ranges during image probe in order
to avoid them while finding the buffer for different kdump segments.
Override arch_kexec_loc
