Add a utility function for iterating through all valid process
and thread of each process.
Use it in different parser where we are traversing through the task
list Ex : memusages.py, ion_buffer_parse.py

Change-Id: Ided26acc67e7c5dc2ba7d4c2db0935f0c9fa24f1
Signed-off-by: Ankur Bansal <ankban@codeaurora.org>

1) When lrdp-v2 is parsing RAM dumps generated on ARM-32 platforms,
   the Trace32 startup script will not contain any instructions
   to enable MMU support, which causes Linux kernel symbol loading
   failure on some newer Trace32 simulators.

   Add Trace32 startup instruction to set bit 0 of P15:0x1 if
   lrdp-v2 detects MMU support within the RAM dump.

2) Use task.symbol.loadmod instead of data.load.elf to load all
   the kernel moduels' symbols to avoid symbol loading failures.

Change-Id: Ibae79e3c80279788d7cccd28080d2cecd5432a4b

Currently LRDP-v2 will only add linux.t32 and linux.men into
the t32_startup_script.cmm script when it is parsing RAM
dumps generated on ARM 32-bit platforms.

Change the code in ramdump.py to add linux3.t32 and its
related linux.men into t32_startup_script.cmm when it is
determined that the kernel version is greater than 3.0.0.

Change-Id: Id0ddc62cc702b0bc586bb9864ceb02177d397e13

Verify that files exist before checking file size.

Change-Id: Icb55984bf33a677594726345f4c82c55c2948134

The hypervisor may populate an imem cookie with the location of
a standard dump table, instead of using the table allocated by linux.
Read the table location from this cookie instead of relying on the
linux variable 'memdump'.
On error, fall back to the old approach of reading from 'memdump'.

Change-Id: Id99bb643fb7f35de79ff7308a999cc2143d7aff0

Currently the loadble module symbol parsing code is only decoding
the symbol names without prefixing the module names. This will
result in some confusion when two module's symbol names are
identical, and things get worse espeicially when parsing RAM
dumps where two WLAN drivers are loaded.

Prefix module names to module specific symbol names when parsing
their symbol files so user can easily tell which module is
involved in a call stack.

Change-Id: I3cf5e9527be191fb5f21830b1ba9f915d734b5d2

Starting from msm-4.9, a new field named 'core_layout' will be
available to replace 'module_core' in struct module.

Add code to parse the newly introduced field for loadable module
symbol addition based on the Linux kernel version.

Change-Id: I503ba6b0d4f5928bb2fea85ab3fdd4a33150b1c0

In thread_saved_field_common_32, read_word should not be used to
retrieve the thread_info structure's address because
get_thread_info_addr is already doing the same.

Change-Id: I422c67b98d318c0084ab32fb0ad9f180da186829

        In the latest kernel version minidump_table structure got changed. Some emelments are removed.
        like smem_table, version. In those information anyhow is not being used in ramparser. So removed all those elements
Change-Id: Ibce7ab2515737a7871c1f9df70d4eddee64bdc09

Add support to parse DCC dumps with autodump option to RDP
In autodump we give only ramdumps location without --ram-file
bin locations.

Change-Id: I87aa2b337415dd93cc5b60c813bf6cd1712f2565

	Read the linux banner data from vmlinux rodata section.
	Also read the linux banner data from ramump. Do a matching of both the data.
	If success then ramparser will go ahead and proces further
Change-Id: I1b9245f1a4fcc9cdff0a3bfb7293b2385981feba

	here fp is value is coming less than page_offset.
	Due that rest of the call stack is not getting printed

Change-Id: Ie878d41f0ecc16d21f9795c699f035a7460904b4

Current Linux Ram Dump Paser scripts are only able to load kernel
symbols by default. No loadable modules' symbols will be parsed
at startup time, which may result in 'unknown symbols' in some
cases, especially when checking SLAB info on dual-wifi platforms.

With this change, loadable modules' symbols can be parsed on
script startup by the following configurations:

1) Put all symbols under a certain dir, such as:

<dump_location>/symbols/wlan.ko
<dump_location>/symbols/wlan_sdio.ko

2) Add --sym_path when invoking the scripts, such as:

python %RAM_DUMP_PARSER_PATH%\ramparse.py --sym_path
<dump_location>/symbols

With the above actions, all loadable modules' symbols will be
parsed and stored for subsequent information dumping. Symbol
loading commands will also be added into the Trace32 startup
script.

Change-Id: Idda9c9a08cfd24c19bf4021e80fee5187cd031b9

The THREAD_INFO_IN_TASK kernel feature removes the thread_info
structure from task stack. Add support for this in the parser to handle
when this option is enabled.

Change-Id: I23eda300395936618e6d69eccd6c5d610c871ba8

Abstract out whether kaslr is enabled or not to allow ddrcompare to work
regardless of whether kaslr is enabled or not.

Change-Id: I4b00ed48748ce9a5a63c0905c99200ac9bfe4482

        As DCC is not going to be enabled on secure device,
        SDI would dump required registers in standard dcc dumping format.
        So extend ramparser’s DCC parsing support for <address><value> format.
        The KMISC section would contain all registers address value pair as mentioned below.
        Parse the data and generate the “dcc_captured_data.xml” and it should be same as actual dcc dump parsed xml.

Change-Id: Ib042ebc6895f0594f5784600174087a979e8709f

Add support for generating sram.bin from DCC_SRAM.BIN
With this NEW sram will call version 2 of DCC driver
for parsing.

Change-Id: If8012b1f38ba29daa5bdac2fd15820de51ea9cab

	A minidump supports fewer features than a full ramdump,
	but does not require the user to save all 4GB+ of memory.
	Instead a small subset of DDR is saved by crashscope as an elf file.
	Currently dmesg logs, rtb logs, and the cpu context parser are supported.

	Example usage: python ramparse.py --vmlinux <vmlinux> --minidump
			--ram-elf <elf_file> --ram-file <OCIMEM.bin> --everything

Change-Id: Ib689b4811d66472ac20aa7c63893fdaed915512e

   This changes to fetch serila number of HW from dump

Change-Id: I93ee37feafd9e407fe380761c0e6469fabe40f7d

When calling read_structure_field with an undefined symbol, the
desired behavior is to return None rather than crash.

Change-Id: Iaf172a038779cf767b55c47ec37b8e90e194aa0f

Add a function for reading a signed 64 bit value from a ramdump.

Change-Id: Ic7e5a8a7cb9d5fd551ffb2c3add2499a25aff540

This prints kimage_voffset info if kaslr is enabled.

Change-Id: Ia18bba9f2df1c579721aeb44a8dd2b7143183b89

This adds remove_file function to ramdump class.

Change-Id: Ibe6196aad7ccd1c2bb381b9adab682394244f879

As of commit c4c54dd1 (kernel/cpu.c: change type of cpu_possible_bits
and friends), cpu_present_bits no longer exists. Add new method of finding
number of cpus and also change other functions to use the get_num_cpus
API instead of defining it again.

Change-Id: I6d38d505ba7674b94e8481e6679226803eba977e

Add check to avoid "object has no attribute 'kaslr_addr'" on boards
where kaslr_addr is not defined.

Change-Id: I2691b313f6a0ab75b216cd678245e97cf22ce4e7

Kaslr-offset in stored in imem by the kernel driver. This patch
enables the parser to extract the required offset before parsing.

Change-Id: Ie773a2e52989b0f2a83c19d39ffdba7f77911e39

When kernel address space layout randomization is enabled by kernel,
a new kaslr_offset will be added to the kimage_vaddress. This patch
adds this offset to get the correct kimage_vaddress.

Change-Id: Ia19c5b4d47674e2753ba167e5a50295902720457

The startup scripts used with T32 is not generated properly for use with
Linux. Fix this:

* Make T32 use absolute paths on both Windows and Linux
* Update T32 config scripts to work with Linux

Change-Id: If96dd762d8cb5a9419d149d370ae21cf222ed93b

the paths used by the T32 launcher used the incorrect directory when the
autodump option was passed.

Additionally, fix an issue where not all of the files detected by autodump
are printed out.

Change-Id: Id96500e6a59961aa1d06af515560b367a42f2e5b

Customers normally share extracted logs from RAMDUMP because of
various reasons including security and to protect personal
information. Add support to extract WLAN module debug details so
that customer issues can be triaged easily.

CRs-fixed: 1074311
Change-Id: If7a3f2c6ed990d9203ea93c8e0688c5c44f13c53

   File creation is failing in some filers if it is created
in a non-existing folder.

Change-Id: Ieaacc3f1992b38683c52df6225727ab88944d65a

Latest kernel introduces KIMAGE_VADDR which allows the
virtual base of the kernel region to be below PAGE_OFFSET.

Change-Id: I9d063f882e220d0795eca45a618ad72580dff552

The board number is intended to be a human readable identification value.
Allowing this to be a string is more flexible.

CRs-Fixed: 1013327
Change-Id: If523acafc54f5026680d18c95e4899fb0436599d

Calling read_byte() on windows may return the empty string '' prior
to the end of the file without opening the file in 'rb' mode.

The 'rb' mode was removed by
commit 5743b613
("lrdp-v2: ramdump: Fix autoparse for some targets.")

Change-Id: Ibea608112400c06a9adc6f1fd3b4842a87717846

   Add memory files used for some targets.

Change-Id: I64df5549568a97f907b0e493f3d4cac81a98ddf9

Add support for parsing dump_info.txt and load.cmm to properly set phys
offset and find the base addresses of memory files.

This change fixed autoparse on a few targets, though may not apply to all
platforms and situations.

Changes based heavily on those made from a prior change.
See Change-Id: I4be54a48a659ac1e6346d9178d19a8b40e2e1b6d

CRs-Fixed: 1038185
Change-Id: If98a4073e9afc98fd3903e606539b9e4e9ca2c51

Debug image parsing currently includes QDSS ETM and ETR binary data
parsing by default. However, these two parsing operations can take a
significant amount of time if either of their respective data buffers
are very large. Furthermore, this binary data is not needed for most
common debug image parsing use cases.

Add an argument to optionally disable QDSS ETM and ETR binary data
parsing when debug image parsing has also been selected.

Change-Id: Iab25c15d00dde1bb5dfafb3149e6e55760fd6291

Add module to get information from MDP dumps, which can occur under
situations where MDP cannot recover.

Change-Id: I8ecdced37206947c434c7ddf4d7d61979c9cf92f

Currently we split each config line on the equals sign, assuming that
there's only one equals sign there.  This isn't a valid assumption for
cases like:

    CONFIG_CMDLINE="console=ttyAMA0"

Fix this by splitting at the first equals sign, rather than splitting
at *all* equals signs.

Change-Id: I01e44fe2e9a0f09a8bebdd76715002f6b12cf0b5

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

Change-Id: I208d964ea3ca58536a0b80a32b4e334c73aae534