mirror of
https://github.com/ibm-s390-linux/s390-tools.git
synced 2026-08-05 02:14:52 +00:00
At the moment the memory range of processed vmdump always corresponds to the highest defined byte (q v storage) obtained from Address Space Information Block ignoring memory ranges specified in CP vmdump command. This might lead to the invalid dump size calculation upon conversion to s390 format. Use Requested Range Table from ASIZBK to identify actual memory ranges being dumped. Consider the end of the highest memory range as a vmdump upper limit (dump memory size). In case no range table entries present fall back to the original method using 'storage_size_def_store' value. Signed-off-by: Mikhail Zaslonko <zaslonko@linux.ibm.com> Reviewed-by: Alexander Egorenkov <egorenar@linux.ibm.com> Signed-off-by: Steffen Eiden <seiden@linux.ibm.com>
16 KiB
16 KiB