procmem: fix procmem crash issue

For the case pm_map_pagemap return error(e.g, maps[i]->start==maps[i]->end==0),
the main loop continue without set mis[i] fields, and then mis[i]==0. So that
the corresponding mi item is 0 for this case.
Skip dumping this item to avoid crash.

Change-Id: I7e1bea1abdccfd7594b9d904938b3462dc182a76
Signed-off-by: Hong-Mei Li <a21834@motorola.com>
Adding a few bandwidth tests.

New tests being added:
- copy_bandwidth: Gathers the copy bandwidth using four different
  hand-coded assembler routines and using memcpy.
- write_bandwidth: Gathers the write bandwidth using four different
  hand-coded assembler routines and using memset.
- per_core_bandwidth: Launches a thread of any one of the write/copy
  bandwidth tests locked to every available core on the machine.
- multithread_bandwidth: Launches a user specified number of threads running
  any one of the write/copy bandwidth tests.

Each of the tests can be modified as to the size of the data to manipulate
and the number of loops to run.

Deleted tests:
- memcpy (a better memcpy benchmark can be found in system/extras/micro_bench)
- memset (a better memset benchmark can be found in system/extras/micro_bench)
- memcmp (no real replacement, but I plan to add this to micro_bench)
- strlen (no real replacement, but I plan to add this to micro_bench)
- cpufreq (this doesn't work any more)

All verification tests have been mostly shifted to system/extras/libc_test.

Merge from internal master.

(cherry-picked from commit 1348ce27ee9bb8e50a3294879c1523fa4b4d8f8b)

Change-Id: I96e9f26357e4bac1d7bb8736176d80cc41d0b36b
Merge "Adding a few bandwidth tests."
Update the libc_test.

- Refactored the fencepost testing code, include adding a fencepost
  before the buffer (when not using the value returned by malloc).
- Add a verbose option to display more information as the test runs.
- Change the test to stop on the first fail rather than keep going.

Merge change from internal master.

(cherry-picked from commit f0b2c68c83e6ced8f988f014bc235393ca231958)

Change-Id: I846c7a01be64a0bcea49084fe2f75df4af00e699
Add defines around neon code.

Merge from internal master.

(cherry-picked from commit e5282ae49814c9ed0b9bdec920a20e6978349327)

Change-Id: I00bf68545987ef360fe489b14df8e11fdd7b687b
Merge "Update the libc_test."
Merge "Add defines around neon code."
Merge "procmem: fix procmem crash issue"
Fix hard-coded fencepost value.

Merge from internal master.

(cherry-picked from commit 1685d00d0a6b905a820a76c9686b6b4b077dfe4a)

Change-Id: Ie9d64844c28ea720091acfefc21f888827fecb4b
Merge "Fix hard-coded fencepost value."
Add read bandwidth and small refactor.

- Addition of read bandwidth test.
- Move the allocation of all buffers used for testing into the
  setSize() function.
- Add a canRun function to indicate whether a test is able to
  run on this platform. Currently, this only disables neon bandwidth
  tests on platforms that don't support neon.
- Refactor the thread testing functions to use one common routine.

Merge from internal master.

(cherry-picked from 1a3794a84074d7f22b8ddaba840aedd758a14cdd)

Change-Id: Ie0f29ec7e484a376471d121333b1982be8f41393
Merge "Add read bandwidth and small refactor."
Fix a few incorrect return codes.

Merge from internal master.

(cherry-picked from f90ab5f4ab00ddfbcf313be9001837aaefd64ba2)

Change-Id: I87379bac089107a95301015d849433c9e304a988
Merge "Fix a few incorrect return codes."
Add guards around neon code.

Missed the neon code in the copy bandwidths. Added guards and the
functionality to indicate that these are neon based benchmarks.

(cherry-pick of a67e53c2345eac337d24e4decaf4733c5314aff8.)

Change-Id: If0fae051c47979eb243681a3c994222cefaae826
Merge "Add guards around neon code."
Merge branch 'master' into HEAD

Conflicts:
	tests/memtest/Android.mk

Change-Id: I8defa9d3360cbdcc041cc03b9b8262c9a13d7962