Describe the cache format used in msmcobalt.

CRs-Fixed: 983532
Change-Id: I4dc88fc7f29770e892a29a7e48e8a79d883c9b06

Describe the cache format used for 8937, 8953 and 8917.

Change-Id: Ie877173bc0fa6ea01e7daf1825720c5601a6f82a

Add support for detecting msm8917 target
and parsing the ramdumps.

Change-Id: I8014abc0f52a459bdcb7d94b09f4826ded74542c

Add support for detecting APQ8953 target
and parsing the ramdumps.

Change-Id: I9529d2187ce70401d57ca14c4294c4a7cee2c810

Add support for detecting msm8953 target and parsing the ramdumps.

Change-Id: Ie0ddf18e46ab20d0419609c1f84f2d5b0667be9c

Add '--kaslr-offset' option.  This specifies the offset for loading symbols
for a KASLR-enabled kernel.

Change-Id: I208d964ea3ca58536a0b80a32b4e334c73aae534

The register_parser decorator function is one of the most important
public functions in the codebase.  Improve its documentation by adhering
to Python docstring standards, including parameter documentation.

Change-Id: Ibbde495e799dcd550810635e591b24e9eba8cb28

It can be convenient to automatically re-generate documentation as the
source files are edited.  Add a make target for this.

Change-Id: Id3f26e0978bc50f5851200fb2c3d0fe94e2d4d41

Some of our module documentation is a bit lacking.  Fix this by filling
in some docstrings and add then adding some pointers to existing
modules/functions in the docs.

Change-Id: Ibf714225f1fc185be916e514861540fd98cb2de5

Support is required for version 3 of IPC Logging, which increases the
maximum size of a logging context name from 20 to 32.

Add this support.

Change-Id: Id7c4b30efd2499cbad99db5d00a5008198047c72

Along with the unpack() functions which are present for parsing, the
classes which parse individual log messages also have pack() functions
which are used for recreating the log messages in their binary form.
These functions are used for unit testing.

In the TSVQTimer pack() function, incorrect math is performed on the
result before it is returned. In the LogMessageString pack() function, a
QTimer object is manipulated before it is created.

Fix these errors.

Change-Id: I5c288ddd53e468368c3663bdc9c1134a5f694865

Parse out the APM state that has been configured so that it can
be compared against the VDD supply voltage to ensure correct
functionality.

Change-Id: Iabf78a6799015861379a39d93e59289a489e1510

Some of the documentation in register.py doesn't render nicely when
built with Sphinx.  Fix this.

Change-Id: Ifdb0da6c21f092b58c51be8f566a7a4e5cab984b

There's a comment in gdbmi that doesn't adhere to the canonical Python
prompt format.  Fix this.

Change-Id: I0a369669cc4c5aa5ac318da0f4949aba84bed02d

The parser is a large enough project that some proper documentation is
needed.  In order to facilitate contribution to the ramdump parser, add
some documentation with a standard sphinx Makefile to build it.

Change-Id: Idfbc65173dc082c3144ec811a75a9c226c73ec53

Add support for detecting 8937 target and parsing the ramdumps.

Change-Id: If487b01d02c634b8e9788ada07d408cd516af556

Most read functions that take a virtual address also understand string
variable names, for convenience.  Add this support to the `hexdump'
function as well.

Change-Id: I773992ba3793a68226b49525b66141b021924387

Although the `--shell' option can currently be used for ad-hoc
debugging, it's not ideal for scripting since it prints out a bunch of
other stuff during initialization.  Add a dedicated `--eval' option that
executes arbitrary Python code without printing anything else.

Change-Id: I9e24e6d140dd49208b850b2a17ac2f599a35657b

Most of the time 100 is a good default max length when reading any old
C-string.  Use it.

Change-Id: I1805b0b4b2b9bc18c06f4ca0e7cd6cd70b854620

GdbMI.symbol_at returns a string, not a GdbSymbol object, so the extra
field traversal is unnecessary.

Change-Id: I85acd83657e4b6055bd1f7945da73dcf9d4839f1

The name symbol_at gives a better idea of what the function does, and it
more closely mirrors the corresponding gdbmi function.

Change-Id: If2f3df505bc129a3b963ea363e4c544599626948

In lieu of a more generic way of reading fields from structures,
introduce another specialized structure field reader for reading C
strings.

Change-Id: I6aba392f59179fa70a065a08f19a694e87f683dd

Rename addr_lookup to address_of to match common terminology more
closely.

Change-Id: I7fc744ce88d1f8880f13dfbf83fb0efcbe9ba0f2

The cmdParse() function has excessive cyclomatic complexity.

Reduce the cyclomatic complexity by writing helper functions to obtain
version info, handle processing log contexts, and handle processing log
pages.

Change-Id: I15b8da9b20bb7b20daad3f0f0ac460b6cfe8ad89

LogPage_v1.sortAndLink() has excessive cyclomatic complexity. Reduce the
complexity by refactoring sortAndLink() into several smaller functions.

This commit is to be squashed into the commit containing all other
style fixes.

Change-Id: I52ac6027e5f9d45af7d44d4b24beff7a28baea05

The LogPage_v1's class documentation says that the class represents a
version 0 IPC log page, but the class represents a version 1 IPC log
page.

Correct the error.

Change-Id: If6ca9a66d486f36d5a2078ff7f78850c35ad65f3

IPC Logging currently displays the kernel log timestamp, which is based
on a timer that does not increase when the Apps processor is in suspend.
This means that the kernel log timestamp "loses time" and cannot be
correlated with events on other processors. The source of the QTimer
timestamp is always running and has the same source other logs in the
system, which makes it convenient to correlate logs across the system.

Update the IPC Logging extraction script to handle version 2 of IPC
Logging, which includes the QTimer timestamp.

Change-Id: Ia4534a53012e29efe5ac647b6212530f84c07f46

The coding style of the IPC Logging extraction script is not compliant
with the Python coding style guide (PEP 0008). In order to be merged
into the Linux Ram Dump Parser, the code must be made compliant with PEP
0008.

Bring the code into compliance with PEP 0008.

Change-Id: Idf587a55670a5b30c7668c78b1625100d6128c9c