Integrate the IPC Logging extraction script module into
linux-ramdump-parser-v2.

Move ipc_logging.py from into the linux-ramdump-parser-v2/parsers
directory, and create a relative symbolic link in the original location.
Add a new file, ipc_logging_ramparse.py, which performs the actual
integration.

Change-Id: If0db4f82814a644094af7ebd0e4290dd145f94ac

The constructor currently used in ramparse.py to initialize the RamDump
object has a very long argument list. This list can be shortened by
passing the options object to the constructor, rather than enumerating
every member of the options object as a separate argument.

Pass the options object to the RamDump constructor instead of passing
each member as a separate argument.

Change-Id: I7cbf173232838dd8f9fdbdad0e2b7336ad8fc07b

It is necessary to allow the script to get included as a module by other
scripts. Currently, the logging and output directory configuration are
performed in the script's main function, and the options from parsing
the command line are not passed from function to function.

Create two new functions for the logging and output directory
configuraiton, and pass the command-line options object to each
function that uses it. This allows the options to be passed in from
other scripts.

Change-Id: Ibf34d72cd70620bcbcc00e48141a87a721b1f987

When processing a log page, the page header size depends on the size of
internal structures and pointers that can vary with machine size
(32-bit or 64-bit). This information is stored in the logging context
during automated extraction (i.e. when the "parse" command is used), but in
the "test" command only the log pages are provided, so the necessary
information is not present.

The correct page header size can be determined if the version of IPC
Logging and the architecture size (32-bit or 64-bit) are known. Store
the possible header sizes as module variables, modify the test command
to accept the IPC Logging version, and modify the script to take an
argument denoting if the logs are interpreted as 32-bit or 64-bit.
In the "test" command, select the correct header size using the IPC
Logging version and architecture size.

Change-Id: I53ccdc7982b5cfd79dfb6c36d982037b3b2a3955

When parsing IPC logs, sometimes a bogus log page header is present which
overwrites the bit used to discern whether or not the log page is version
0. This causes the script to read the version as being 1 or greater, and
the script then asserts after failing to find a log context for the page.
In general, header corruption like this may cause other issues that could
lead to the context not being found, which currently aborts the script.

Modify the script to continue parsing the logs as logs of an unknown
version in this case. If the header is valid, the proper version will be
parsed from it, allowing parsing to continue normally.

Change-Id: I02ae617980f817705224b7b02926a9f576dd88e6

Add support for detecting the 8996 target and parsing the dumps.

Change-Id: I8288790eaa78b07f3c2b70e97e16c55534f5b736

Do not use hardcoded value for TTBR1. Compute TTBR1 value using
swapper_pg_dir_addr and phys_offset variables dynamically.

Change-Id: Ia9b4704b07e933c686e366ed0af8230be1d97e9c

Running launch_t32.bat with newer T32 gives syntax errors without newlines
before "SCREEN=" and "PRINTER=WINDOWS" strings in t32_config.t32. Add
newlines before these strings to avoid T32 syntax errors.

Change-Id: I53ffd02d4c86959804a89bd744bf1ce7f42f163c

Parse and print lpm levels and spm data for cpus and clusters.

Change-Id: Ied79d9317dff92cfe99d5a8fe9ee0539b8c62b4d

Rename a variable to better describe its purpose.
Change the size of the L2 cache for 8992 to the correct value.
Update version information for 8994.

Change-Id: Ie0bf7e9ff257555cc40467918d258b05bf4c2ada

If user specified --force-hardware, then skip the socinfo parsing to
determine the hardware/board information. The user is warned about
using the force-hardware option any way.

Checking for valid swapper_pg_dir in the vmlinux also ensures that
the parsing doesn't trip over when --force-hardware is used along with
a bad or stripped vmlinux.

Change-Id: Icce1556b39a7533418668a7f38af30f4463c32e5

Add support for detecting 8929 target and parsing the ramdumps.

Change-Id: I044a93570b82857850957c8b8ebd23df7a9e0389

Print the workqueue information for 3.14 kernel.

Change-Id: Id40503c9f8ad2fc23cff587553e66e0a6a0406fd

The format of the roareadiff output was recently changed, in
[99a8ae9d: "linux-ramdump-parser-v2: Update roareadiff for arm64"].
That change introduced the possibility of printing non-printable
characters in string representations of the memory dumps.  Fix this by
outputting a `.' for non-printable characters.

Change-Id: I1efd0775fac89618f43986523c6a9207afed7e5e

When attempting to locate panicking tasks via the
"--check-for-panic" option, the taskdump parser currently attempts
to exhaustively check every task in kernel task list to see if it
panicked.

To improve performance, task checking can be limited to tasks that
were listed as currently running at the time the RAM dump was
collected. Other tasks do not need to be checked because a
panicking process is expected to disable IRQs and preemption after
entering the panic handler, and therefore will not yield to any
other tasks executing on the same CPU prior to resetting.

Change-Id: I51d7b979f918e21bfdd2adf2a3429883f11bab6a

The stack and pointer sizes are different on arm64. Update
accordingly.

Change-Id: I262c79ea81671d97fd8bbc8343267cc3bc8c3d38
Acked-by: Kosuke Shitaba <kshibata@qti.qualcomm.com>

Consider the case of a nentries==8 and 3 cpus.
Numbers in parenthesis are the equivalent location in the circular buffer.
CPU:   Index0:  Index1: Index2: Index3:
0      0        3       6       9(1)
1      1        4       7       10(2)
2      2        5       8(0)

The current design is only appropriate for the case where
nentries % nrcpus == 0.

Fix this issue by incrementing the index by (nentries % nrcpus)
each time circular buffer wraps around.

CPU:   Index0:  Index1: Index2:
0      0        3       6+2==8(0)
1      1        4       7+2==9(1)
2      2        5       8+2==10(2)

Change-Id: I439fb540fc2c437c6b642d18aa9683603c270f36

The elf header file is different for arm64. Update it so that
the roareadiff feature can be used on 64bit targets.

Change-Id: Ica4424a6ea9d2e599e1a157353aa5f702a5e4bf8
Acked-by: Kosuke Shitaba <kshibata@qti.qualcomm.com>

The imem start address was missing for 9635. Add it.

Change-Id: Iea221df9f91e7d7ac54393f50ce0ea6b257e7a66

Add a parser which parses relevant thermal device information.

Change-Id: I4edde5a59ba5150cabc282716a42b7084dadda62