[Crash-utility] ramdump support for va_bits_actual

[vinayak menon]

Hi Dave, zhaoqianli

> Yeah, that looks reasonable.  But what about the parallel discussion re: vmemmap_start?
>
>   https://www.redhat.com/archives/crash-utility/2020-April/msg00064.html

I have picked up the vmemmap_start as 4th patch. The physvirt_offset
based VTOP is already
part of patchset 1. I hope I have not missed anything from those
recommended by Zhaogianli.

>
> Can you send in an updated patch set with all fixes applied?

PFA.

Thanks,
Vinayak
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0003-get-CONFIG_ARM64_VA_BITS-from-config.patch
Type: application/octet-stream
Size: 1770 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/crash-utility/attachments/20200421/fffde707/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-fix-the-calculation-of-_stext_vmlinux-for-ramdumps.patch
Type: application/octet-stream
Size: 783 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/crash-utility/attachments/20200421/fffde707/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-fix-the-arm64-vtop-and-ptov-calculations.patch
Type: application/octet-stream
Size: 3607 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/crash-utility/attachments/20200421/fffde707/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0004-fix-vmemmap_start.patch
Type: application/octet-stream
Size: 815 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/crash-utility/attachments/20200421/fffde707/attachment-0003.obj>