Hari Bathini writes:
> On 04/09/19 5:00 PM, Michael Ellerman wrote:
>> Hari Bathini writes:
>>> Firmware uses 32-bit field for region size while copying/backing-up
>>
>> Which firmware exactly is imposing that limit?
>
> I think the MDST/MDRT tables in the f/w. Vasant, which component is that?
>
On 04/09/19 5:00 PM, Michael Ellerman wrote:
> Hari Bathini writes:
>> Firmware uses 32-bit field for region size while copying/backing-up
>
> Which firmware exactly is imposing that limit?
I think the MDST/MDRT tables in the f/w. Vasant, which component is that?
>> +/*
>> + * Firmwa
Hari Bathini writes:
> Firmware uses 32-bit field for region size while copying/backing-up
Which firmware exactly is imposing that limit?
> memory during MPIPL. So, the maximum copy size for a region would
> be a page less than 4GB (aligned to pagesize) but FADump capture
> kernel usually needs
Firmware uses 32-bit field for region size while copying/backing-up
memory during MPIPL. So, the maximum copy size for a region would
be a page less than 4GB (aligned to pagesize) but FADump capture
kernel usually needs more memory than that to be preserved to avoid
running into out of memory error
