When calculating pfn_to_page, the pfn needs to be offset before
indexing into the array. Account for this.

Change-Id: If207447a91537ab7670058fede65473d3ea93281

When checking for rodata differences, we scan the ELF headers of
the vmlinux. Newer vmlinux files seem to have extra ELF headers
with addresses outside the valid mapped range. If we encounter
one of those headers and read an invalid address, skip it.

Change-Id: I2a8af784df7216bf9d890be42eec8599fbaa7f72

Commit 3d6a90bd
(linux-ramdump-parser-v2: Don't use ram start address in socinfo)
corrected the case for --auto-dump detection but broke the case of
specifying ram files manually with addresses. When specifying the
addresses manually, the addresses given are correct so the ram start
does need to be added. Correct the code to add the offset by default
but not add when doing autodetection.

Change-Id: I50d54a932210afeace49a898dd819dc46c3e3aa1

The page_tracking code is missing the page_buddy import. Import it.

Change-Id: I0030305e51f470cdd379f8237bb15c912601e861

Ram dumps are now being generated for 64-bit ramdumps. Update the
parser to account for this.

Change-Id: I54a354f39701ad96dd7b81010ec6c5989dd471ad

array_index properly accounts for the changes in sizes of array
items. Use it.

Change-Id: I0dd0fb70f968a2b837a3d2aa02ae3d02ad5a578a

Several of the values used in printing the runqueues are actually
ints, not words. Correct the type used.

Change-Id: I1b700a679d1dee04d2de28e9ec8d8e343e03fbe4

The ramdump APIs now provide functions for accessing per CPU
variables. Use those instead of writing the same code over again.

Change-Id: Ia34a9b1a279e8385bdc08b2612e59fdfe0e1f958

The IRQ parsing makes some non-generic assumptions about the sizes
of various fields in the structures. Update the parsing to use better
types.

Change-Id: I914f6104e7f914aa941b301a71c38182806e11cc

Rather than assume a text offset, use one that is already found
as a symbol.

Change-Id: I1ad608085984bb0b658d371858cf01e0732811a3

The socinfo code depends on fixed size types which may be different
from the word size. Update the parsing accordingly.

Change-Id: I7c4a23f92e13349c9ebd67aa69438d1a55aba721

The PAGE_OFFSET (traditionally 0xc0000000) may change depending on
architecture version. Switch it to be a property of the ramdump.

Change-Id: Ide04649f59005f39e84d0caa5edab0f46e691b3f

unwind tables may not be used on all dumps. Support unwinding the
old fashioned way with framepointers.

Change-Id: I978c604dc0974eb6930249e47a205e3d9d37c249

Several of the fields of the task are not being read out as
'true size'. Use more appropriate functions. At the same time,
factor out the reading of pc/fc/sp into a ramdump specific
functionality since that code may be architectur specific.

Change-Id: I5d7bd14031a4431aa665207e8e31e3ecb7dd1cdb

The sizes for reading some of the structures of the binary logbuf
do not match exactly. Switch to explicitly sized functions due to
size changes across architectures.

Change-Id: Iae09a069f5cb641c61a63d864ec59d0c8359e65b

The binary logbuf now uses *log_buf instead of __log_buf to find the
log buffer. Correctly dereference the pointer.

Change-Id: If3cce2105ee12a81098abe1c4c2fe736550cadff

When tracing with read_physical, the result of what was read is printed.
The result may contain unprintable characters which wreak havok on
terminals. re-use the cleanupString function which is already in use
in several places to make the output readable.

Change-Id: I1a62c88f1d51038ba2c429d8ec918c58d39af4bf

The return size of read_word may change depending on the architecture.
Add functions to read specific types and sizes.

Change-Id: I3b9b11c263bf684a8e3783a10dcdc770a6a1b25e

The 8916 board is now generating ramdumps. Add support to parse
these dumps.

Change-Id: I9920544031443ce97f95824c8927b50e0927d5c1